chore(ci): bump GitHub Actions to Node 24#152
Merged
zepeng811 merged 1 commit intoJun 18, 2026
Conversation
zepeng811
approved these changes
Jun 18, 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
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.
Summary
Bulk SHA-pin update of GitHub Actions to their latest Node-24-compatible release. Pre-emptive migration ahead of GitHub Actions runner Node 20 removal in Fall 2026.
Actions bumped
actions/checkout@v4.3.0->df4cb1c0...(v6.0.3)actions/setup-node@v4.4.0->48b55a01...(v6.4.0)aws-actions/configure-aws-credentials@v4.3.1->e7f100cf...(v6.2.0)aws-actions/aws-secretsmanager-get-secrets@v2.0.5->2cb1a461...(v3.0.1)Verification
Every emitted SHA was verified via
gh api /repos/<owner>/<repo>/commits/<sha>before commit.Background
Node 20 is being removed from GitHub Actions runners in Fall 2026 (see GitHub changelog). This PR pre-emptively bumps every pinned third-party action to its first Node-24-compatible release so the workflows keep running on the new runner default.