ci(publish): upgrade npm CLI before publish (Trusted Publishing needs >=11.5.1) - #7
Merged
Merged
Conversation
… >=11.5.1) v1.0.4 publish attempt got a 404 (anonymous/unauthenticated request) instead of the earlier 403 -- OIDC auth wasn't even attempted. Node 22's bundled npm is ~10.x, which predates Trusted Publishing support entirely. Added an explicit `npm install -g npm@latest` step after Setup Node so the CLI actually supports the OIDC exchange, regardless of what Node bundles.
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.
v1.0.4 got a 404 (fully unauthenticated request) instead of the earlier 403 -- OIDC exchange wasn't happening at all. Root cause: Node 22's bundled npm CLI is ~10.x, which predates Trusted Publishing support. Adds
npm install -g npm@latestafter Setup Node.