mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-22 01:47:00 +01:00
Update publishing doc to reflect automation (#6899)
This commit is contained in:
parent
2761cc5a2d
commit
618c1caf40
@ -20,9 +20,9 @@ We try to ensure certain criteria are met before deploying:
|
|||||||
|
|
||||||
## Incrementing Version & Changelog
|
## Incrementing Version & Changelog
|
||||||
|
|
||||||
Version can be automatically incremented [using our bump script](./bumping-version.md).
|
Version can be automatically incremented by creating a branch with the name `Version-vX.Y.Z`, where `X`, `Y`, and `Z` are numbers. Branches should be created off of the main branch. [Branches can be created on GitHub.](https://help.github.com/en/articles/creating-and-deleting-branches-within-your-repository)
|
||||||
|
|
||||||
npm run version:bump `$BUMP_TYPE` where `$BUMP_TYPE` is one of `major`, `minor`, or `patch`.
|
Once a version branch has been created, a build on CircleCI will create a Pull Request for the release with the app manifest and changelog versions bumped.
|
||||||
|
|
||||||
## Preparing for Sensitive Changes
|
## Preparing for Sensitive Changes
|
||||||
|
|
||||||
|
@ -18,10 +18,9 @@ Simply follow the steps in [the publishing guide](./publishing.md).
|
|||||||
|
|
||||||
### Prepare Rollback Release
|
### Prepare Rollback Release
|
||||||
|
|
||||||
1. Be on the new risky version branch.
|
Follow the steps in [the publishing guide](./publishing.md) with a different context:
|
||||||
2. Run `npm run rollback $ROLLBACK_TARGET_VERSION`.
|
|
||||||
|
|
||||||
The rollback version will now be a branch and tag on the origin.
|
Instead of creating a version branch off of the main branch, create a version branch off of the latest release. It is customary that this release increments the patch version number.
|
||||||
|
|
||||||
### Roll the normal release out
|
### Roll the normal release out
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user