chore(deps): update dependency lerna to v9

[renovate]

Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.

This PR contains the following updates:

Package	Change	Age	Confidence
lerna (source)	8.2.4 -> 9.0.0

---

Release Notes

lerna/lerna (lerna)

v9.0.0

Compare Source

Bug Fixes

• publish: ensure README file names are populated on package.json (#​4211) (362875d)

Features

• support OIDC trusted publishing (d51e344)

OIDC trusted publishing is now supported by Lerna with no specification configuration required.

• A new guide has been added: https://lerna.js.org/docs/recipes/oidc-trusted-publishing
• A fully working example repo has been set up here https://github.com/JamesHenry/lerna-v9-oidc-publishing-example

BREAKING CHANGES

After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.

As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.

• node v18 support is dropped because it is end of life

When a node version becomes end of life (EOL) it means that it does not receive any updates or maintenance whatsoever, even if critical security vulnerabilities have been uncovered.

We strongly encourage all folks here to keep up with the maintenance LTS version of Node at an absolute minimum:

https://github.com/nodejs/release#release-schedule

The versions of node supported by lerna are now ^20.19.0 || ^22.12.0 || >=24.0.0.

• The @​lerna/legacy-package-management package has been formally removed after 2 years of deprecation.

If you are still using lerna add, lerna bootstrap or lerna link commands, please migrate to using your package manager's long-supported workspaces feature. The updated guide should help with this https://lerna.js.org/docs/legacy-package-management**

8.2.4 (2025-07-27)

Bug Fixes

• remove all remaining lodash usage (#​4207) (8211512)

8.2.3 (2025-06-29)

Bug Fixes

• use internal fork of unmaintained strong-log-transformer (#​4195) (7115485)

8.2.2 (2025-04-10)

Note: Version bump only for package lerna

8.2.1 (2025-03-03)

Note: Version bump only for package lerna

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/ts-morph
npm error   dev ts-morph@"27.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional ts-morph@"^20.0.0 || ^21.0.0 || ^24.0.0 || ^25.0.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/graphql
npm error   dev @nestjs/graphql@"13.1.0" from the root project
npm error   peer @nestjs/graphql@"^13.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"13.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/ts-morph
npm error   peerOptional ts-morph@"^20.0.0 || ^21.0.0 || ^24.0.0 || ^25.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/graphql
npm error     dev @nestjs/graphql@"13.1.0" from the root project
npm error     peer @nestjs/graphql@"^13.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"13.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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/2025-09-24T00_05_31_667Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-24T00_05_31_667Z-debug-0.log

[coveralls]

Pull Request Test Coverage Report for Build 1dd8c027-bb24-439b-8859-e1e35af8e890

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 88.687%

---

Totals
Change from base Build 9124a2fe-bca5-42ba-b470-5a231493d02b:	0.0%
Covered Lines:	7275
Relevant Lines:	8203

---

💛 - Coveralls

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.