Skip to content

chore(deps): update npm to v12 - #56

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-12.x
Open

chore(deps): update npm to v12#56
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-12.x

Conversation

@renovate

@renovate renovate Bot commented Jul 20, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
npm (source) ^8.19.4 → ^12.1.0 age confidence

Release Notes

npm/cli (npm)

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

Bug Fixes
Dependencies

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 configs in .npmrc, unknown CLI flags, abbreviated flags, and single-hyphen multi-char shorthands now throw instead of warning.
Chores
Dependencies

v11.20.0

Compare Source

v11.19.1

Compare Source

v11.19.0

Compare Source

v11.18.0

Compare Source

v11.17.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v11.16.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies
Chores

v11.15.0

Compare Source

Features
Bug Fixes
Dependencies
Chores

v11.14.1

Compare Source

Bug Fixes

v11.14.0

Compare Source

Features
Bug Fixes
Dependencies
Chores

v11.13.0

Compare Source

Features
Bug Fixes
Dependencies
Chores

v11.12.1

Compare Source

Bug Fixes
Documentation
Dependencies

v11.12.0

Compare Source

Features
Bug Fixes
Dependencies
Chores

v11.11.1

Compare Source

Bug Fixes
Documentation
Dependencies
Chores

v11.11.0

Compare Source

Features
Bug Fixes
Documentation
Dependencies

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "after 6am and before 10am on monday"
  • 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.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Jul 20, 2026
@renovate
renovate Bot force-pushed the renovate/npm-12.x branch from 0111072 to 494bd56 Compare July 30, 2026 00:16
@renovate
renovate Bot force-pushed the renovate/npm-12.x branch from 494bd56 to 4d0b2a9 Compare September 16, 2026 00:48
@renovate
renovate Bot force-pushed the renovate/npm-12.x branch from 4d0b2a9 to 842399f Compare September 23, 2026 00:11
@renovate

renovate Bot commented Sep 23, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn cli npm v12.1.0 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
npm error (0 , U.tracingChannel) is not a function
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-23T00_11_06_474Z-debug-0.log
File name: .netlify/functions/ssr/package-lock.json
npm warn cli npm v12.1.0 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
npm error (0 , U.tracingChannel) is not a function
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-23T00_11_07_436Z-debug-0.log
File name: .functions/package-lock.json
npm warn cli npm v12.1.0 does not support Node.js v16.20.2. This version of npm supports the following node versions: `^22.22.2 || ^24.15.0 || >=26.0.0`. You can find the latest version at https://nodejs.org/.
npm error (0 , U.tracingChannel) is not a function
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-23T00_11_08_501Z-debug-0.log

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

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants