Skip to content

deps: upgrade npm to 11.18.0#64199

Open
npm-cli-bot wants to merge 1 commit into
nodejs:mainfrom
npm:npm-v11.18.0-main
Open

deps: upgrade npm to 11.18.0#64199
npm-cli-bot wants to merge 1 commit into
nodejs:mainfrom
npm:npm-v11.18.0-main

Conversation

@npm-cli-bot

Copy link
Copy Markdown
Contributor

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

@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. labels Jun 29, 2026
@richardlau richardlau added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 30, 2026
@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jun 30, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@richardlau

Copy link
Copy Markdown
Member

This will need a rebase to fix the CI failures.

@MikeMcC399

Copy link
Copy Markdown
Contributor

This will need a rebase to fix the CI failures.

Is it too late to get the rebase done and landed before the Node.js 26.5.0 release?

@manzoorwanijk

Copy link
Copy Markdown

The last lone maintainer of npm CLI is no longer at GitHub, and I don’t see anyone else being assigned yet. So, this may take longer to get rebased.

@reggi

reggi commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

The last lone maintainer of npm CLI is no longer at GitHub, and I don’t see anyone else being assigned yet. So, this may take longer to get rebased.

star-wars-yoda

✌️ I'm Tea I work on npm

@richardlau richardlau added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 7, 2026
@richardlau

Copy link
Copy Markdown
Member

Is it too late to get the rebase done and landed before the Node.js 26.5.0 release?

I've restarted the CI for this PR, but am making no promises about getting this into the 26.5.0 release.

My intention for 26.5.0 was to start release builds tonight before I go to sleep so I can do the release tomorrow during my working hours (the worst case build time (which I don't know if we'll hit) is ~7 hours). We're past my work hours today so if I did try to get the npm release into 26.5.0 I'd have to give up a chunk of my evening to:

  • Check the CI for this PR has passed (restarting for any flakes)
  • Merge this PR
  • Update the release proposal
  • Rerun CI for the release proposal

The good news for Node.js 26 is that we do current releases fairly often, so it should not be too long before the next release.

@manzoorwanijk

Copy link
Copy Markdown

I'm Tea I work on npm

Oh, that’s great. Thank you for the info. Looking forward to collaborating more on npm.

@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 7, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants