sets node engine range to ^20.17.0 || >=22.9.0 #7831
Merged
Conversation
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
BREAKING CHANGE: @npmcli/docs now supports node `^20.17.0 || >=22.9.0`
…>=22.9.0` BREAKING CHANGE: @npmcli/smoke-tests now supports node `^20.17.0 || >=22.9.0`
… >=22.9.0` BREAKING CHANGE: @npmcli/mock-globals now supports node `^20.17.0 || >=22.9.0`
…| >=22.9.0` BREAKING CHANGE: @npmcli/mock-registry now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmversion now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmteam now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmsearch now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmpublish now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmpack now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmorg now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmhook now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmfund now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmexec now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmdiff now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: libnpmaccess now supports node `^20.17.0 || >=22.9.0`
…9.0` BREAKING CHANGE: @npmcli/config now supports node `^20.17.0 || >=22.9.0`
…2.9.0` BREAKING CHANGE: @npmcli/arborist now supports node `^20.17.0 || >=22.9.0`
BREAKING CHANGE: npm now supports node `^20.17.0 || >=22.9.0`
reggi force-pushed the node-engine-20-22 branch from f90069a to 88d8d3d Compare reggi changed the title ^20.17.0 || >=22.9.0 
wraithgar approved these changes Oct 14, 2024
There was a problem hiding this comment.
- v10 branch has already been created.
- We can enable pre-release mode in any workspaces where we think we'll have more breaking changes prior to any releases we make.
- Node.js
v20.18.0has been released, but there is no compelling reason to re-do all the work here to limit to that version. In the absence of a particular Node.js feature we wanted to use in npm 11, the floors of each version are a best-effort, not a hard and and fast "latest" rule
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
This pr sets npm and all its workspaces dependencies to support Node.js versions
^20.17.0 || >=22.9.0dropping support for node 18, this is a breaking change and will usher in npm 11.related to: npm/statusboard#899
part of: npm/statusboard#898
prior art: #7803