Skip to content

CLDSRV-891 Update GitHub Actions to Node 24 runtime#6149

Open
JBWatenbergScality wants to merge 3 commits intodevelopment/9.3from
improvement/CLDSRV-891-update-github-actions-to-node24
Open

CLDSRV-891 Update GitHub Actions to Node 24 runtime#6149
JBWatenbergScality wants to merge 3 commits intodevelopment/9.3from
improvement/CLDSRV-891-update-github-actions-to-node24

Conversation

@JBWatenbergScality
Copy link
Copy Markdown

Summary

Update GitHub Actions workflow files to use action versions that run on Node 24.

Closes CLDSRV-891

Context

GitHub is deprecating Node 20 as the JavaScript runtime for GitHub Actions runners:
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Timeline:

  • June 2, 2026: Runners will default to Node 24 (deprecation warnings for node20 actions)
  • Fall 2026: Node 20 completely removed from runners

Changes

Updated action versions in all workflow files:

  • actions/checkout@v4@v6
  • actions/setup-node@v4@v6
  • actions/setup-python@v5@v6
  • docker/build-push-action@v5@v7
  • docker/login-action@v3@v4
  • docker/setup-buildx-action@v3@v4
  • softprops/action-gh-release@v2@v3
  • codecov/codecov-action@v4/@v5@v6

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Apr 14, 2026

Hello jbwatenbergscality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Copy Markdown
Contributor

bert-e commented Apr 14, 2026

Incorrect fix version

The Fix Version/s in issue CLDSRV-891 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 9.3.7

  • 9.4.0

Please check the Fix Version/s of CLDSRV-891, or the target
branch of this pull request.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 14, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.39%. Comparing base (6d86b25) to head (8c5537c).
⚠️ Report is 1 commits behind head on development/9.3.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 2 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.3    #6149      +/-   ##
===================================================
- Coverage            84.42%   84.39%   -0.03%     
===================================================
  Files                  206      206              
  Lines                13275    13275              
===================================================
- Hits                 11207    11204       -3     
- Misses                2068     2071       +3     
Flag Coverage Δ
file-ft-tests 67.96% <ø> (-0.06%) ⬇️
kmip-ft-tests 28.12% <ø> (ø)
mongo-v0-ft-tests 69.20% <ø> (-0.05%) ⬇️
mongo-v1-ft-tests 69.16% <ø> (ø)
multiple-backend 36.32% <ø> (ø)
sur-tests 35.60% <ø> (-0.83%) ⬇️
sur-tests-inflights 37.46% <ø> (-0.04%) ⬇️
unit 70.07% <ø> (ø)
utapi-v2-tests 34.37% <ø> (ø)

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

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

uses: actions/checkout@v6

- name: Initialize CodeQL
uses: github/codeql-action/init@v3
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

github/codeql-action/init@v3 and github/codeql-action/analyze@v3 (line 25) were not updated. These run on Node 20 and will need a version bump for Node 24 compatibility.

— Claude Code

uses: actions/checkout@v6

- name: 'Dependency Review'
uses: actions/dependency-review-action@v4
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

actions/dependency-review-action@v4 was not updated. This action runs on Node 20 and will need a version bump for Node 24 compatibility.

— Claude Code

@claude
Copy link
Copy Markdown

claude bot commented Apr 14, 2026

The workflow files listed in the PR description are updated correctly. However, several actions that also run on Node 20 were not updated:

- Composite actions not updated (high impact — used by most CI jobs):
- .github/actions/setup-ci/action.yaml still uses actions/setup-node@v4, actions/cache@v3, and actions/setup-python@v4
- .github/actions/cleanup-and-coverage/action.yaml still uses codecov/codecov-action@v5

- Workflow actions not updated:
- github/codeql-action/init@v3 and github/codeql-action/analyze@v3 in codeql.yaml
- actions/dependency-review-action@v4 in dependency-review.yaml
- actions/create-github-app-token@v1 in release.yaml
- codecov/test-results-action@v1 in tests.yaml (6 occurrences)

Review by Claude Code

@claude
Copy link
Copy Markdown

claude bot commented Apr 14, 2026

  • actions/create-github-app-token@v1 in release.yaml:98 was not updated. Latest available is v3 which runs on Node 24.
    - Update to actions/create-github-app-token@v3

    Review by Claude Code

…actions

- setup-ci: setup-node@v4→@v6, cache@v3→@v5, setup-python@v4→@v6
- cleanup-and-coverage: codecov-action@v5→@v6
- release: create-github-app-token@v1→@V3

Note: dependency-review-action and codecov/test-results-action have no
Node 24-compatible release yet; will update once available.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
flags: unit
- name: Upload coverage reports to Codecov
uses: codecov/codecov-action@v5
uses: codecov/codecov-action@v6
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

codecov/test-results-action@v1 (line 130, and 8 more occurrences) was not updated in this PR, while the related codecov/codecov-action was bumped to v6. If it is a Node-based action, it may also need a version bump for Node 24 compatibility.

— Claude Code

@claude
Copy link
Copy Markdown

claude bot commented Apr 14, 2026

  • codecov/test-results-action@v1 (9 occurrences in tests.yaml) was not updated, while the sibling codecov/codecov-action was bumped to v6. Worth verifying it does not need a Node 24-compatible version bump as well.

    Review by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants