chore(deps): update dependency uuid to v14#1861
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
0ad7b77 to
c2bed02
Compare
c2bed02 to
b565eba
Compare
PatelUtkarsh
added a commit
that referenced
this pull request
May 12, 2026
The uuid package was used in exactly one place (an E2E test) to generate a unique post title. Node 22 (and all modern browsers) ship crypto.randomUUID() natively, so the dependency is unnecessary. Also unblocks XWPENG-29: uuid v14 dropped CJS exports, which broke eslint-plugin-import's resolver chain (eslint-import-resolver-node 0.3.9 does not understand ESM-only "exports" maps). Removing uuid avoids needing to upgrade the resolver chain. Refs XWPENG-29 Supersedes #1861
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^11.1.1β^14.0.0Release Notes
uuidjs/uuid (uuid)
v14.0.0Compare Source
Security
v3(),v5(), andv6()did not validate that writes would remain within the bounds of a caller-supplied buffer, allowing out-of-bounds writes when an invalidoffsetwas provided. ARangeErroris now thrown ifoffset < 0oroffset + 16 > buf.length.β BREAKING CHANGES
cryptois now expected to be globally defined (requires node@β20+) (#β935)v13.0.2Compare Source
Bug Fixes
v13.0.1Compare Source
Bug Fixes
v13.0.0Compare Source
β BREAKING CHANGES
Bug Fixes
v12.0.1Compare Source
v12.0.0Compare Source
β BREAKING CHANGES
Features
Bug Fixes
Configuration
π Schedule: (UTC)
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.