FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

deps: upgrade npm to 11.19.0 by npm-cli-bot · Pull Request #64885 · nodejs/node · GitHub

/ node Public

deps: upgrade npm to 11.19.0 - #64885

Closed
npm-cli-bot wants to merge 1 commit into
nodejs:v24.x-stagingfrom
npm:npm-v11.19.0-24
Closed

deps: upgrade npm to 11.19.0#64885
npm-cli-bot wants to merge 1 commit into
nodejs:v24.x-stagingfrom
npm:npm-v11.19.0-24

Conversation

Copy link
Copy Markdown
Contributor

This PR contains changes from: npm@11.18.0 npm@11.19.0


11.18.0

11.18.0 (2026-06-29)

Features

Bug Fixes

Documentation

Dependencies

Chores

arborist: 9.9.0

9.9.0 (2026-06-29)

Features

Bug Fixes

config: 10.12.0

10.12.0 (2026-06-29)

Features

Bug Fixes

Documentation

libnpmdiff: 8.1.11

Dependencies

libnpmexec: 10.3.1

10.3.1 (2026-06-29)

Bug Fixes

Dependencies

libnpmfund: 7.0.25

Dependencies

libnpmpack: 9.1.11

Dependencies

11.19.0

11.19.0 (2026-07-28)

Features

Bug Fixes

Dependencies

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/security-wg

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. v24.x Issues that can be reproduced on v24.x or PRs targeting the v24.x-staging branch. labels Jul 31, 2026
MikeMcC399 added the request-ci Add this label to start a Jenkins CI on a PR. label Aug 1, 2026
github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 1, 2026

Copy link
Copy Markdown
Collaborator

avivkeller added the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Aug 1, 2026

Copy link
Copy Markdown
Collaborator

aduh95 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Why does this target v24.x-staging instead of main?

Copy link
Copy Markdown
Contributor

Why does this target v24.x-staging instead of main?

How would that work if #64882 proposes to land npm@12.0.2 into main?

aduh95 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Ideally 11.19.0 should land on main before 12.0.2 – if #64882 lands first, we would still want the PR against v26.x-staging, not v24.x-staging

Copy link
Copy Markdown
Contributor

@reggi who triggered these releases also opened a Slack thread https://openjs-foundation.slack.com/archives/C019Y2T6STH/p1785531468429629 so it may be easier to sort out the strategy with her in Slack.

Copy link
Copy Markdown
Member

Ideally 11.19.0 should land on main before 12.0.2 – if #64882 lands first, we would still want the PR against v26.x-staging, not v24.x-staging

The PR for v26.x-staging is #64883. That should be land cleanly on v24.x-staging if npm 11.18.0 is cherry-picked first.

MikeMcC399 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

This PR goes against https://github.com/nodejs/node/blob/main/doc/contributing/backporting-to-release-lines.md#criteria-for-backporting

The "Current" release line is more flexible than LTS lines. LTS branches, detailed in the Release Plan, require commits to mature in the Current release for at least two weeks before backporting.

MikeMcC399 removed the author ready PRs that have at least one approval, no outstanding review comments, and a CI started. label Aug 4, 2026

Copy link
Copy Markdown
Member

Superseded by #64883.

Renegade334 closed this Aug 4, 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

Labels

needs-ci PRs that need a full CI run. npm Issues and PRs related to the npm client dependency or the npm registry. v24.x Issues that can be reproduced on v24.x or PRs targeting the v24.x-staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants


Back | FazBrowse Home | New Git URL