Repository navigation
Test on Node 24 and build releases on it - #5
Merged
Merged
Conversation
Node 20 reached end of life in April 2026, so the release job moves to Node 24, the current LTS. CI adds 24 to the matrix and keeps 18 and 20, because package.json still declares engines >=18 and that floor should stay tested until it is raised on purpose.
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
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 reached end of life in April 2026.
release.yml: builds and publishes on Node 24 (current LTS) instead of 20.ci.yml: matrix gains 24 and keeps 18/20, becauseengines.nodeis still>=18; dropping the floor from CI would leave the declared support untested. Raising the floor is a separate, breaking decision.