chore(deps-dev): bump lerna from 7.4.2 to 8.0.2

[dependabot]

Bumps lerna from 7.4.2 to 8.0.2.

Release notes

Sourced from lerna's releases.

v8.0.2

8.0.2 (2024-01-05)

Bug Fixes

• add-caching: explicitly set targetDefaults for all scripts (#3929) (dae18c9)

v8.0.1

8.0.1 (2023-12-15)

Bug Fixes

• update node-gyp usage to v10 to resolve npm warning (#3919) (f5fdcba)
• version: create correct independent tags when using --sign-git-tag (#3917) (8f7a32b)

v8.0.0

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 v16 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

• lerna's task runner for lerna run now depends on nx v17 instead of v16

lerna run gets to benefit from all of the further performance improvements in the nx v17 task runner behind scenes.

• @lerna/child-process is no longer a separately published package

Lerna is a monorepo management tool with versioning and publishing capabilities, it is not a child process manager. There are lots of good options out there in the ecosystem to help you with managing child processes in nodejs, and it does not really make sense to treat some of lerna's implementation details around child processes as if they were a public API. The package will be officially deprecated on npm in the future. You can of course take the code and fork it and adapt it for your own purposes if you wish!

• Older packages under @lerna/ on npm have been officially marked as deprecated

Under prior stewardship the lerna repo used to publish a very large (>65) number of packages. The vast majority of these should not form part of the public API of lerna and so they have no longer been published as packages since v6. We have now officially marked them as deprecated packages on the npm registry so that users get clear feedback that they are using packages which are no longer maintained (which they can of course fork and do whatever they want with). NOTE: We have not yet marked @lerna/child-process as deprecated so as not to create noise for lerna v7 users until they have had chance to migrate to v8.

Features

• version: add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages (#3876) (3b05947)
• version: use corepack for install when enabled (#3877) (a3cb7ca)

Changelog

Sourced from lerna's changelog.

8.0.2 (2024-01-05)

Bug Fixes

• add-caching: explicitly set targetDefaults for all scripts (#3929) (dae18c9)

8.0.1 (2023-12-15)

Bug Fixes

• update node-gyp usage to v10 to resolve npm warning (#3919) (f5fdcba)

8.0.0 (2023-11-23)

Features

• version: add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages (#3876) (3b05947)

8.0.0-alpha.0 (2023-11-22)

Features

• version: add --premajor-version-bump option to force patch bumps for non-breaking changes in premajor packages (#3876) (3b05947)

Commits

• 4fcac71 chore(misc): publish 8.0.2
• dae18c9 fix(add-caching): explicitly set targetDefaults for all scripts (#3929)
• 5646a45 chore(misc): publish 8.0.1
• f5fdcba fix: update node-gyp usage to v10 to resolve npm warning (#3919)
• 9c71696 chore: update v8 release notes
• b664840 chore(misc): publish 8.0.0
• 32d9f63 chore: fix formatting
• 2ff3705 chore: add missing updates
• 4f5edee feat!: stop publishing @​lerna/child-process (#3909)
• 4445fce chore(run): enable strict type checking (#3907)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[dreamorosi]

Marking this as do-not-merge for the time being since there appear to be breaking changes that might require us to have to tweak the lerna.json config file.

We need to test this locally before merging to make sure everything is working as expected.

[dreamorosi]

I have tested the new version locally and both the version and publish command seem to work as expected.

[dreamorosi]

@dependabot merge