Skip to content

chore!: bump minimum Node.js engine to >=14.17.0#154

Open
escoberik wants to merge 2 commits intoapache:masterfrom
escoberik:chore/bump-engines-node-14
Open

chore!: bump minimum Node.js engine to >=14.17.0#154
escoberik wants to merge 2 commits intoapache:masterfrom
escoberik:chore/bump-engines-node-14

Conversation

@escoberik
Copy link
Copy Markdown

Companion to #153.

crypto.randomUUID() — introduced to replace the uuid dependency in #153 — requires Node.js >=14.17.0. Node 10 and 12 have been EOL since 2021 and 2022 respectively.

This is a separate PR as requested so that #153 can be reverted independently if needed.

Breaking change

Node <14.17.0 is no longer supported.

escoberik added 2 commits May 4, 2026 16:48
uuid <14.0.0 is flagged by GHSA-w5hq-g745-h8pq (missing buffer bounds
check in v3/v5/v6 when buf is provided). The only upstream fix is uuid
v14, but v14 dropped CommonJS support, which would break this package.

Since only uuid.v4() is used here (in generateUuid()), replace it with
Node's built-in crypto.randomUUID() — available since Node 14.17.0,
produces the same RFC 4122 v4 UUID format, and requires no external
dependency. The uuid package is removed from dependencies entirely.

BREAKING CHANGE: Node >=14.17.0 is now required at runtime (crypto.randomUUID
was introduced in that release). The engines field remains >=10.0.0; a
separate PR will bump it to reflect the new minimum.

All 426 existing tests pass.
Reflects the runtime requirement introduced by apache#153
(crypto.randomUUID, available since Node 14.17.0). Node 10 and 12 have
been EOL since 2021 and 2022 respectively.

BREAKING CHANGE: Node <14.17.0 is no longer supported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant