You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Git workflow used in this project is largely inspired by [Gitflow workflow]()(https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
3
+
4
+
* The development branch is `dev`
5
+
* When releasing a new **patch** version:
6
+
* Cherry-pick the necessary commits to the `master` branch
7
+
* Push to GitHub, make sure all CI tests are passed, and then run `yarn release` in the project root
8
+
* Draft a new **release** in the GitHub [Releases](https://github.com/vuejs/vue-cli/releases) page
9
+
* Merge `master` back into `dev`
10
+
* When releasing a new **minor/major** version
11
+
* Cherry-pick the necessary commits to the `next` branch
12
+
* Push to GitHub, make sure all CI tests are passed, and then run `yarn release --dist-tag next` in the project root
13
+
* Draft a new **pre-release** in the GitHub [Releases](https://github.com/vuejs/vue-cli/releases) page
14
+
* If no urgent regressions have been reported in **3 days**:
15
+
* run `npm dist-tag add {{package-name}} latest` for all the packages in this repository
16
+
* Go to the Releases page and uncheck the `This is a pre-release` option for this release
17
+
* 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 patch.
0 commit comments