Skip to content

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

Closed
renovate[bot] wants to merge 2 commits into
devfrom
renovate/npm-12.x
Closed

chore(deps): update npm to v12#1778
renovate[bot] wants to merge 2 commits into
devfrom
renovate/npm-12.x

Conversation

@renovate

@renovate renovate Bot commented Sep 4, 2026

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) 11.9.0 → 12.0.2 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

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

v11.10.1

Compare Source

Bug Fixes
Documentation
Dependencies
Chores

v11.10.0

Compare Source

Features

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Asia/Almaty)

  • Branch creation
    • "on friday"
  • 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 commented Sep 4, 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: examples/with-nextjs/package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: arkenv-example-with-nextjs@undefined
npm warn Found: next@16.3.3
npm warn node_modules/next
npm warn   next@"^16.3.4" from the root project
npm warn   1 more (@arkenv/nextjs)
npm warn
npm warn Could not resolve dependency:
npm warn peer next@"^13.4.0 || ^14.0.0 || ^15.0.0 || ^16.0.0-0" from @arkenv/nextjs@0.1.5
npm warn node_modules/@arkenv/nextjs
npm warn   @arkenv/nextjs@"^0.1.5" from the root project
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @arkenv/nextjs@0.1.5
npm error Found: react@19.2.8
npm error node_modules/react
npm error   react@"^19.2.8" from the root project
npm error   peer react@"^19.2.8" from react-dom@19.2.8
npm error   node_modules/react-dom
npm error     react-dom@"^19.2.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"19.2.5" from @arkenv/nextjs@0.1.5
npm error node_modules/@arkenv/nextjs
npm error   @arkenv/nextjs@"^0.1.5" from the root project
npm error
npm error Conflicting peer dependency: react@19.2.5
npm error node_modules/react
npm error   peer react@"19.2.5" from @arkenv/nextjs@0.1.5
npm error   node_modules/@arkenv/nextjs
npm error     @arkenv/nextjs@"^0.1.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-04T07_04_48_567Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-04T07_04_48_567Z-debug-0.log
File name: examples/with-nextjs-strict/package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: arkenv-example-with-nextjs-strict@undefined
npm warn Found: next@16.3.3
npm warn node_modules/next
npm warn   next@"^16.3.4" from the root project
npm warn   1 more (@arkenv/nextjs)
npm warn
npm warn Could not resolve dependency:
npm warn peer next@"^13.4.0 || ^14.0.0 || ^15.0.0 || ^16.0.0-0" from @arkenv/nextjs@0.1.5
npm warn node_modules/@arkenv/nextjs
npm warn   @arkenv/nextjs@"^0.1.5" from the root project
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @arkenv/nextjs@0.1.5
npm error Found: react@19.2.8
npm error node_modules/react
npm error   react@"^19.2.8" from the root project
npm error   peer react@"^19.2.8" from react-dom@19.2.8
npm error   node_modules/react-dom
npm error     react-dom@"^19.2.8" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"19.2.5" from @arkenv/nextjs@0.1.5
npm error node_modules/@arkenv/nextjs
npm error   @arkenv/nextjs@"^0.1.5" from the root project
npm error
npm error Conflicting peer dependency: react@19.2.5
npm error node_modules/react
npm error   peer react@"19.2.5" from @arkenv/nextjs@0.1.5
npm error   node_modules/@arkenv/nextjs
npm error     @arkenv/nextjs@"^0.1.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-04T07_04_52_682Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-04T07_04_52_682Z-debug-0.log

@changeset-bot

changeset-bot Bot commented Sep 4, 2026 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 73819a2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions Bot added the example Issues or Pull Requests concerning at least one ArkEnv example. (Found in the `examples/` directory) label Sep 4, 2026
@renovate

renovate Bot commented Sep 4, 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.

@yamcodes yamcodes mentioned this pull request Sep 4, 2026
Merged
4 tasks
yamcodes added a commit that referenced this pull request Sep 4, 2026
@yamcodes @autofix-ci
fix(examples): stop Renovate/sync packageManager loop (#1786)
a3ca71f 
## Summary

Breaks the Renovate ↔ `sync-examples` empty-PR loop that produced #1774
and #1778.

### What was happening
1. Renovate bumped `packageManager` in generated
`examples/*/package.json` (e.g. npm 11.9.0 → 12.0.2).
2. `sync-examples` regenerated those files from playgrounds via
`scripts/sync-lib/transform.js`, which hardcoded `npm@11.9.0`.
3. The net PR became empty / merge no-op’d; Renovate reopened the same
bump.

### Fix
1. **Catalog is SoT** — `pnpm-workspace.yaml` catalog now includes `npm:
12.0.2` and `pnpm: 11.24.0` (alongside existing `bun`).
2. **`transform.js`** reads `catalog[packageManager]` and **throws** if
the key is missing (no silent hardcoded fallback).
3. **Renovate** ignores `npm` / `pnpm` / `bun` under `examples/**`
(generated). Also dropped `examples/**` from the pnpm automerge group;
catalog (`pnpm-workspace.yaml`) stays in that group so intentional bumps
still group/automerge.
4. Regenerated example `packageManager` values are `npm@12.0.2` for npm
examples.

### Closing #1778
After this merges into `dev`, close #1778 — Renovate should stop
reopening empty packageManager bumps for generated examples. Catalog
bumps remain the path to ship newer npm/pnpm/bun for examples.

## Test plan
- [ ] `pnpm test` (includes `scripts/sync-lib/transform.test.js`)
- [ ] `pnpm sync:examples:check` passes on this branch
- [ ] Confirm npm examples show `"packageManager": "npm@12.0.2"`
- [ ] After merge, close #1778

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
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

example Issues or Pull Requests concerning at least one ArkEnv example. (Found in the `examples/` directory)

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants