Repository navigation
feat(create-release-branch): add Changesets mode - #170
Open
GuillaumeRx wants to merge 1 commit into
Open
GuillaumeRx wants to merge 1 commit into
GuillaumeRx wants to merge 1 commit into
Conversation
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
from
November 12, 2026 14:54
c4fa918 to
bce6016
Compare
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
from
November 12, 2026 15:10
bce6016 to
26e62e7
Compare
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
2 times, most recently
from
November 12, 2026 16:11
3e9a3f2 to
847ec33
Compare
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
2 times, most recently
from
November 12, 2026 17:33
1d90303 to
5061364
Compare
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
from
November 12, 2026 17:44
5061364 to
b2f2b01
Compare
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
from
November 13, 2026 10:28
b2f2b01 to
4fa4422
Compare
Member
|
@metamaskbot publish-preview Hijacking your PR to test preview builds with OIDC. |
Select the mode with --changesets or with "mode": "changesets" in release.config.json. The release spec lists the packages of the pending Changesets with the version specifiers that the Changesets give. The maintainer can leave packages out, but cannot change their versions. Before the Initialize Release commit, the mode checks that the .changeset directory has no uncommitted changes, so that this commit does not take in a Changeset by mistake. The functional tests load the real @metamask/changesets-changelog module from its source.
GuillaumeRx
force-pushed
the
gr/crb-cs-06-mode
branch
from
November 16, 2026 11:20
4fa4422 to
87dde2d
Compare
2 of 4 tasks
GuillaumeRx
marked this pull request as ready for review
November 16, 2026 12:43
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Explanation
Adds Changesets mode to
create-release-branch. It connects the load, candidates, plan, and apply steps from the earlier PRs.Choosing the mode. Use the
--changesetsflag, or set"mode": "changesets"inrelease.config.json.--interactiveis not supported yet. It fails before it changes anything.createChangesetsModeimplementsMode. Itspreparestep checks that the.changesetdirectory has no uncommitted changes. The core runs this step before the "Initialize Release" commit, so that this commit does not take in a Changeset by mistake. The mode reads the Changesets again each time it lists the candidates, so it sees changes that the user makes while the editor is open.planreuses what the lastlistCandidatescall read, because the core calls them one after the other.Release spec template. Each package gets the version specifier that the Changesets give and a short comment. The instructions say not to change the value, and explain when to use
intentionally-skipinstead of removing a package:Tests. New functional tests run the tool on a Changesets monorepo with the real
@metamask/changesets-changelog. They cover a full release, a partial release, a changed version that stops the tool,Unreleasedentries that stop the tool, an uncommitted Changeset that stops the tool before the first commit, a committed Changeset without a pull request number, the config file, a failed apply, the legacy fallback, and--interactive.Docs.
docs/setup.mdhas a new "Changesets mode" section. It explains when to useintentionally-skip, thatUnreleasedentries stop the release, and that an entry has no link if the commit of its Changeset has no pull request number.References
create-release-branchChecklist