Update dependency vis-data to v7.1.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vis-data (source)	7.0.0 → 7.1.10

---

Release Notes

visjs/vis-data (vis-data)

v7.1.10

Compare Source

Bug Fixes

• deps: allow uuid ^10 and ^11 (77010fd)

v7.1.9

Compare Source

Bug Fixes

• deps: update dependency component-emitter to v2 (#​1126) (254eb5e)

v7.1.8

Compare Source

Bug Fixes

• deps: regenerate package lock (#​1118) (d285783)

v7.1.7

Compare Source

Bug Fixes

• deps: update dependency vis-dev-utils to v4.0.33 (#​1042) (c98c408)

v7.1.6

Compare Source

Bug Fixes

• deps: update dependency uuid to v9 (#​982) (8f6838a)

v7.1.5

Compare Source

Bug Fixes

• deps: allow v9 of uuid (#​999) (2576178)
• deps: synchronize peer dep versions across packages (#​1027) (1d4b2fc)
• types: typescript 4.8 compatibility (fefb552)

v7.1.4

Compare Source

Bug Fixes

• deps: update all (#​869) (1386454)

v7.1.3

Compare Source

Bug Fixes

• deps: update to Vis Dev Utils 3 (#​858) (2a0d959)

v7.1.2

Compare Source

Bug Fixes

• deps: update Vis Util (#​613) (5e52309)

v7.1.1

Compare Source

Bug Fixes

• build: switch back to soft privacy (#​544) (e32909c)

v7.1.0

Compare Source

Features

• add structural Data Set and Data View checks (#​498) (8d21364)

v7.0.1

Compare Source

Bug Fixes

• use #props instead of underscore convention (#​500) (25a4762)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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 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.

[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 WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: vis-network-react@1.3.6
npm ERR! Found: vis-util@4.3.4
npm ERR! node_modules/vis-util
npm ERR!   vis-util@"4.3.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vis-util@"^5.0.1" from vis-data@7.1.9
npm ERR! node_modules/vis-data
npm ERR!   vis-data@"7.1.9" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/c560eb/8be873/cache/others/npm/_logs/2023-11-24T18_12_25_962Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/c560eb/8be873/cache/others/npm/_logs/2023-11-24T18_12_25_962Z-debug-0.log