feat!: bump engines requirement to Node 22
#1167
Merged
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
9e52f83 to
bc19e91
Compare
931e82b to
5e5336d
Compare
erickzhao
reviewed
Apr 4, 2025
BREAKING CHANGE: bumps required Node.js version to >=22.12.0. ESM-only.
VerteDinde
approved these changes
Apr 29, 2025
dsanders11
approved these changes
Apr 29, 2025
erickzhao
approved these changes
Apr 29, 2025
Co-authored-by: David Sanders <[email protected]>
|
🎉 This PR is included in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
BREAKING CHANGE: bumps required Node.js version to
>=22.12.0. ESM-only.I also took the opportunity to update
farmhashto3.3.1in one of the test fixtures so we can run a couple of test cases we were skipping onarm64macOS. I tried switching to4.0.1but it would require some deeper changes in the tests, so I figured it would be a good idea to address that in a follow-up PR as3.3.1is enough to get those tests running for the Node upgrade.