Repository navigation
fix: use Node 24 in publish workflow instead of upgrading npm - #35
Merged
Merged
Conversation
Node 22's bundled npm 10.9.7 breaks when self-upgrading to npm 11.x (MODULE_NOT_FOUND for promise-retry). Node 24 ships with npm 11.x natively, which supports OIDC trusted publishing out of the box. This removes the 'Upgrade npm for OIDC trusted publishing' step entirely.
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
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
Fixes the publish workflow failure where
npm install -g npm@latestcrashes withMODULE_NOT_FOUND: Cannot find module 'promise-retry'. Node 22's bundled npm 10.9.7 corrupts itself when self-upgrading to npm 11.x.Changes