Skip to content

chore(deps): update dependency lerna to v10 - #1068

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-lerna-monorepo
Open

chore(deps): update dependency lerna to v10#1068
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-lerna-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
lerna (source) 9.0.710.0.0 age confidence

Release Notes

lerna/lerna (lerna)

v10.0.0

Compare Source

Bug Fixes
Features
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

9.0.5 (2026-02-28)

Bug Fixes

9.0.4 (2026-02-10)

Bug Fixes

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

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.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedlerna@​10.0.0921008191100

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm nx is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/lerna@10.0.0npm/nx@23.1.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/nx@23.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant