[Snyk] Security upgrade lerna from 5.6.2 to 8.1.9

[adamlaska]

Snyk has created this PR to fix 5 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-17900054
	Infinite loop SNYK-JS-TAR-17909068
	Incorrect Type Conversion or Cast SNYK-JS-TAR-17909104
	Allocation of Resources Without Limits or Throttling SNYK-JS-TAR-17909152
	Uncaught Exception SNYK-JS-TAR-17909225

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Uncaught Exception

[adamlaska]

This upgrade spans three major versions (v6, v7, v8) and introduces significant breaking changes that will require migration effort. The core philosophy of Lerna has shifted towards leveraging package manager workspaces and the Nx task runner.

Key Breaking Changes:

• v6.0: Caching & Nx by Default:

  • Lerna now uses Nx as its default task runner for improved performance and caching. This changes how tasks are scheduled and executed.
  • Several command-line flags like --parallel, --sort, and --include-dependencies are now obsolete as Nx manages the task graph automatically.

• v7.0: Removal of Legacy Package Management:

  • The bootstrap, add, and link commands have been removed. Users must now rely on their package manager's (npm, yarn, pnpm) built-in workspace features for dependency management.
  • CI/CD scripts using lerna bootstrap must be updated to use npm install, yarn install, or pnpm install.

• v8.0: Node.js Version and Configuration:

  • Support for Node.js v16 has been dropped. The changelog for v9 (the next major version) indicates support for Node.js v18 is also dropped, so users should target v20 or higher.
  • The lerna repair command is introduced to help automatically migrate lerna.json configurations to the latest format.

Recommendation:
This is a high-effort migration. Before merging, developers must:

1. Update CI/CD scripts to replace lerna bootstrap with the package manager's install command (e.g., npm install).
2. Ensure the project is configured to use package manager workspaces (e.g., in package.json).
3. Run lerna repair to update the lerna.json configuration file.
4. Verify that the Node.js version in use is compatible (v18+ recommended).

Source: Lerna Changelog, Legacy Package Management Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.