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

Commit f219ec7

Browse files
authored
Update RELEASING.md (#466)
* Update RELEASING.md * fix review comment
1 parent 40f7b53 commit f219ec7

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

RELEASING.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,12 @@ Create a new branch called `x.y.z-proposal` from the current commit.
1414

1515
## Use Lerna to prepare each package for release
1616

17-
Use `npm install` and `lerna bootstrap` to initialize all package directories.
17+
Use below command to initialize all package directories.
18+
19+
```
20+
npm install
21+
```
22+
1823
Also, use `lerna publish --skip-npm --skip-git` to bump version numbers.
1924
Ensure that the version being bumped to is `x.y.z`. This should create some unstaged changes.
2025

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

6469
Publish the GitHub release, ensuring that the tag points to the newly landed commit corresponding to release proposal `x.y.z`.
70+
71+
## Update CHANGELOG and release versions in examples
72+
* After releasing is done, you need to update all examples to point to the latest
73+
version.
74+
* In addition, update the CHANGELOG.md and start new Unreleased label.
75+
* Create a new commit with the exact title: `Post Release: update CHANGELOG, Examples and ReadMe`.
76+
* Go through PR review and merge it to GitHub master branch.

0 commit comments

Comments
 (0)