Skip to content

chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates#121

Merged
PatrickSys merged 1 commit intomasterfrom
dependabot/npm_and_yarn/npm_and_yarn-7aa7e12bf9
Apr 30, 2026
Merged

chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates#121
PatrickSys merged 1 commit intomasterfrom
dependabot/npm_and_yarn/npm_and_yarn-7aa7e12bf9

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 30, 2026

Bumps the npm_and_yarn group with 2 updates in the / directory: uuid and postcss.

Updates uuid from 9.0.1 to 14.0.0

Release notes

Sourced from uuid's releases.

v14.0.0

14.0.0 (2026-04-19)

⚠ BREAKING CHANGES

  • expect crypto to be global everywhere (requires node@20+) (#935)
  • drop node@18 support (#934)

Features

Bug Fixes

  • expect crypto to be global everywhere (requires node@20+) (#935) (f2c235f)
  • Use GITHUB_TOKEN for release-please and enable npm provenance (#925) (ffa3138)

v13.0.1

13.0.1 (2026-04-27)

Bug Fixes

v13.0.0

13.0.0 (2025-09-08)

⚠ BREAKING CHANGES

  • make browser exports the default (#901)

Bug Fixes

v12.0.1

12.0.1 (2026-04-29)

Bug Fixes

v12.0.0

12.0.0 (2025-09-05)

... (truncated)

Changelog

Sourced from uuid's changelog.

14.0.0 (2026-04-19)

Security

  • Fixes GHSA-w5hq-g745-h8pq: v3(), v5(), and v6() did not validate that writes would remain within the bounds of a caller-supplied buffer, allowing out-of-bounds writes when an invalid offset was provided. A RangeError is now thrown if offset < 0 or offset + 16 > buf.length.

⚠ BREAKING CHANGES

  • crypto is now expected to be globally defined (requires node@20+) (#935)
  • drop node@18 support (#934)
  • upgrade minimum supported TypeScript version to 5.4.3, in keeping with the project's policy of supporting TypeScript versions released within the last two years

13.0.0 (2025-09-08)

⚠ BREAKING CHANGES

  • make browser exports the default (#901)

Bug Fixes

12.0.0 (2025-09-05)

⚠ BREAKING CHANGES

  • update to typescript@5.2 (#887)
  • remove CommonJS support (#886)
  • drop node@16 support (#883)

Features

Bug Fixes

11.1.0 (2025-02-19)

... (truncated)

Commits
  • 7c1ea08 chore(main): release 14.0.0 (#926)
  • 3d2c5b0 Merge commit from fork
  • f2c235f fix!: expect crypto to be global everywhere (requires node@20+) (#935)
  • 529ef08 chore: upgrade TypeScript and fixup types (#927)
  • 086fd79 chore: update dependencies (#933)
  • dc4ddb8 feat!: drop node@18 support (#934)
  • 0f1f9c9 chore: switch to Biome for parsing and linting (#932)
  • e2879e6 chore: use maintained version of npm-run-all (#930)
  • ffa3138 fix: Use GITHUB_TOKEN for release-please and enable npm provenance (#925)
  • 0423d49 docs: remove obsolete v1 option notes (#915)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for uuid since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.


Updates postcss from 8.5.6 to 8.5.12

Release notes

Sourced from postcss's releases.

8.5.12

  • Fixed reading any file via user-generated CSS.
  • Added opts.unsafeMap to disable checks.

8.5.11

  • Fixed nested brackets parsing performance (by @​offset).

8.5.10

  • Fixed XSS via unescaped </style> in non-bundler cases (by @​TharVid).

8.5.9

  • Speed up source map encoding paring in case of the error.

8.5.8

  • Fixed Processor#version.

8.5.7

  • Improved source map annotation cleaning performance (by CodeAnt AI).
Changelog

Sourced from postcss's changelog.

8.5.12

  • Fixed reading any file via user-generated CSS.
  • Added opts.unsafeMap to disable checks.

8.5.11

  • Fixed nested brackets parsing performance (by @​offset).

8.5.10

  • Fixed XSS via unescaped </style> in non-bundler cases (by @​TharVid).

8.5.9

  • Speed up source map encoding paring in case of the error.

8.5.8

  • Fixed Processor#version.

8.5.7

  • Improved source map annotation cleaning performance (by CodeAnt AI).
Commits
  • 9bc81c4 Release 8.5.12 version
  • 85c4d7d Another try to fix coverage
  • 94484ca Try to fix coverage
  • c64b748 Load only .map source maps
  • aaec7b7 Avoid throwing JSON parsing errors for non-JSON source maps
  • 233fb26 Mention original author of the solution
  • 2502f75 Release 8.5.11 version
  • 5ca1901 Speed up parsing many nested brackets
  • 42b5337 Update dependencies
  • 7e36e15 Cache node.raws locally in Stringifier hot methods
  • Additional commits viewable in compare view

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

…dates

Bumps the npm_and_yarn group with 2 updates in the / directory: [uuid](https://github.com/uuidjs/uuid) and [postcss](https://github.com/postcss/postcss).


Updates `uuid` from 9.0.1 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@v9.0.1...v14.0.0)

Updates `postcss` from 8.5.6 to 8.5.12
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.5.6...8.5.12)

---
updated-dependencies:
- dependency-name: uuid
  dependency-version: 14.0.0
  dependency-type: direct:production
  dependency-group: npm_and_yarn
- dependency-name: postcss
  dependency-version: 8.5.12
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 30, 2026
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 30, 2026

Greptile Summary

This dependabot PR bumps uuid from 9.0.1 to 14.0.0 (5 major versions) and postcss from 8.5.6 to 8.5.12. The postcss update is straightforward — patch/minor with security fixes. The uuid jump introduces two issues that need to be resolved before merging:

  • The project's engines field still declares \"node\": \">=18.0.0\", but uuid@14 drops Node 18 support and requires Node 20+ for its global crypto dependency. Users or CI on Node 18 will hit runtime failures.
  • @types/uuid@^9.0.8 remains in devDependencies despite uuid now shipping its own TypeScript types since v10; the stale community types will conflict with v14's bundled declarations.

Confidence Score: 3/5

Not safe to merge as-is — uuid v14 requires Node 20+ but the declared engine minimum is Node 18, and the stale @types/uuid will cause TypeScript type conflicts.

Two P1 findings: a runtime compatibility break on Node 18 (contradicts the declared engine range) and a stale type package that will conflict with uuid v14's bundled types. Both need to be resolved before this is safe to land.

package.json — engines field and @types/uuid devDependency both need updating.

Important Files Changed

Filename Overview
package.json uuid bumped 9→14 (5 major versions) while engines still allows Node 18; @types/uuid stale at v9 alongside uuid v14.
pnpm-lock.yaml Lock file updated consistently for uuid 9→14 and postcss 8.5.6→8.5.12; no anomalies in the snapshot entries.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[uuid 9 to 14] --> B{Breaking changes}
    B --> C[Node 18 dropped - requires Node 20+]
    B --> D[CommonJS removed in v12 - ESM only]
    B --> E[Browser exports default in v13]
    B --> F[Bundled TS types since v10]
    C --> G[engines still says node 18+ - P1 conflict]
    F --> H[types/uuid at v9 still present - P1 type conflict]
    I[postcss 8.5.6 to 8.5.12] --> J[Patch update - security fixes only]
Loading

Comments Outside Diff (2)

  1. package.json, line 57 (link)

    P1 Node.js engine constraint conflicts with uuid v14

    uuid@14 drops Node.js 18 support and requires Node 20+ (it now expects crypto to be globally available, which is only guaranteed on Node 20+). The project's engines field still declares "node": ">=18.0.0", so any user or CI runner on Node 18 will encounter a runtime failure when uuid tries to access the global crypto object. Either the engines constraint needs to be tightened to >=20.0.0, or uuid should be pinned to a version that still supports Node 18 (e.g., ^11.x or the 12.0.1/13.0.1 backports).

  2. package.json, line 150 (link)

    P1 @types/uuid is stale and will conflict with uuid v14

    @types/uuid was the community-maintained type package for uuid v9 and earlier. Starting with uuid v10, the uuid package ships its own bundled TypeScript declarations, making @types/uuid redundant and potentially conflicting. Keeping @types/uuid@^9.0.8 alongside uuid@^14.0.0 risks duplicate or mismatched type definitions — TypeScript may pick up the stale v9 types and fail to recognise APIs added or changed across the 5 major versions since then. @types/uuid should be removed from devDependencies.

Reviews (1): Last reviewed commit: "chore(deps): bump the npm_and_yarn group..." | Re-trigger Greptile

@PatrickSys PatrickSys merged commit 61fbedc into master Apr 30, 2026
4 checks passed
@PatrickSys PatrickSys deleted the dependabot/npm_and_yarn/npm_and_yarn-7aa7e12bf9 branch April 30, 2026 07:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant