Skip to content

feat(create-release-branch): plan a Changesets release - #168

Draft
GuillaumeRx wants to merge 1 commit into
gr/crb-cs-03-candidatesfrom
gr/crb-cs-04-plan
Draft

GuillaumeRx wants to merge 1 commit into
gr/crb-cs-03-candidatesfrom
gr/crb-cs-04-plan

Conversation

@GuillaumeRx

@GuillaumeRx GuillaumeRx commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Explanation

Turns the release choices into a release plan. Nothing uses this code yet.

The choices only select the packages. The Changesets set their versions.

  • planChangesetsRelease returns a plan or a list of errors, like legacy mode.
    • It keeps the Changesets of the chosen packages with filterChangesets, and assembles the plan of these Changesets.
    • It reports a package whose value gives another version than the Changesets. The hint gives the value to use.
    • It also reports packages missing from the release spec, packages released only because of intentionally-skip, chosen packages with nothing to release, and an empty release.
  • filterChangesets in @metamask/changesets-utils now keeps none releases, and Changesets that have only none releases.

New dependencies: @changesets/assemble-release-plan and @metamask/changesets-utils. @metamask/changesets-utils is not published yet. It must be published before or with create-release-branch.

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Add planChangesetsRelease, which checks the release choices against the
Changesets release plan and builds the plan to apply. The choices select
the packages, and the Changesets set their versions. A choice that gives
another version than the Changesets is an error.

Select the Changesets with filterChangesets from changesets-utils. It now
keeps the none releases of a kept Changeset, and keeps the Changesets
that have only none releases.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant