chore: update Node.js version requirements#2527
Merged
Conversation
* Update Node.js version requirements in `package.json` to `^20.19.0 || ^22.12.0 || >=23.0.0` * Update `.nvmrc` to use `lts/*`
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
rinatkhaziev
approved these changes
Aug 29, 2025
|
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
Purpose and Context
This change updates the supported Node.js runtime versions to modern, actively maintained releases. It updates the
engines.nodefield inpackage.jsonso the project requires^20.19.0 || ^22.12.0 || >=23.0.0. The change ensures compatibility with recent dependencies, improving security and long-term maintenance for contributors and CI environments.Key Changes
engines.nodeinpackage.jsonto require^20.19.0 || ^22.12.0 || >=23.0.0.enginesvalue frompackage.jsonImpact and Considerations
This change raises the minimum supported Node.js version and may therefore break installations or runtime on systems running older Node versions. Developers and CI that use older Node releases must upgrade before installing or running the CLI. Deployments that pin older Node versions must be updated to a supported runtime to avoid incompatibility. The
package.jsonenginesfield is authoritative for install-time checks and helper scripts that validate environment versions.Security Considerations
Requiring modern Node.js releases improves the security posture by adopting versions with current security patches and updated SSL stacks. This change reduces exposure to vulnerabilities present in older Node releases and aligns the codebase with supported, actively patched runtimes.
Performance Considerations
Newer Node.js versions include runtime and JIT improvements that typically reduce startup time and improve throughput for CPU-bound workloads. Users may see modest performance and memory efficiency improvements when running the CLI and tests on the newer Node releases. This change introduces no code-level performance regressions.
Testing and Validation
The change relies on existing CI and local test suites to validate compatibility with the new Node range.
BREAKING CHANGE: This release raises the minimum supported Node.js version to
^20.19.0 || ^22.12.0 || >=23.0.0. Users and CI systems running Node versions older than this range must upgrade before installing or running the project.Related: PLTFRM-1573
Changelog Description
Changed
package.jsonto^20.19.0 || ^22.12.0 || >=23.0.0Pull request checklist
New release checklist
Steps to Test
TBD.