Skip to content

[v22.x] deps: upgrade npm to 10.9.8#62463

Open
npm-cli-bot wants to merge 1 commit intonodejs:v22.x-stagingfrom
npm:npm-v10.9.8-22
Open

[v22.x] deps: upgrade npm to 10.9.8#62463
npm-cli-bot wants to merge 1 commit intonodejs:v22.x-stagingfrom
npm:npm-v10.9.8-22

Conversation

@npm-cli-bot
Copy link
Copy Markdown
Contributor

Dependencies

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/security-wg

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. npm Issues and PRs related to the npm client dependency or the npm registry. v22.x Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch. labels Mar 27, 2026
@owlstronaut
Copy link
Copy Markdown

please add a do not release on v20 label

@Renegade334 Renegade334 added the dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. label Mar 27, 2026
@Renegade334 Renegade334 linked an issue Mar 27, 2026 that may be closed by this pull request
@aduh95 aduh95 changed the title deps: upgrade npm to 10.9.8 [v22.x] deps: upgrade npm to 10.9.8 Mar 27, 2026
@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Mar 27, 2026
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Mar 28, 2026
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

jordanstephens added a commit to DefangLabs/pulumi-defang that referenced this pull request Apr 9, 2026
The ubuntu-24.04 runner image (20260329.72.1) ships with a corrupted
Node 22.22.2 tool cache: npm 10.9.7 is missing `promise-retry` from its
own module tree, causing any `npm install -g` to fail with
MODULE_NOT_FOUND. This broke all nodejs SDK build jobs.

Node 24 ships with npm 11 natively, which supports OIDC Trusted
Publishers without requiring a separate upgrade step, so we can drop the
`npm install -g` workaround entirely.

See: actions/runner-images#13883
     nodejs/node#62463

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. needs-ci PRs that need a full CI run. npm Issues and PRs related to the npm client dependency or the npm registry. v22.x Issues that can be reproduced on v22.x or PRs targeting the v22.x-staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Possible NodeJS 22.22.2 regression when installing latest NPM

7 participants