Drop support for Node 18 #2827
Merged
Drop support for Node 18 #2827
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.js v18 hit end of life in April 2025. Dropping official support, mostly in the form of changing the
enginesrule and not testing on 18 any longer. As of yet there should not be any breaking changes that should force someone to upgrade to Node.js v20, but this warrants us the option to do so when necessary.This change will go out in
@elastic/elasticsearch9.1 and@elastic/transport9.1, which are currently scheduled to go GA in July 2025. All 8.x clients still support v18 indefinitely.