Skip to content

Upgrade GitHub Actions for Node 24 compatibility#6990

Merged
alliepiper merged 3 commits intoNVIDIA:mainfrom
salmanmkc:upgrade-github-actions-node24
Jan 29, 2026
Merged

Upgrade GitHub Actions for Node 24 compatibility#6990
alliepiper merged 3 commits intoNVIDIA:mainfrom
salmanmkc:upgrade-github-actions-node24

Conversation

@salmanmkc
Copy link
Contributor

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action Old Version(s) New Version Release Files
actions/checkout v4 v6 Release backport-prs.yml, build-and-test-python-wheels.yml, build-docs.yml, build-matx.yml, build-pytorch.yml, build-rapids.yml, ci-workflow-nightly.yml, ci-workflow-pull-request.yml, ci-workflow-weekly.yml, git-bisect.yml, release-create-new.yml, release-finalize.yml, release-update-rc.yml, update-branch-version.yml, verify-devcontainers.yml, workflow-dispatch-standalone-group-linux.yml, workflow-dispatch-standalone-group-windows.yml, workflow-dispatch-two-stage-linux.yml, workflow-dispatch-two-stage-windows.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

  • Node 20 EOL: April 2026
  • Node 24 default: March 4th, 2026
  • Action: Update to latest action versions that support Node 24

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

@salmanmkc salmanmkc requested a review from a team as a code owner December 16, 2025 11:58
@salmanmkc salmanmkc requested a review from jrhemstad December 16, 2025 11:58
@github-project-automation github-project-automation bot moved this to Todo in CCCL Dec 16, 2025
@copy-pr-bot
Copy link
Contributor

copy-pr-bot bot commented Dec 16, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@cccl-authenticator-app cccl-authenticator-app bot moved this from Todo to In Review in CCCL Dec 16, 2025
@salmanmkc salmanmkc force-pushed the upgrade-github-actions-node24 branch from eeaa171 to 8d33c2f Compare December 16, 2025 12:11
@davebayer
Copy link
Contributor

/ok to test 8d33c2f

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@alliepiper alliepiper self-assigned this Jan 29, 2026
@alliepiper
Copy link
Contributor

/ok to test 6bcedf3

@alliepiper alliepiper moved this from In Review to Testing in CCCL Jan 29, 2026
@github-project-automation github-project-automation bot moved this from Testing to In Review in CCCL Jan 29, 2026
@alliepiper alliepiper moved this from In Review to Testing in CCCL Jan 29, 2026
@github-project-automation github-project-automation bot moved this from Testing to In Review in CCCL Jan 29, 2026
@alliepiper alliepiper moved this from In Review to Testing in CCCL Jan 29, 2026
@github-actions
Copy link
Contributor

🥳 CI Workflow Results

🟩 Finished in 5h 50m: Pass: 100%/302 | Total: 10d 04h | Max: 5h 50m | Hits: 84%/451549

See results here.

@alliepiper alliepiper merged commit ad6c85f into NVIDIA:main Jan 29, 2026
321 checks passed
@github-project-automation github-project-automation bot moved this from Testing to Done in CCCL Jan 29, 2026
fbusato pushed a commit to fbusato/cccl that referenced this pull request Feb 19, 2026
* Upgrade GitHub Actions for Node 24 compatibility

* Update newer workflows.

---------

Co-authored-by: alliepiper <alliepiper16@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants