Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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 isdev
  • When releasing a newpatch version:
    • Cherry-pick the necessary commits to themaster branch
    • Push to GitHub, make sure all CI tests are passed, and then runyarn release in the project root
    • Draft a newrelease in the GitHubReleases page
    • Mergemaster back intodev
  • When releasing a newminor/major version
    • Cherry-pick the necessary commits to thenext branch
    • Push to GitHub, make sure all CI tests are passed, and then runyarn release --dist-tag next in the project root
    • Draft a newpre-release in the GitHubReleases page
    • Mergenext back intodev
    • If no urgent regressions have been reported in3 days:
      • runnpm dist-tag add {{package-name}} latest for all the packages in this repository
      • Go to the Releases page and uncheck theThis is a pre-release option for this release
    • Otherwise, fix the bugs, and start over to release a new version from thenext branch. But this time, the new version string should be bumped as a patch.

For edits please submit a PRhere. For documentation, please visitcli.vuejs.org.

Clone this wiki locally

[8]ページ先頭

©2009-2025 Movatter.jp