-
Notifications
You must be signed in to change notification settings - Fork 40
Core Release
Sean Albert edited this page Jul 27, 2022
·
2 revisions
- Create a new branch from master with a name that follows the format of yyyy-mm-dd-release
- In most cases you'll be able to merge dev into this branch, sometimes you may be creating a release from cherry-picking commits from dev
- Create a new release report with ZenHub
- Open a PR to merge into master
5. Review the commit history of dev since the last release and add each issue to the release. Add any PRs directly to the release only if their isn't a related issue
6. Add the report to the PRs description
7. Have the release PR reviewed
- Merge the release branch into master
- Checkout the master branch and make sure it's up-to-date
- Using lerna, version bump and publish the core packages to NPM
- Since we want to dev's versions to be sequential from the new release, create a branch from dev with the naming convention yyyy-mm-dd-sync-master
- Sync master to this branch
- Open a PR with this branch to merge into core dev and merge