chore: set Node compatibility version to >=16 #4866
Merged
Conversation
This file contains 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
cat2608
force-pushed
the
chore/HEAD-497-upgrade-engines
branch
from
f4ef2e7 to
30e7c78
Compare
cat2608
force-pushed
the
chore/HEAD-497-upgrade-engines
branch
from
60a289d to
e31a757
Compare
bastiandoetsch
approved these changes
Sep 22, 2023
This was referenced Oct 18, 2023
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.
What does this PR do?
The main goal of this change is to add support for Node 18.
As a first step to make this change granular, this PR updates the minimum required Node.js version for the project to
>=16.How should this be manually tested?
Installing dependencies with a Node version older than 16 will trigger a warning the Node version not being compatible.
Any background context you want to provide?
What are the relevant tickets?
HEAD-497