Update dependency lerna to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
lerna (source)	^9.0.1 → ^10.0.0

---

Release Notes

lerna/lerna (lerna)

v10.0.0

Compare Source

• feat!: throw error in case of stale remote for CI mode (#​4369) (3e81682), closes #​4369
• feat!: support node ^22.13.0 || ^24.0.0 || ^26.0.0, ship lerna as ESM-only (#​4390) (a148ba2), closes #​4390
• fix(core)!: replace deprecated conventional-changelog dependencies (#​4332) (b1ff72f), closes #​4332

Bug Fixes

• core: remove p-map-series, p-pipe, p-reduce, and p-waterfall (#​4321) (fe066cb)
• core: remove upath dependency (#​4317) (aa65470)

Features

• core: add bun as supported package manager (#​4264) (4ca7d2c)

BREAKING CHANGES

• In CI, EBEHIND will now be thrown during versioning and publishing if the checkout is behind the latest on the remote. This previously only occurred outside of CI environments.

  If you wish to opt into the old behavior, you can do so by setting --ci-behind-behavior (error | skip, default error) or command.version.ciBehindBehavior in lerna.json.

• Lerna is now shipped as ESM-only and the lowest supported node version has changed to 22.13.0, because on this version CommonJS consumers can still require in its entry points without any additional flags or warnings.

• Lerna now uses the current conventional-changelog APIs instead of the deprecated conventional-changelog-core stack.

  Generated CHANGELOG.md output may differ, including normalized whitespace and URL-encoded tag names. Projects using custom changelog presets should verify their output; Lerna retains compatibility for legacy parser/writer option names and Handlebars string templates.

  CLI options and version-bump behavior remain unchanged.

9.0.7 (2026-03-13)

Bug Fixes

• core: remove multimatch dependency and legacy-core internals (#​4314) (ec01462)

9.0.6 (2026-03-11)

Bug Fixes

• deps: add missing ci-info dependency (#​4263) (b768187)
• deps: bump tar from 7.5.8 to 7.5.11 (#​4296) (7a69a57)

9.0.5 (2026-02-28)

Bug Fixes

• bump minimatch from 3.0.5 to 3.1.4 (#​4285) (2e3f99e)
• bump tar from 7.5.7 to 7.5.8 (#​4273) (bdffd1d)

9.0.4 (2026-02-10)

Bug Fixes

• bump tar to 7.5.7, rimraf to 6.1.2, @​npmcli/run-script to 10.0.3 (#​4267) (43e3d46)

9.0.3 (2025-11-27)

Note: Version bump only for package lerna

9.0.2 (2025-11-27)

Note: Version bump only for package lerna

9.0.1 (2025-11-14)

Bug Fixes

• expand version range to include nx v22.x (#​4242) (0cca286)

v9.0.7

Compare Source

Bug Fixes

• core: remove multimatch dependency and legacy-core internals (#​4314) (ec01462)

v9.0.6

Compare Source

Bug Fixes

• deps: add missing ci-info dependency (#​4263) (b768187)
• deps: bump tar from 7.5.8 to 7.5.11 (#​4296) (7a69a57)

v9.0.5

Compare Source

Bug Fixes

• bump minimatch from 3.0.5 to 3.1.4 (#​4285) (2e3f99e)
• bump tar from 7.5.7 to 7.5.8 (#​4273) (bdffd1d)

v9.0.4

Compare Source

Bug Fixes

• bump tar to 7.5.7, rimraf to 6.1.2, @​npmcli/run-script to 10.0.3 (#​4267) (43e3d46)

v9.0.3

Compare Source

Note: Version bump only for package lerna

v9.0.1

Compare Source

Bug Fixes

• expand version range to include nx v22.x (#​4242) (0cca286)

---

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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact 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 Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-standard@17.1.0
npm error Found: eslint@9.38.0
npm error node_modules/eslint
npm error   dev eslint@"^9.38.0" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.28.5
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"^7.28.5" from the root project
npm error   11 more (@eslint-community/eslint-utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.0.1" from eslint-config-standard@17.1.0
npm error node_modules/eslint-config-standard
npm error   dev eslint-config-standard@"^17.1.0" from the root project
npm error   eslint-config-standard@"17.1.0" from standard@17.1.2
npm error   node_modules/standard
npm error     dev standard@"^17.1.2" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.1
npm error node_modules/eslint
npm error   peer eslint@"^8.0.1" from eslint-config-standard@17.1.0
npm error   node_modules/eslint-config-standard
npm error     dev eslint-config-standard@"^17.1.0" from the root project
npm error     eslint-config-standard@"17.1.0" from standard@17.1.2
npm error     node_modules/standard
npm error       dev standard@"^17.1.2" 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-08-21T04_06_17_452Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-21T04_06_17_452Z-debug-0.log