Repository navigation
Use staged publishing and unprefixed release tags - #5507
Merged
GeoffreyBooth merged 1 commit intoOct 25, 2026
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Two changes to
.github/workflows/release.yml:npm stage publishinstead ofnpm publish. CI uploads the version to npm's staging queue, and a maintainer must approve each version with 2FA, usingnpm stage approveor npmjs.com. The npm trusted publisher is configured stage-only (Allownpm publishunchecked), so a plainnpm publishfrom this workflow would be rejected.package.jsonversion to the release tag with novprefix, matching the repo's tag history (2.6.0, 2.6.1, 2.7.0). The tag is also passed through anenvvariable instead of being interpolated into the shell command. The release for this version must therefore be tagged2.7.1, notv2.7.1.Merge this PR before creating the GitHub Release. A release run uses the workflow file from the tagged commit, so a release created before this merges would run the old
npm publishworkflow and itsv-prefixed tag check.