Repository navigation
ci: upgrade github actions to node-v24 and pin to commit shas - #407
Merged
Merged
Conversation
BartoszLitwiniuk
changed the title
KishanPRao
approved these changes
Oct 7, 2026
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.
GitHub runners now force actions built for Node 20 to run on Node 24, and log a deprecation warning for each one (setup-java v4 also gets a "no longer receives updates" warning). This PR moves every action to a release that runs on Node 24 natively and pins each one to a commit hash.
Each action is pinned as
owner/action@<sha> # vX.Y.Z. android-emulator-runner was already on Node 24, so it only gets the hash pin.Success runs: Android CI and Node.js CI