chore(deps-dev): bump the development-dependencies group with 3 updates

[dependabot]

Bumps the development-dependencies group with 3 updates: lerna, lint-staged and snyk.

Updates lerna from 8.1.7 to 8.1.8

Release notes

Sourced from lerna's releases.

v8.1.8

8.1.8 (2024-08-05)

Bug Fixes

• publish: upgrade @​npmcli/arborist to 7.5.4 (#4058) (89de0eb)
• version: truncate release body based on maximum size allowed by VCS client (#4041) (3c2a3c9)

Features

• publish: enable throttling when publishing modules (#4013) (fccca12)

Changelog

Sourced from lerna's changelog.

8.1.8 (2024-08-05)

Bug Fixes

• publish: upgrade @​npmcli/arborist to 7.5.4 (#4058) (89de0eb)

Commits

• 0343c31 chore(misc): publish 8.1.8
• 3cd9bc9 chore: update e2e-repair snapshots with new output (#4059)
• 89de0eb fix(publish): upgrade @​npmcli/arborist to 7.5.4 (#4058)
• See full diff in compare view

Updates lint-staged from 15.2.7 to 15.2.8

Release notes

Sourced from lint-staged's releases.

v15.2.8

Patch Changes

• f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

  The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

Changelog

Sourced from lint-staged's changelog.

15.2.8

Patch Changes

• f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

  The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

Commits

• 52f6eef chore(changeset): release (#1462)
• 8d8fe23 build: update repository url in package.json
• f0480f0 Revert "chore(changeset): release (#1461)"
• 1da81c0 chore(changeset): release (#1461)
• cc04e08 ci: add required permission for provenance generation
• fa2dac8 Revert "chore(changeset): release (#1455)"
• 8325985 chore(changeset): release (#1455)
• 92f295f build(deps): update dependencies (#1460)
• 5293c09 build: generate provenance statements for npm package (#1459)
• f184fff Merge pull request #1454 from Falcion/master
• Additional commits viewable in compare view

Updates snyk from 1.1292.1 to 1.1292.2

Release notes

Sourced from snyk's releases.

v1.1292.2

1.1292.2 (2024-08-01)

The Snyk CLI is being deployed to different deployment channels, users can select the stability level according to their needs. For details please see this documentation

Complete changelog

Bug Fixes

• container test: Improve the accuracy of identifying npm projects within docker images by removing the explicit folder ignore rules (#5384)
• container test: Pass platform parameter when pulling an image from a container registry (#5360)

Commits

• c8fa39f Merge pull request #5389 from snyk/tmp/hotfix-UNIFY-216
• d76a419 docs: update release notes
• 9af7971 Merge pull request #5384 from snyk/hotfix/v1.1292.0-container-remove-ignored-...
• c498b46 fix: make dotnet acceptance test resilient to system lib vulns
• 8164ad8 fix: remove ignored paths when discovering npm manifests UNIFY-216
• 39f308a Merge pull request #5351 from snyk/chore/update_rc
• See full diff 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

[changeset-bot]

⚠️ No Changeset found

Latest commit: b6c3e25

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR