chore(ci): upgrade actions to Node.js 24 runtimes#4648
Merged
Yicong-Huang merged 7 commits intoMay 2, 2026
Conversation
Bump every Node.js-based action used in .github/workflows/ to a version that ships Node 24, ahead of GitHub's deprecation deadlines (forced Node 24 on 2026-06-02; Node 20 removed on 2026-09-16). First-party actions: - actions/github-script v7 -> v8 (auto-assign, issue-triage) - actions/checkout v4 -> v5 (automatic-email-notif-on-ddl-change, check-header, create-release-candidate) - actions/cache v4 -> v5 (build) - actions/upload-artifact v4 -> v5 (build-and-push-images, create-release-candidate) - actions/download-artifact v4 -> v6 (build-and-push-images, create-release-candidate) Third-party actions (SHA-pinned with version comment): - amannn/action-semantic-pull-request v5.5.3 -> v6.1.1 - docker/setup-buildx-action v3.11.1 -> v4.0.0 - docker/login-action v3.6.0 -> v4.1.0 - docker/build-push-action v6.18.0 -> v7.1.0 - docker/setup-qemu-action v3.7.0 -> v4.0.0 Already on Node 24 (no change): actions/setup-java@v5, actions/setup-node@v5, actions/setup-python@v6, actions/labeler@v6, sbt/setup-sbt (composite), coursier/cache-action, apache/skywalking-eyes (composite). Closes apache#4647 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
aglinxinyuan
reviewed
May 2, 2026
Contributor
aglinxinyuan
left a comment
There was a problem hiding this comment.
Does this affect the node version used in the frontend CI? If so, do we also want to bump the node on the frontend?
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4648 +/- ##
============================================
+ Coverage 46.60% 47.20% +0.59%
- Complexity 2002 2090 +88
============================================
Files 996 996
Lines 37939 39345 +1406
Branches 3753 3888 +135
============================================
+ Hits 17683 18573 +890
- Misses 19479 19981 +502
- Partials 777 791 +14
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
Author
I don't think it affects. but let's bump that anyway, separately. |
Yicong-Huang
added a commit
that referenced
this pull request
May 2, 2026
### What changes were proposed in this PR? Bump every Node-based action used in `.github/workflows/` to a version that ships Node 24, ahead of GitHub's deadlines (forced Node 24 on 2026-06-02; Node 20 removed 2026-09-16). | Action | From | To | |---|---|---| | `actions/github-script` | `v7` | `v8` | | `actions/checkout` | `v4` | `v5` | | `actions/cache` | `v4` | `v5` | | `actions/upload-artifact` | `v4` | `v5` | | `actions/download-artifact` | `v4` | `v6` | | `amannn/action-semantic-pull-request` | `v5.5.3` | `v6.1.1` | | `docker/setup-buildx-action` | `v3.11.1` | `v4.0.0` | | `docker/login-action` | `v3.6.0` | `v4.1.0` | | `docker/build-push-action` | `v6.18.0` | `v7.1.0` | | `docker/setup-qemu-action` | `v3.7.0` | `v4.0.0` | Third-party actions are SHA-pinned with a version comment (existing convention). For each, the SHA points to that release tag; `runs.using: 'node24'` is verified. Already on Node 24 (no change): `actions/setup-java@v5`, `actions/setup-node@v5`, `actions/setup-python@v6`, `actions/labeler@v6`, `coursier/cache-action`. Composite actions are unaffected by the Node 20 deprecation: `sbt/setup-sbt`, `apache/skywalking-eyes`. ### Any related issues, documentation, discussions? Closes #4647 ### How was this PR tested? YAML parses locally for all 11 workflow files. Will be exercised on this PR's own CI run — the Node 20 deprecation warning should disappear from logs of every job. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Opus 4.7) Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> (backported from commit e3d96b0)
This was referenced May 2, 2026
Closed
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.
What changes were proposed in this PR?
Bump every Node-based action used in
.github/workflows/to a version that ships Node 24, ahead of GitHub's deadlines (forced Node 24 on 2026-06-02; Node 20 removed 2026-09-16).actions/github-scriptv7v8actions/checkoutv4v5actions/cachev4v5actions/upload-artifactv4v5actions/download-artifactv4v6amannn/action-semantic-pull-requestv5.5.3v6.1.1docker/setup-buildx-actionv3.11.1v4.0.0docker/login-actionv3.6.0v4.1.0docker/build-push-actionv6.18.0v7.1.0docker/setup-qemu-actionv3.7.0v4.0.0Third-party actions are SHA-pinned with a version comment (existing convention). For each, the SHA points to that release tag;
runs.using: 'node24'is verified.Already on Node 24 (no change):
actions/setup-java@v5,actions/setup-node@v5,actions/setup-python@v6,actions/labeler@v6,coursier/cache-action. Composite actions are unaffected by the Node 20 deprecation:sbt/setup-sbt,apache/skywalking-eyes.Any related issues, documentation, discussions?
Closes #4647
How was this PR tested?
YAML parses locally for all 11 workflow files. Will be exercised on this PR's own CI run — the Node 20 deprecation warning should disappear from logs of every job.
Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.7)