Fix npm trusted publishing - upgrade npm CLI to latest #10
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
GitHub runners have npm 10.x but trusted publishing requires npm 11.5.1+. Also restore registry-url to setup-node for proper .npmrc configuration.
khaledosman
approved these changes
Oct 20, 2025
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.
Problem
npm trusted publishing was failing with:
Root Cause
GitHub-hosted runners ship with npm 10.x, but npm trusted publishing requires npm CLI v11.5.1 or later.
Solution
registry-urlto setup-node for proper.npmrcconfigurationTesting
After merging, will delete and recreate v0.0.2 release to verify trusted publishing works.
References