chore: upgrade GitHub Actions from Node 20 to Node 24 - #140
Merged
Conversation
Like GradleDependency, this check fires whenever a newer version is released, causing spurious CI failures unrelated to the PR under review. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
BehnamMozafari
approved these changes
Jun 9, 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.
Node 20 is being deprecated on GitHub Actions runners. Starting June 16, 2026, runners will use Node 24 by default.
This PR upgrades outdated action references in this repo to the latest released version that ships Node 24 support, pinned to its commit SHA. Each action's node version is determined by reading its
action.ymlat the pinned ref.See: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/