- Stable releases use versions like
0.4.24and publish to the npmlatestdist-tag. - Prereleases use versions like
0.4.24-alpha.1and publish to the npm dist-tag named by the prerelease suffix, such asalpha.
Branch policy
Use branch separation to decide what code is eligible for each release channel. Dist-tags only control npm install defaults; they do not remove code from a package.mainis stable/releasable. Anything merged tomainis eligible forlatest.release/v*branches are for stable patch releases and hotfixes.next,alpha,beta,rc,canary, andprerelease/*branches are for prerelease integration.
main.
Stable release
Stable releases publish only when a reviewedrelease/vX.Y.Z PR merges into protected main.
Prepare and review release notes before creating the release commit:
release:prepare drafts missing changelog artifacts and exits non-zero for review so chained release commands stop before tagging. After the generated TODO summary is rewritten, rerun the same command to create the release commit and tag.
See Changelog process for the full workflow. For stable releases, bun run set-version <version> still enforces this checkpoint when maintainers run the lower-level release command directly.
Push the release branch without its local tag, open a PR to main, and merge it after approval and CI. The publish workflow checks out the exact PR merge SHA, verifies it before publishing, creates the stable tag at that commit, publishes npm packages, and creates the GitHub release. Before it publishes, the run waits for a maintainer to approve it in the npm-publish environment.
If that workflow needs recovery, rerun its original merged-PR event. Stable tag pushes and manual dispatches do not publish, so recovery cannot select a different commit.
For hotfixes, branch from the last stable tag, cherry-pick only the fix, publish the patch release, then merge or cherry-pick the same fix back into the prerelease branch.
Alpha release
Alpha releases must be reachable from a prerelease branch such asorigin/next or origin/alpha.
Use the same changelog draft workflow when the prerelease contains changes that users should know about.
npm-publish environment. A maintainer other than the person who pushed the tag approves the run on the workflow page, and only then is anything published. A prerelease branch has no PR review, so this approval is its review.
Consumers can install alpha builds explicitly:
CI guardrails
The publish workflow validates release channel boundaries before publishing:- Stable versions must publish with
latest. - Prerelease versions must publish with the prerelease dist-tag, such as
alpha. - Stable releases must come from a merged, reviewed
release/vX.Y.ZPR. - Prerelease tags must be reachable from a prerelease branch.
- Every publish, stable or prerelease, waits for a maintainer other than the one who started it to approve the run in the
npm-publishenvironment. - Merged
release/vX.Y.ZPRs publish stable releases only. - Every publish job verifies that its checkout matches the immutable event SHA.
- Builds, lifecycle scripts and
npm packrun in a job with a read-only token and no secrets. - The job that holds the npm token runs no code from the release commit. It checks that every packed tarball is a package this workflow publishes, at exactly the release version, then uploads it with lifecycle scripts off.
- A version already on npm is skipped only when its contents match the new tarball, or on a re-run of the same workflow run. Otherwise the publish fails, because something other than this run published that version.