Skip to content

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

Merged
Betree merged 4 commits into
mainfrom
renovate/npm-12.x
Sep 16, 2026
Merged

Betree merged 4 commits into
mainfrom
renovate/npm-12.x

Conversation

@renovate

@renovate renovate Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
npm (source) 11.x → 12.x age confidence

Release Notes

npm/cli (npm)

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekday after 2:00 am before 6:00 am,every weekend"
  • 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.

@Betree

Betree commented Sep 7, 2026

Copy link
Copy Markdown
Member

@cursor update the project for npm 12

@cursor

cursor Bot commented Sep 7, 2026 •

Copy link
Copy Markdown

Updated the project for npm 12. Renovate had bumped engines.npm to 12.x, but CI was still running npm 11.19.0, which caused EBADENGINE failures with engine-strict=true.

Root cause

CI uses Node 24 with bundled npm 11. After the engines bump, npm ci failed immediately because .npmrc has engine-strict=true.

Changes made

  1. package.json — Added packageManager pinning npm@12.0.2 (with integrity hash from corepack).
  2. .github/workflows/ci.yml and e2e.yml — Added an "Enable npm 12" step (npm install -g npm@12.0.2) after setup-node in all jobs.
  3. README.md — Updated the prerequisite from npm 11.x to 12.x.

Verification

Tested locally with npm 12.0.2:

  • npm ci (with OC_ENV=ci) — passes
  • npm run lint:check — passes
  • npm run type:check — passes
  • npm run build — passes

For local development, upgrade with npm install -g npm@12 or use corepack with the new packageManager field.

Open in Web Open in Cursor 

- Add packageManager field pinning npm@12.0.2
- Install npm 12 in CI before npm ci to satisfy engine-strict
- Update README prerequisite to npm 12.x

Fixes CI EBADENGINE failures after engines.npm was bumped to 12.x.
@renovate

renovate Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@Betree

Betree commented Sep 7, 2026

Copy link
Copy Markdown
Member

@cursor schema update job is failing

@cursor

cursor Bot commented Sep 7, 2026 •

Copy link
Copy Markdown

The schema-update job was failing because npm 12 rejects unknown config flags. The config.commitizen.path field in package.json was being passed as --commitizen_path, which npm 12 treats as an error (EUNKNOWNCONFIG) instead of ignoring it like npm 11 did.

Fix

  • Moved commitizen configuration to a new .czrc file
  • Removed the config block from package.json

npm run graphql:update (used by scripts/check-schemas.sh) works again with npm 12.

Verification

  • Locally: npx npm-run-all graphql:updateV1 no longer throws EUNKNOWNCONFIG
  • CI: schema-update passed on the new run (1m22s)

Commit: fix: move commitizen config out of package.json for npm 12

Open in Web Open in Cursor 

npm 12 throws EUNKNOWNCONFIG for package.json config fields like
commitizen.path. Move the configuration to .czrc so npm-run-all and
graphql:update work in CI again.
@Betree

Betree commented Sep 7, 2026

Copy link
Copy Markdown
Member

@cursor depcheck now failing

@cursor

cursor Bot commented Sep 7, 2026 •

Copy link
Copy Markdown

The depcheck failure was a side effect of the commitizen config move for npm 12.

Root cause

After moving commitizen config from package.json to .czrc, depcheck no longer saw cz-conventional-changelog as used. Its commitizen special only reads config.commitizen in package.json, so it reported the adapter as an unused devDependency.

Fix

Added cz-conventional-changelog to the @opencollective/depcheck ignores in package.json, since it's still required via .czrc.

Verification

  • Locally: npm run depcheck → No depcheck issue
  • CI: depcheck passed (31s) on the new run
Open in Web Open in Cursor 

Depcheck's commitizen special only reads package.json config.commitizen.
After moving commitizen config to .czrc for npm 12 compatibility, mark the
adapter as an intentional devDependency.
@Betree
Betree merged commit e4dc077 into main Sep 16, 2026
20 checks passed
@Betree
Betree deleted the renovate/npm-12.x branch September 16, 2026 09:29
znarf added a commit that referenced this pull request Sep 16, 2026
* Revert "chore(deps): update npm to v12 (#12073)"

This reverts commit e4dc077.

* chore(Renovate): keep npm on the version bundled with Node

No Node release bundles npm 12 (nodejs/node#64882 was closed), so a
12.x engine pin forces every environment to install npm on top of Node
for the life of the LTS. Stay on the bundled major and stop Renovate
from proposing the next one.
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.

2 participants