Skip to content

[v26.x] deps: upgrade npm to 11.20.0 - #66259

Open
npm-cli-bot wants to merge 1 commit into
nodejs:v26.x-stagingfrom
npm:npm-v11.20.0-26
Open

npm-cli-bot wants to merge 1 commit into
nodejs:v26.x-stagingfrom
npm:npm-v11.20.0-26

Conversation

@npm-cli-bot

Copy link
Copy Markdown
Contributor

11.20.0 (2026-09-21)

Features

Bug Fixes

Chores

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. v26.x Issues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch. labels Sep 24, 2026
@reggi

reggi commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

per recommendation of @ MikeMcC399 #66245 (comment)

I've opened this as a replacement for #66245
freeing up npm@12 #66212 to land on main without conflict

@aduh95 aduh95 changed the title deps: upgrade npm to 11.20.0 [v26.x] deps: upgrade npm to 11.20.0 Sep 24, 2026
@MikeMcC399 MikeMcC399 added the dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. label Sep 25, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@MikeMcC399

This comment was marked as outdated.

@MikeMcC399

Copy link
Copy Markdown
Contributor

Separate issue #66324 opened for Darwin failures which are not related to the npm PR content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. needs-ci PRs that need a full CI run. npm Issues and PRs related to the npm client dependency or the npm registry. v26.x Issues that can be reproduced on v26.x or PRs targeting the v26.x-staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants