Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Commit

Permalink
Update RELEASING.md (#466)
Browse files Browse the repository at this point in the history
* Update RELEASING.md

* fix review comment
  • Loading branch information
mayurkale22 authored Apr 4, 2019
1 parent 40f7b53 commit f219ec7
Showing 1 changed file with 13 additions and 1 deletion.
14 changes: 13 additions & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,12 @@ Create a new branch called `x.y.z-proposal` from the current commit.

## Use Lerna to prepare each package for release

Use `npm install` and `lerna bootstrap` to initialize all package directories.
Use below command to initialize all package directories.

```
npm install
```

Also, use `lerna publish --skip-npm --skip-git` to bump version numbers.
Ensure that the version being bumped to is `x.y.z`. This should create some unstaged changes.

Expand Down Expand Up @@ -62,3 +67,10 @@ Check your e-mail and make sure the number of “you’ve published this module
## Publish the GitHub Release

Publish the GitHub release, ensuring that the tag points to the newly landed commit corresponding to release proposal `x.y.z`.

## Update CHANGELOG and release versions in examples
* After releasing is done, you need to update all examples to point to the latest
version.
* In addition, update the CHANGELOG.md and start new Unreleased label.
* Create a new commit with the exact title: `Post Release: update CHANGELOG, Examples and ReadMe`.
* Go through PR review and merge it to GitHub master branch.

0 comments on commit f219ec7

Please sign in to comment.