fix(ci): pin release job to Node 22.21 to fix npm global upgrade#12
Merged
Conversation
Node 22.22.2's bundled npm 10.9.5 ships broken in the GitHub Actions toolcache — `npm install -g` fails with `Cannot find module 'promise-retry'`. This blocks the `Upgrade npm for OIDC trusted publishing` step in the release job. Pin only the release job to 22.21.0 (whose bundled npm 10.9.3 still works); other jobs use yarn and aren't affected.
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.
Summary
The
releasejob on main is failing at the Upgrade npm for OIDC trusted publishing step:npm install -g npm@latestaborts withCannot find module 'promise-retry'. This is a regression in Node 22.22.2's bundled npm 10.9.5 as shipped in the GitHub Actions toolcache — the bundled arborist is missing one of its runtime dependencies, so the in-place npm can't install anything (including itself).Pin only the release job to
22.21.0(bundled npm 10.9.3 still works), so it can then upgrade to npm@latest for OIDC trusted publishing. Other jobs (install,lint,typescript,unit-tests,build-package) all use yarn and are unaffected.Reference: failing run https://github.com/Andarius/react-native-zstd/actions/runs/25955516695/job/76301446653
Test plan
Upgrade npmstep passes → publish succeeds