chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates#121
Conversation
…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>
Greptile SummaryThis dependabot PR bumps
Confidence Score: 3/5Not 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.
|
| 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]
Comments Outside Diff (2)
-
package.json, line 57 (link)Node.js engine constraint conflicts with uuid v14
uuid@14drops Node.js 18 support and requires Node 20+ (it now expectscryptoto be globally available, which is only guaranteed on Node 20+). The project'senginesfield still declares"node": ">=18.0.0", so any user or CI runner on Node 18 will encounter a runtime failure whenuuidtries to access the globalcryptoobject. Either the engines constraint needs to be tightened to>=20.0.0, oruuidshould be pinned to a version that still supports Node 18 (e.g.,^11.xor the12.0.1/13.0.1backports). -
package.json, line 150 (link)@types/uuidis stale and will conflict with uuid v14@types/uuidwas the community-maintained type package for uuid v9 and earlier. Starting with uuid v10, theuuidpackage ships its own bundled TypeScript declarations, making@types/uuidredundant and potentially conflicting. Keeping@types/uuid@^9.0.8alongsideuuid@^14.0.0risks 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/uuidshould be removed fromdevDependencies.
Reviews (1): Last reviewed commit: "chore(deps): bump the npm_and_yarn group..." | Re-trigger Greptile
Bumps the npm_and_yarn group with 2 updates in the / directory: uuid and postcss.
Updates
uuidfrom 9.0.1 to 14.0.0Release notes
Sourced from uuid's releases.
... (truncated)
Changelog
Sourced from uuid's changelog.
... (truncated)
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.
Install script changes
This version adds
preparescript that runs during installation. Review the package contents before updating.Updates
postcssfrom 8.5.6 to 8.5.12Release notes
Sourced from postcss's releases.
Changelog
Sourced from postcss's changelog.
Commits
9bc81c4Release 8.5.12 version85c4d7dAnother try to fix coverage94484caTry to fix coveragec64b748Load only .map source mapsaaec7b7Avoid throwing JSON parsing errors for non-JSON source maps233fb26Mention original author of the solution2502f75Release 8.5.11 version5ca1901Speed up parsing many nested brackets42b5337Update dependencies7e36e15Cache node.raws locally in Stringifier hot methodsDependabot 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 <dependency name> major versionwill 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 versionwill 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 conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.