chore(deps): bump uuid from 11.1.0 to 14.0.0#5869
Closed
dependabot[bot] wants to merge 1 commit intounstablefrom
Closed
chore(deps): bump uuid from 11.1.0 to 14.0.0#5869dependabot[bot] wants to merge 1 commit intounstablefrom
dependabot[bot] wants to merge 1 commit intounstablefrom
Conversation
Bumps [uuid](https://github.com/uuidjs/uuid) from 11.1.0 to 14.0.0. - [Release notes](https://github.com/uuidjs/uuid/releases) - [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md) - [Commits](uuidjs/uuid@v11.1.0...v14.0.0) --- updated-dependencies: - dependency-name: uuid dependency-version: 14.0.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
rtibblesbot
suggested changes
May 1, 2026
Contributor
rtibblesbot
left a comment
rtibblesbot
left a comment
There was a problem hiding this comment.
Dependency Update Review
Package: uuid 11.1.0 → 14.0.0
Semver risk: Multi-major (3 major versions)
Dependency type: Production (dependencies)
CI status: Failing — Frontend tests
Changelog Analysis
Sources consulted:
- Release notes and CHANGELOG.md entries from the PR body
Breaking changes (cumulative across v12, v13, v14):
- v12.0.0: Removed CommonJS support — uuid is now ESM-only. This is the root cause of CI failures.
- v12.0.0: Dropped Node 16 support
- v13.0.0: Made browser exports the default
- v14.0.0: Dropped Node 18 support; requires Node 20+ and global
crypto
Security fixes:
- GHSA-w5hq-g745-h8pq: Out-of-bounds write in
v3(),v5(),v6()when an invalidoffsetis provided. This project only importsv4, so the exposure is not present here. The fix is also backported to v13.0.1 and v12.0.1.
Other notable changes:
- v12.0.0: Updated to TypeScript 5.2
Compatibility Assessment
- CI result: The entire frontend test suite fails with
SyntaxError: Unexpected token 'export'across 20+ test files. This is the canonical symptom of a Jest environment receiving an ESM-only module — Jest's defaulttransformIgnorePatternsexcludesnode_modules, so uuid's ESMexportstatements cannot be parsed. - Project uses affected APIs: No — only
v4is imported (import { v4 as uuidv4 } from 'uuid'). The security fix does not coverv4, so there is no security urgency driving this specific jump. - Code changes required: Yes — the Jest configuration must be updated to transpile uuid (e.g., by removing it from
transformIgnorePatterns), or the project should adopt uuid v11.x which retains CommonJS support and is maintained until ~2028 (per the updated deprecation notice now in the lockfile). - No migration included: The PR only changes
package.jsonandpnpm-lock.yaml.
Recommendation
REQUEST_CHANGES — CI is failing due to ESM incompatibility introduced in uuid v12. Either add Jest transform config for uuid, or hold at uuid v11 (which keeps CommonJS support). If the goal is to apply the GHSA-w5hq-g745-h8pq security fix, note that the project only uses v4 and is not affected by that advisory.
No UI files changed — visual inspection skipped.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Reviewed the pull request diff checking for:
- Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
- Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
- Architecture: duplicated concerns, minimal interfaces, composition over inheritance
- Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
- Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
- Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
- Checked CI status and linked issue acceptance criteria
- For UI changes: inspected screenshots for layout, visual completeness, and consistency
| "store2": "^2.14.4", | ||
| "string-strip-html": "8.3.0", | ||
| "uuid": "^11.1.0", | ||
| "uuid": "^14.0.0", |
Contributor
There was a problem hiding this comment.
blocking: uuid v12 removed CommonJS support, making it ESM-only. Jest's default transformIgnorePatterns excludes node_modules, so it cannot parse uuid's export statements — causing SyntaxError: Unexpected token 'export' across the entire frontend test suite (confirmed in CI).
Two options:
- Stay on uuid v11 (
^11.1.0): v11 retains CommonJS support and is maintained until ~2028 (per the updated deprecation notice now visible in the lockfile). The security advisory GHSA-w5hq-g745-h8pq affects onlyv3/v5/v6— this project imports onlyv4and is not exposed. - Update Jest config: Add uuid to the transpilation allowlist (e.g., remove it from
transformIgnorePatternsin the Jest config) so the test runner can handle ESM. This would require testing carefully as it affects the build toolchain.
Member
|
@dependabot ignore this major version |
Contributor
Author
|
OK, I won't notify you about version 14.x.x again, unless you re-open this PR. |
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
2 participants
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.
Bumps uuid from 11.1.0 to 14.0.0.
Release notes
Sourced from uuid's releases.
... (truncated)
Changelog
Sourced from uuid's changelog.
Commits
7c1ea08chore(main): release 14.0.0 (#926)3d2c5b0Merge commit from forkf2c235ffix!: expectcryptoto be global everywhere (requires node@20+) (#935)529ef08chore: upgrade TypeScript and fixup types (#927)086fd79chore: update dependencies (#933)dc4ddb8feat!: drop node@18 support (#934)0f1f9c9chore: switch to Biome for parsing and linting (#932)e2879e6chore: use maintained version of npm-run-all (#930)ffa3138fix: Use GITHUB_TOKEN for release-please and enable npm provenance (#925)0423d49docs: remove obsolete v1 option notes (#915)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for uuid since your current version.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.