Repository navigation
ci: stage each release on npm for a maintainer to approve - #11
Merged
MorningLightMountain713 merged 1 commit intoOct 15, 2026
Merged
MorningLightMountain713 merged 1 commit into
MorningLightMountain713 merged 1 commit into
Conversation
The trusted publisher for @runonflux/nat-upnp allows `npm stage publish` only. A published GitHub release stages the version; it becomes public when a maintainer approves it with 2FA. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
The trusted publisher for
@runonflux/nat-upnpon npm is RunOnFlux/nat-upnp,ci.yml, and it allowsnpm stage publishonly. A published GitHub release now stages the version on npm. It becomes public when a maintainer approves it with 2FA, on npmjs.com under the package's Staged Packages tab or withnpm stage approve <stage-id>.npm stageneeds npm 11.15.0 or later, so the publish job installs it before staging.A staged version holds its version number even before approval: if a release run fails after staging, check the Staged Packages tab before running it again.
🤖 Generated with Claude Code