ci(release): pin npm 11.x for trusted publishing - #450
Merged
Conversation
…ng provenance publish Signed-off-by: xNet Test <test@xnet.dev>
Contributor
|
Preview removed for PR #450. |
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.
npm 12.0.0 (released today, now
npm@latest) is missing thesigstoremodule its ownlibnpmpublishprovenance path requires — every--provenancepublish dies withMODULE_NOT_FOUND. This broke today's release run (nothing published; all packages still at their prior versions, no partial state).Pin the trusted-publishing step to
npm@11(what all previous successful releases used). Bump deliberately once a 12.x publish is verified.After merge, the push-triggered npm Release run should publish the staged 0.8.0/0.2.0 versions from #421.
🤖 Generated with Claude Code