Skip to content

chore(deps): update dependency npm to v12 - #443

Merged
GraemeF merged 1 commit into
mainfrom
renovate/npm-12.x
Oct 19, 2026
Merged

GraemeF merged 1 commit into
mainfrom
renovate/npm-12.x

Conversation

@renovate

@renovate renovate Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
npm (source) 11.21.1 → 12.2.0 age confidence

Release Notes

npm/cli (npm)

v12.2.0

Compare Source

Features
Documentation
Dependencies

v12.1.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v12.0.2

Compare Source

Bug Fixes
Documentation
Chores
Dependencies

v12.0.1

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v12.0.0

Compare Source

⚠️ 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.
  • 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 CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning. (Unknown .npmrc configs still warn by default; opt into erroring with the new strict-npmrc config.)
  • Dependency lifecycle scripts are now blocked by default unless allowed by the root package's allowScripts policy. After installing, run npm install-scripts approve to record approvals and npm rebuild to execute newly approved scripts.
Chores
Dependencies

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@sonarqubecloud

Copy link
Copy Markdown

@GraemeF

GraemeF commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

Review: npm 11.21.1 → 12.2.0 (major)

npm is a root dev dependency. It is on PATH through node_modules/.bin, so changeset publish in the release workflows runs this npm. Nothing else in the repo calls it; installs go through Bun.

Age: 12.2.0 was published on 2026-09-30, well past three days.

Breaking changes in 12.0.0 and why each is safe here:

  • npm view/npm info --json now always returns an array. This broke published-version detection in older @changesets/cli. The repo is on @changesets/cli 3.0.3, whose parseInfoResult unwraps the array.
  • npm pack/npm publish --json output changed. @changesets/cli 3.0.3 reads the tarball filename from either shape.
  • Node ^22.22.2 || ^24.15.0 || >=26. The ubuntu-24.04 runner image the release jobs use ships Node 22.23.3.
  • Unknown .npmrc keys now throw. The repo has no .npmrc. The manual publish workflow writes only the standard _authToken key.
  • Dependency lifecycle scripts blocked by default, allow-git/allow-remote default to none, root preinstall ordering. These apply to npm install, which this repo does not use.
  • Removed commands (shrinkwrap, adduser, star), npm pkg output, npm init licence default, sbom naming, man pages, whichnode. None is used.

12.0.1 to 12.2.0 add OIDC support to dist-tag, staged-package status and granular token types, and fix bugs. Trusted publishing through OIDC is unchanged.

CI is green. CI does not run a publish, so the first real check of the publish path is the next release. If it fails there, the remedy is to revert this bump.

@GraemeF
GraemeF merged commit d389f67 into main Oct 19, 2026
3 checks passed
@GraemeF
GraemeF deleted the renovate/npm-12.x branch October 19, 2026 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant