feat!: drop support for Node 18 and 20

[cryptodev-2s]

Top of stack #315, on #323. Mirrors MetaMask/core#9976, the bottom of core's foundational stack.

Breaking

	Before	After
engines.node	^18.18 || ^20.14 || >=22	^22.14.0 || ^24
CI matrix	18, 20, 22	22, 24

constraints.pro is updated to match, so yarn constraints enforces the new range.

Why this one before TypeScript and target/lib

Core sequenced its stack Node → ESM → TypeScript → target/lib, and that order is a dependency chain rather than an arbitrary grouping. Raising the runtime floor first is what justifies each step above it, and bumping the emit target is only defensible once the floor guarantees the runtime supports it.

The remaining two land in that order after this.

---

Note

Medium Risk
Breaking runtime contract for all consumers and CI; no application logic changes, but anyone on Node 18/20 must upgrade before adopting this release.

Overview
Breaking: This PR raises the minimum supported Node version and aligns CI with that floor, mirroring MetaMask/core’s foundational stack ordering.

engines.node is now ^22.14.0 || ^24 (Node 18 and 20 are no longer supported). The same range is enforced via constraints.pro, so yarn constraints keeps workspace packages consistent. GitHub Actions build-lint-test now runs on 22.x and 24.x instead of 18, 20, and 22. The unreleased CHANGELOG entry documents the breaking change.

^{Reviewed by Cursor Bugbot for commit a3e25e3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​node@​18.18.14 ⏵ 22.20.1	+12

View full report