Stage npm releases for owner approval - #11
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
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.
Switch the release workflow from direct
npm publishtonpm stage publish, matching the trusted publisher configured on npmjs.com with npm's recommended staged-only setting.release.yml) still rebuilds and tests the tag, packs one tarball, and runs the package gate. It then stages that exact tarball undernextwith provenance, and the run summary lists the tested integrity and the owner commands.verify-release.yml, new, no publishing permissions) runs after the owner approves the staged version (npm stage approve, 2FA). On Linux and Windows it checks that registry integrity matches the tested tarball and thatnextpoints at the version. It then installs fresh from the registry, reruns the MCP transport tests against the installed bin, and checks the provenance attestation andnpm audit signatures.No package code changes;
v1.1.0still points at 08b189f.