Repository navigation
[Breaking] Bump minimum Node.js version to >=20.9.0
#83113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
devjiwonchoi
merged 7 commits into
canary
from
jiwon/08-27-_breaking_bump_minimum_node.js_version_to_20.9.0_
Aug 29, 2025
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
a141393
[Breaking] Bump minimum Node.js version to `>=20.9.0`
devjiwonchoi b69c3c4
20.9 -> 20.19
devjiwonchoi b4b130c
20.19 -> 20.9
devjiwonchoi 7ea13d6
test: fix next-swc nodejs version range
devjiwonchoi be69985
run prettier fix
devjiwonchoi 6cae8a3
next-stats-action had 18.18.2 hard coded
devjiwonchoi 9672c24
update github actions engines
devjiwonchoi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -50,6 +50,6 @@ | |
| "validate-npm-package-name": "5.0.1" | ||
| }, | ||
| "engines": { | ||
| "node": ">=18.18.0" | ||
| "node": ">=20.9.0" | ||
| } | ||
| } | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -369,6 +369,6 @@ | |
| "vercel" | ||
| ], | ||
| "engines": { | ||
| "node": "^18.18.0 || ^19.8.0 || >= 20.0.0" | ||
| "node": ">=20.9.0" | ||
| } | ||
| } | ||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,7 +8,7 @@ | |
| "react-dom": "19.1.1" | ||
| }, | ||
| "engines": { | ||
| "node": ">=18.18.0" | ||
| "node": ">=20.9.0" | ||
| }, | ||
| "packageManager": "pnpm@9.6.0" | ||
| } | ||
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a TODO comment indicating that the hardcoded node version matrix should use environment variables instead.
View Details
Analysis
The modified line contains a TODO comment that suggests replacing the hardcoded node version array
[20, 22]with environment variables like[env.NODE_MAINTENANCE_VERSION, env.NODE_LTS_VERSION]. While the environment variables are already defined at the top of the file (NODE_MAINTENANCE_VERSION: 20andNODE_LTS_VERSION: 22), they're not being used in the matrix configuration. This creates a maintenance burden as version updates require changes in multiple places, and the TODO indicates the developers want to address this technical debt.The same TODO pattern appears on line 532 as well. Implementing this change would centralize version management and reduce the risk of inconsistencies during future Node.js version updates.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
env.NODE_MAINTENANCE_VERSIONis actually never used yet. Will follow up to use envs for versions.Since both are LTS,
NODE_ACTIVE_LTS_VERSIONandNODE_MAINTENANCE_LTS_VERSIONmakes sense to me.