chore: bump Node version to 24 in CI workflows #96
+13
−6
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
pkosiec
approved these changes
Feb 10, 2026
Member
pkosiec
left a comment
There was a problem hiding this comment.
Before merge, please confirm that the Node version doesn't require any updates in the lock files 👍
MarioCadenas
requested changes
Feb 10, 2026
Collaborator
MarioCadenas
left a comment
There was a problem hiding this comment.
why are we doing node 22 instead of 24 which is LTS?
Contributor
Author
agreed, bumped to 24 |
MarioCadenas
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Bumps Node.js from v20 to v22 in all GitHub Actions workflows and updates CONTRIBUTING.md