Remove support for old ArangoDB and Node.js versions #319
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
Yogu
changed the title
|
huh didn't expect everything to break with node 20+ :D |
Yogu
force-pushed
the
remove-arango-and-node-support
branch
from
b3f091d to
3436755
Compare
Etienne-Buschong
approved these changes
May 16, 2024
It will become the default for target=es2022
Node 22 is not LTS yet, but it will be in a few months, so it's good to test it already.
Only Node.js 18+ is supported. Increased the target and lib to ES2022 because that's the level supported by Node 18. target=ES2022 means useDefineForClassFields is now the default. BREAKING CHANGE: Node.js 14 and 16 are no longer supported.
Still keeping the tests for 3.8 for now. BREAKING CHANGE: ArangoDB 3.8, 3.9 and 3.10 are no longer supported.
Yogu
force-pushed
the
remove-arango-and-node-support
branch
from
3436755 to
d499a7f
Compare
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.
long due.
We need to keep in mind to release the next version as 4.0 (because removing support of old versions is breaking)