Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update dependency uuid to v11 #677

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update dependency uuid to v11 #677

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
uuid 9.0.1 -> 11.0.3 age adoption passing confidence

Release Notes

uuidjs/uuid (uuid)

v11.0.3

Compare Source

Bug Fixes

v11.0.2

Compare Source

Bug Fixes

v11.0.1

Compare Source

Bug Fixes

v11.0.0

Compare Source

⚠ BREAKING CHANGES
  • refactor v1 internal state and options logic (#​780)
  • refactor v7 internal state and options logic, fixes #​764 (#​779)
  • Port to TypeScript, closes #​762 (#​763)
  • update node support matrix (only support node 16-20) (#​750)
  • This library always aims at supporting one EOLed LTS release which by this time now is 12.x which has reached EOL 30 Apr 2022.
  • Remove the minified UMD build from the package.
  • Drop support for browsers that don't correctly implement const/let and default arguments, and no longer transpile the browser build to ES2015.
  • Although in practice this is currently a noop since the resulting build does not change, the build will no longer transpiles future changes for Node.js 8.x targets, so semantically this is still a breaking change.
  • Deep requiring specific algorithms of this library like require('uuid/v4'), which has been deprecated in uuid@7, is no longer supported.
  • The default export, which used to be the v4() method but which was already discouraged in v3.x of this library, has been removed.
  • Explicitly note that deep imports of the different uuid version functions are deprecated and no longer encouraged and that ECMAScript module named imports should be used instead. Emit a deprecation warning for people who deep-require the different algorithm variants.
  • Remove builtin support for insecure random number generators in the browser. Users who want that will have to supply their own random number generator function.
  • Remove support for generating v3 and v5 UUIDs in Node.js<4.x
  • Convert code base to ECMAScript Modules (ESM) and release CommonJS build for node and ESM build for browser bundlers.
Features
Bug Fixes
Performance Improvements
Documentation
Miscellaneous Chores
Build System

v10.0.0

Compare Source

⚠ BREAKING CHANGES
  • update node support (drop node@12, node@14, add node@20) (#​750)
Features
Bug Fixes

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 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 Renovate
Copy link
Contributor Author

renovate bot commented Oct 28, 2024 •
edited
Loading

⚠️ 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: [email protected]
npm error Found: [email protected]
npm error node_modules/uuid
npm error   dev uuid@"11.0.3" 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 [email protected]
npm error node_modules/vis-data
npm error   dev vis-data@"7.1.9" from the root project
npm error   peer vis-data@"^6.3.0 || ^7.0.0" from [email protected]
npm error   node_modules/vis-graph3d
npm error     dev vis-graph3d@"6.0.6" from the root project
npm error   2 more (vis-network, vis-timeline)
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/uuid
npm error   peer uuid@"^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0" from [email protected]
npm error   node_modules/vis-data
npm error     dev vis-data@"7.1.9" from the root project
npm error     peer vis-data@"^6.3.0 || ^7.0.0" from [email protected]
npm error     node_modules/vis-graph3d
npm error       dev vis-graph3d@"6.0.6" from the root project
npm error     2 more (vis-network, 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-11-11T02_08_19_189Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-11T02_08_19_189Z-debug-0.log

@renovate renovate bot force-pushed the renovate/uuid-11.x branch 2 times, most recently from 51b63bc to 720de3e Compare October 30, 2024 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants