Use npx npm@latest in publish step - #6
Merged
Merged
Conversation
Globally upgrading npm mid-workflow corrupts the install (promise-retry MODULE_NOT_FOUND). Running the publish through npx keeps the base environment intact and still gives us the npm >= 11.5.1 required for Trusted Publisher OIDC token exchange. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 20, 2026
Merged
This was referenced Apr 26, 2026
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.
Globally upgrading npm broke the runner install. Switching to npx keeps the base env intact and still picks up npm 11+ for the OIDC publish.