Upgrade GitHub Actions for Node 24 compatibility

[salmanmkc]

Warning

You may currently be seeing a warning like this in your workflow runs:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20
and may not work as expected: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8, actions/cache@9255dc7a253b0ccc959486e2bca901246202afeb.
Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026.
Please check if updated versions of these actions are available that support Node.js 24.
To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment
variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you
can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true.
For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The exact actions listed will vary per workflow.

Upgrades GitHub Actions to versions that support Node 24, since Node 20 is reaching EOL in April 2026.

Changes

Action	Old Version(s)	New Version	Compare	Files
actions/cache	9255dc7	cdf6c1f	Diff	presubmit.yml
actions/checkout	8e8c483	de0fac2	Diff	presubmit.yml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will default to Node 24 starting June 2nd, 2026.

• Node 20 EOL: April 2026
• Node 24 becomes default: June 2nd, 2026

Release Notes

Release notes for actions/checkout

v6.0.2

What's Changed

• Add orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set by @TingluoHuang in Add orchestration_id to git user-agent when ACTIONS_ORCHESTRATION_ID is set actions/checkout#2355
• Fix tag handling: preserve annotations and explicit fetch-tags by @ericsciple in Fix tag handling: preserve annotations and explicit fetch-tags actions/checkout#2356

Full Changelog: actions/checkout@v6.0.1...v6.0.2

Release notes for actions/cache

v5.0.3

What's Changed

• Bump @actions/cache to v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)
• Bump @actions/core to v2.0.3

Full Changelog: actions/cache@v5...v5.0.3

v5.0.2

v5.0.2

What's Changed

When creating cache entries, 429s returned from the cache service will not be retried.

Notes

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA).

Worth running the workflows on a branch before merging to make sure everything still works.

Validation Warnings

The following issues were detected by actionlint:

• presubmit.yml: ../../../../../tmp/tmpudba8296/shell-encryption/.github/workflows/presubmit.yml:30:15: label "ubuntu-24.04-64core" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2025-vs2026", "windows-2022", "windows-11-arm", "ubuntu-slim", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "macos-latest", "macos-latest-xlarge", "macos-latest-large", "macos-26-xlarge", "macos-26-large", "macos-26", "macos-15-intel", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xlarge", "macos-14-large", "macos-14", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file [runner-label]
• presubmit.yml: |
• presubmit.yml: 30 | labels: ubuntu-24.04-64core