chore: Update actions version for Node.js 24#66
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
Fixes #64
Latest version of github runner is deprecating Node.js 20 and moving to Node.js 24. Some actions are not compatible with the Upcoming Node.js 24 version. Hence we need to update those actions to versions that have added support of Node 24 before the due date. (See details here)
The following actions have been updated.
The warning comes up in every workflow job that has actions that do not support Node 24. I looked through all our action runs taking note of the actions complained about. I looked at the lastest versions of each actions in their repo and checked to see that those versions have added node.js 24 support, before I updated in our CI to use those versions.
The updated version changes works on my fork and no longer shows the warning. (Before vs After)
Once this is approved, it should also be updated in all other bindings CI if needed. (e.g bdk-android)