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

deps: upgrade npm to 12.0.0-pre.1 by npm-cli-bot · Pull Request #64096 · nodejs/node · GitHub

/ node Public

deps: upgrade npm to 12.0.0-pre.1 - #64096

Closed
npm-cli-bot wants to merge 1 commit into
nodejs:mainfrom
npm:npm-v12.0.0-pre.1-main
ConversationCommits (1)ChecksFiles changed
Closed

deps: upgrade npm to 12.0.0-pre.1#64096
npm-cli-bot wants to merge 1 commit into
nodejs:mainfrom
npm:npm-v12.0.0-pre.1-main

Conversation

npm-cli-bot commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains changes from: npm@12.0.0-pre.0.0 npm@12.0.0-pre.1

12.0.0-pre.0.0

12.0.0-pre.0.0 (2026-05-20)

⚠️ BREAKING CHANGES

  • npm view --json now always returns an array.
  • npm sbom --sbom-format=cyclonedx now reports the name field from each package's package.json instead of the on-disk directory name. The name, bom-ref, and purl of the root component and of aliased dependencies may change.
  • npm no longer registers man pages with the system when installed globally. man npm-install will no longer work, but npm help install is unaffected.
  • The npm pkg output is no longer forced to json. This means you can get single values without having to worry about wrapping of the values. It also outputs non-json content more similarly to npm view.
  • npm shrinkwrap is removed, the shrinkwrap config alias is removed, and npm-shrinkwrap.json is no longer loaded or honored at the project root or from inside dependency tarballs. Rename project-root npm-shrinkwrap.json to package-lock.json; use bundleDependencies if you need to ship a locked dependency tree.
  • The Twitter and Freenode profile fields have been removed from the npm registry. This means that users will no longer be able to set or view these fields in their npm profiles.
  • npm will no longer attempt to resolve the path to node via whichnode. process.execPath is already set by Node to the resolved real path of the node binary, so the lookup was redundant. Scripts that expected npm to override process.execPath with a PATH-resolved (potentially symlinked) node path may be affected.
  • the --json output of npm pack and npm publish have changed. They are now always consistent, and in the same format.
  • the star, stars and unstar commands have been removed
  • The npm adduser command has been removed. Create and manage user accounts on the npm website, and use npm login to authenticate on the command line.

Features

Bug Fixes

Documentation

Dependencies

Chores

12.0.0-pre.1

12.0.0-pre.1 (2026-06-19)

⚠️ BREAKING CHANGES

  • Preserve https protocol when working with git (#8703)
  • The default license for npm init has been changed from "ISC" to an empty string. If not set, the license field will be omitted from new packages.
  • npm now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • allow-git and allow-remote now default to "none"; set them to "all" (or "root") to install git or user-supplied tarball-URL dependencies.
  • root `preinstall` now runs before dependencies are installed.
  • unknown configs in .npmrc, unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning.

Features

Bug Fixes

Documentation

Dependencies

Chores

nodejs-github-bot commented Jun 23, 2026

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. labels Jun 23, 2026

owlstronaut commented Jun 23, 2026

Copy link
Copy Markdown

NOT FOR MERGING

CI Test only

JamieMagee commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

See nodejs/Release#1161

JamieMagee mentioned this pull request Jun 23, 2026
Closed
Renegade334 added the blocked PRs that are blocked by other issues or PRs. label Jun 23, 2026

This comment was marked as outdated.

Sign in to view

JamieMagee commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

@Renegade334 is it possible to close this PR please? We'll open a new one shortly with the release of npm 12.

MikeMcC399 commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

@JamieMagee

We'll open a new one shortly with the release of npm 12.

Are you going ahead with a PR for npm 12.0.1 or are you waiting for some fixes and a new release before proceeding here?

npm 12.0.0 was released on Jul 8, 2026
npm 12.0.1 was released on Jul 10. 2026

JamieMagee commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@MikeMcC399 we're planning to open a new PR with 12.0.2 later this week.

MikeMcC399 commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

would also be appreciated as PRs!

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
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

blocked PRs that are blocked by other issues or PRs. 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

Back | FazBrowse Home | New Git URL