Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork6.3k
Release Process
Haoqun Jiang edited this pageFeb 28, 2020 ·3 revisions
The Git workflow used in this project is largely inspired byGitflow workflow(https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
- The development branch is
dev
- When releasing a newpatch version:
- Cherry-pick the necessary commits to the
master
branch - Push to GitHub, make sure all CI tests are passed, and then run
yarn release
in the project root - Draft a newrelease in the GitHubReleases page
- Merge
master
back intodev
- Cherry-pick the necessary commits to the
- When releasing a newminor/major version
- Cherry-pick the necessary commits to the
next
branch - Push to GitHub, make sure all CI tests are passed, and then run
yarn release --dist-tag next
in the project root - Draft a newpre-release in the GitHubReleases page
- Merge
next
back intodev
- If no urgent regressions have been reported in3 days:
- run
npm dist-tag add {{package-name}} latest
for all the packages in this repository - Go to the Releases page and uncheck the
This is a pre-release
option for this release
- run
- Otherwise, fix the bugs, and start over to release a new version from the
next
branch. But this time, the new version string should be bumped as a patch.
- Cherry-pick the necessary commits to the
For edits please submit a PRhere. For documentation, please visitcli.vuejs.org.
Project Management
Contributing
Documentation