drop node 20 support#756
Merged
Merged
Conversation
Node 20.x went End-of-Life on 2026-04-30. Signed-off-by: cjihrig <cjihrig@gmail.com>
Contributor
|
I'm usually loathe to drop backward compatibility if there's no gain to be had for doing so, but there are at least a couple we could do. Small performance gain to be had on aggregation for Which I had to modify for reasons of node 20 compatibility. Wonder if there are any more. |
jdmarshall
approved these changes
Jul 2, 2026
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.
Node 20.x went End-of-Life on 2026-04-30.
The package rename seems like a good time for such a change.