fix: use more explicit node.js version range#39398
Merged
Conversation
This isn't a breaking change, as the previous range was `>=18.0.0`, which is inclusive of these versions. The only change is that this does drop 19, 21, 23, and 25, but Gatsby documents that only LTS releases are supported.
gatsbot
bot
added
the
status: triage needed
serhalp
changed the title
serhalp
removed
the
status: triage needed
pieh
approved these changes
Jan 26, 2026
serhalp
added a commit
that referenced
this pull request
Jan 26, 2026
* fix: set node.js version range to 18 + 20 + 22 + 24 This isn't a breaking change, as the previous range was `>=18.0.0`, which is inclusive of all versions that currently exist. The purpose of this change is to ensure that our current ranges don't automatically start claiming to support node.js 26 (and so on) the day it is released.
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.
Description
This isn't a breaking change, as the previous range was
>=18.0.0, which is inclusive of all versions that currently exist.The purpose of this change is to ensure that our current ranges don't automatically start claiming to support node.js 26 (and so on) the day it is released.
This also makes it clearer that Gatsby now explicitly supports Node.js 22 and 24.
Documentation
https://www.gatsbyjs.com/docs/tutorial/getting-started/part-0/#nodejs
Tests
N/A but in #39380 we started testing against node.js 24
Related Issues
N/A