feat!: require node >=24, test on 24 & 26, support npm >=11#433
Merged
Conversation
Node 20 has reached end-of-life. Raise the minimum supported node to 24, add explicit node 26 coverage via a CI test matrix, and declare npm >=11. BREAKING CHANGE: minimum node is now 24; node 20 and 22 are no longer supported.
doistbot
reviewed
Jul 16, 2026
doistbot
left a comment
doistbot
left a comment
Member
There was a problem hiding this comment.
This PR bumps the minimum Node version to 24, adds a CI test matrix covering Node 24 and 26, and declares npm >=11 support across .nvmrc, package.json, and the CI/release workflows.
Few things worth tightening:
- Update
CODEBASE.md— it still references Node >=20.18.1, which now contradicts the new runtime policy declared here. - Regenerate
package-lock.jsonwith the supported npm version — its root entry still declaresnode: >=20.18.1and omits the npm engine, leaving the checked-in lockfile out of sync with the manifest.
Address doistbot review: CODEBASE.md still advertised Node >=20.18.1 and the package-lock root engines entry was out of sync with the new manifest.
The node-24 bump set engines.node to ">=24"; the doctor node check regex required a full semver, so it silently degraded to a warn. Accept and pad partial major ranges before comparing.
…karound cli-core 0.26.2 accepts partial versions, so the local padVersion helper is no longer needed; the relaxed >= range regex stays.
Contributor
|
🎉 This PR is included in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
3 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.
Node 20 has reached end-of-life. This raises the minimum supported node to 24, adds explicit node 26 coverage via a CI test matrix, and declares npm
>=11support.Changes
.nvmrc:20→24package.jsonengines:node: ">=24",npm: ">=11"test.yml: now runs a[24, 26]node matrixrelease.yml: publish node22→24Breaking change
Minimum node is now 24; node 20 and 22 are no longer supported.