Update to support node LTS versions#206
Merged
captbaritone merged 2 commits intocaptbaritone:mainfrom Dec 10, 2025
Merged
Conversation
✅ Deploy Preview for grats ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Owner
|
I tried running the CI on this PR. Looks like building the docs website fails on Node 25? |
Contributor
Author
|
I couldn't figure out how to fix the issue. What happened was that some codepath in the server bundle executed I removed node 25 for now. |
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
2 participants
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.
Summary
This PR updates our CI workflows to run tests only on Node.js LTS and the current stable (non-LTS) release. It also updates the
enginesfield to require Node.js >= 20.x, aligning with the latest LTS version.Rationale
Most enterprise environments I’ve worked with rely heavily on LTS releases of Node.js. Since those versions are the most relevant in production, focusing our test matrix on LTS provides clearer, more meaningful feedback.
Including the current stable (non-LTS) release gives us early visibility into potential breaking changes without expanding the test matrix unnecessarily.