Repository navigation
chore(release): enter changesets pre-release mode on the beta tag - #188
Merged
Merged
Conversation
v3 is the line under active development and the 2.x line is closed to hotfixes, so `main` should be cutting `3.0.0-beta.N` rather than sitting on a growing pile of unreleased major changesets. `changeset pre enter beta` writes `.changeset/pre.json`. Nothing about authoring a changeset changes; the Version Packages PR now produces prerelease versions, and `changesets/action/publish` uses the pre tag as the npm dist-tag, so betas land on `beta` and `npm install hermex` keeps resolving to 2.11.1 until we run `changeset pre exit` for the real 3.0.0. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Coverage Report
File CoverageNo changed files found. |
Contributor
Output Review0 of 27 case(s) changed · 0 invariant breach(es) · all 27 cases Reference: Output is unchanged. Nothing to review. |
Contributor
|
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
1 participant
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.
What
Enters Changesets pre-release mode on
mainwith the tagbeta, and documents what that means for contributors..changeset/pre.json—{ "mode": "pre", "tag": "beta" }, written bypnpm changeset pre enter betaCONTRIBUTING.md— a "The v3 Beta" subsection under How Releases HappenNo changesets are consumed, and nothing about authoring one changes.
Why
v3 is the line under active development and we are not shipping 2.x hotfixes any more. Today
maincarries fourmajorchangesets that cannot be released without cutting a final 3.0.0, so they just accumulate. Pre-release mode lets us ship the work continuously as3.0.0-beta.Nand get it in front of people before the stable cut.What this changes about releases
3.0.03.0.0-beta.0, then-beta.1, …latestbetanpm install hermexresolves tonpm install hermex@betaThe pipeline needs no edits:
changesets/action/publishreads the pre tag and publishes under it, andselect-modebehaves the same way it does outside pre mode.The first Version Packages PR after this merges will be
3.0.0-beta.0, applying the 16 pending changesets (4 major, 5 minor, 6 patch, 1 empty).Exiting
Cutting the stable 3.0.0 is a deliberate, separate step —
pnpm changeset pre exitin its own PR, after which the next Version Packages PR is the real 3.0.0.Verification
pnpm changeset status→ still reportsmajorforhermex, no changesets consumedpnpm run format:ci,pnpm run lint:ci→ passA local
changeset versiondry run was not possible —@changesets/changelog-githubrequires aGITHUB_TOKENto resolve PR authors — so the exact resulting version is confirmed from the pre-mode semantics, and will be visible for review in the Version Packages PR before anything publishes.🤖 Generated with Claude Code