Update the VERSION environment variable for the release number you want to make, e.g.Update the version number in package.json and package-lock.json on unstable to some provisional new version number, and push it.Fast-forward master to the merge commit: git checkout master & git merge unstable & git push.Create a merge commit that selects the state of unstable and push it: git merge -s ours master & git push.Make sure your local unstable is up-to-date: git checkout unstable & git pull.Make sure your local master is up-to-date: git checkout master & git pull.Since there can be conflicts, it's easiest to use the 'ours' strategy which will allow you to use the state of unstable as-is (i.e. If you are making a feature release, you need to merge unstable onto master.If you are making a patch release, you can just release master with its new patches.Current releases are based on the master branch: git checkout master.Follow the remaining ordinary release steps (step 5 and onward).This ensures that npm lists the current version as the latest one. For patch releases, do the back-port patch release before the corresponding current release.Each milestone should contain its corresponding issues and pull requests. Ensure that milestones exist for the releases that you would like to make.Ensure the docs are updated with the list of releases you would like to make in documentation/md/intro.md (on both master and unstable branches).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |