ci(publish): pin npm for trusted publishing#539
Merged
Conversation
Pin the publish workflow to npm 11.11.0 because the current Node 22 bundled npm 10.9.7 fails to self-upgrade directly to npm@latest with MODULE_NOT_FOUND (missing promise-retry), while npm trusted publishing only requires npm >= 11.5.1. Repro: GitHub Actions run 23901996227 and local Node v22.22.2 / npm 10.9.7 repro.
remiroyc
approved these changes
Apr 2, 2026
Foulks-Plb
approved these changes
Apr 2, 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
2 participants
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.
Summary
npm@11.11.0instead ofnpm@latestCannot find module "promise-retry"Validation
npm install -g npm@latestnpm install -g npm@11.11.0succeeds in the same environment