ci: drop Node 18 from CI matrix, add Node 24#2371
Open
josephfusco wants to merge 1 commit into
Open
Conversation
Bumps CI to test against current Active LTS (Node 22) and the new LTS (Node 24), keeping Node 20 in the matrix to validate the runtime that existing customers still deploy on. Drops Node 18 (EOL since March 2025). Also updates .nvmrc and the bundle-analysis pin away from EOL versions. This is a CI-only change. No package.json engines field is touched, so published packages continue to declare support for Node 18+ and no customer-facing upgrade is forced. Refs #2369
|
This was referenced May 22, 2026
Contributor
📦 Next.js Bundle Analysis for @faustwp/getting-started-exampleThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates our CI to test against current Node LTS versions while keeping support for the runtime our customers are deployed on.
Refs #2369.