Repository navigation
fix(release): use npm staged publishing - #29
Merged
Merged
Conversation
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.
The npm trusted publisher permits staged publishing, so direct publication of v1.0.1 was rejected while GitHub Packages succeeded. Use npm stage publish with the latest tag; maintainers approve the staged package with 2FA before it becomes publicly available.
Allow manually publishing an existing release to one selected registry using the current workflow. This lets v1.0.1 reuse its existing release tarball without republishing to GitHub Packages or moving the Git tag. Document staging, approval, and recovery in AGENTS.md.
Validation: actionlint passed with its outdated ubuntu-26.04 label check excluded; changed-file formatting and git diff --check passed. The preceding release build and all checks succeeded. Hosted staging will be verified after merge.