chore(deps): update dependency uuid to v10 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
uuid	^7.0.0 || ^9.0.0 -> ^7.0.0 || ^9.0.0 || ^10.0.0
uuid	^9.0.0 -> ^10.0.0

---

Release Notes

uuidjs/uuid (uuid)

v10.0.0

Compare Source

⚠ BREAKING CHANGES

• update node support (drop node@12, node@14, add node@20) (#​750)

Features

• support support rfc9562 MAX uuid (new in RFC9562) (#​714) (0385cd3)
• support rfc9562 v6 uuids (#​754) (c4ed13e)
• support rfc9562 v7 uuids (#​681) (db76a12)
• update node support matrix (only support node 16-20) (#​750) (883b163)
• support rfc9562 v8 uuids (#​759) (35a5342)

Bug Fixes

• revert "perf: remove superfluous call to toLowerCase (#​677)" (#​738) (e267b90)

---

Configuration

📅 Schedule: 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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: vis-data@7.1.9
npm error Found: uuid@10.0.0
npm error node_modules/uuid
npm error   dev uuid@"^10.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer uuid@"^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0" from vis-data@7.1.9
npm error node_modules/vis-data
npm error   dev vis-data@"^7.1.0" from the root project
npm error   peer vis-data@"^6.3.0 || ^7.0.0" from vis-network@9.1.9
npm error   node_modules/vis-network
npm error     vis-network@"~9.1.7" from the root project
npm error   1 more (vis-timeline)
npm error
npm error Conflicting peer dependency: uuid@9.0.1
npm error node_modules/uuid
npm error   peer uuid@"^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0" from vis-data@7.1.9
npm error   node_modules/vis-data
npm error     dev vis-data@"^7.1.0" from the root project
npm error     peer vis-data@"^6.3.0 || ^7.0.0" from vis-network@9.1.9
npm error     node_modules/vis-network
npm error       vis-network@"~9.1.7" from the root project
npm error     1 more (vis-timeline)
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 /tmp/renovate/cache/others/npm/_logs/2024-07-09T04_03_20_694Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-09T04_03_20_694Z-debug-0.log