Skip to content

chore(ci): upgrade actions to Node.js 24 runtimes#4648

Merged
Yicong-Huang merged 7 commits into
apache:mainfrom
Yicong-Huang:chore/upgrade-actions-node24
May 2, 2026
Merged

chore(ci): upgrade actions to Node.js 24 runtimes#4648
Yicong-Huang merged 7 commits into
apache:mainfrom
Yicong-Huang:chore/upgrade-actions-node24

Conversation

@Yicong-Huang
Copy link
Copy Markdown
Contributor

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)

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>
@github-actions github-actions Bot added the ci changes related to CI label May 2, 2026
@Yicong-Huang Yicong-Huang added the release/v1.1.0-incubating back porting to release/v1.1.0-incubating label May 2, 2026
Copy link
Copy Markdown
Contributor

@aglinxinyuan aglinxinyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-commenter
Copy link
Copy Markdown

codecov-commenter commented May 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 47.20%. Comparing base (6cf4322) to head (0b6b3a2).

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     
Flag Coverage Δ
access-control-service 28.12% <ø> (ø)
agent-service 28.73% <ø> (ø)
amber 40.77% <ø> (+0.44%) ⬆️
computing-unit-managing-service 0.00% <ø> (ø)
config-service 0.00% <ø> (ø)
file-service 32.40% <ø> (-0.85%) ⬇️
frontend 34.97% <ø> (-0.31%) ⬇️
python 85.18% <ø> (+0.15%) ⬆️
workflow-compiling-service 47.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Yicong-Huang
Copy link
Copy Markdown
Contributor Author

Does this affect the node version used in the frontend CI? If so, do we also want to bump the node on the frontend?

I don't think it affects. but let's bump that anyway, separately.

@Yicong-Huang Yicong-Huang requested a review from aglinxinyuan May 2, 2026 06:19
Copy link
Copy Markdown
Contributor

@aglinxinyuan aglinxinyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Yicong-Huang Yicong-Huang enabled auto-merge (squash) May 2, 2026 18:59
@Yicong-Huang Yicong-Huang merged commit e3d96b0 into apache:main May 2, 2026
67 of 69 checks passed
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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci changes related to CI release/v1.1.0-incubating back porting to release/v1.1.0-incubating

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade GitHub Actions to runtimes that support Node.js 24

3 participants