Skip to content

feat!: require Node.js 22 or newer - #2670

Merged
josephfusco merged 3 commits into
canaryfrom
feat/2658-node-22-minimum
Oct 22, 2026
Merged

josephfusco merged 3 commits into
canaryfrom
feat/2658-node-22-minimum

Conversation

@josephfusco

@josephfusco josephfusco commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

Fixes #2658

This stays a draft until the team agrees on the RFC and the announcement is posted, because merging it makes release-please release @faustwp/core and @faustwp/cli 4.0.0 and @faustwp/blocks 7.0.0; merge the pending release PR (#2666) first so its fixes also ship in 3.x and 6.x for sites that stay on Node.js 20, which get an EBADENGINE warning (an error with engine-strict) on the new majors.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with raising the engines fields, updating the docs, removing the example override, and verifying the build, tests, example installs and the engine check under Node.js 20.

Raise engines.node to >=22 in @faustwp/core, @faustwp/cli, @faustwp/blocks, the root package and the examples, and drop the vitest override the examples only needed for npm 10.8 on Node.js 20.

BREAKING CHANGE: @faustwp/core, @faustwp/cli and @faustwp/blocks now require Node.js 22 or newer. Sites that need to stay on Node.js 20 can keep using core and cli 3.x and blocks 6.x.
@josephfusco
josephfusco marked this pull request as ready for review October 20, 2026 13:20
@josephfusco
josephfusco requested review from a team and colinmurphy as code owners October 20, 2026 13:20
@josephfusco josephfusco added Breaking Change Changes behavior that existing sites depend on [Area] Compatibility WordPress, Next.js, Node.js, and third-party compatibility [Area] Core Issues for the @faustwp/core package [Area] CLI Issues for the @faustwp/cli package [Area] Blocks Issues for the @faustwp/blocks package Needs Discussion Anything that needs a discussion/agreement labels Oct 20, 2026
@josephfusco
josephfusco merged commit 79e700c into canary Oct 22, 2026
18 checks passed
@josephfusco
josephfusco deleted the feat/2658-node-22-minimum branch October 22, 2026 15:10
@github-actions github-actions Bot mentioned this pull request Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Area] Blocks Issues for the @faustwp/blocks package [Area] CLI Issues for the @faustwp/cli package [Area] Compatibility WordPress, Next.js, Node.js, and third-party compatibility [Area] Core Issues for the @faustwp/core package Breaking Change Changes behavior that existing sites depend on Needs Discussion Anything that needs a discussion/agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RFC: Raise the minimum Node.js version to 22 in the next major

1 participant