Skip to content

chore: upgrade GitHub Actions from Node 20 to Node 24#247

Merged
mcollins-ttd merged 1 commit into
mainfrom
mkc-UID2-6742-node20-to-node24-actions
Jun 9, 2026
Merged

chore: upgrade GitHub Actions from Node 20 to Node 24#247
mcollins-ttd merged 1 commit into
mainfrom
mkc-UID2-6742-node20-to-node24-actions

Conversation

@mcollins-ttd

Copy link
Copy Markdown
Contributor

Node 20 is being deprecated on GitHub Actions runners. Starting June 16, 2026, runners will use Node 24 by default.

This PR upgrades outdated action references in this repo to the latest released version that ships Node 24 support, pinned to its commit SHA. Each action's node version is determined by reading its action.yml at the pinned ref.

See: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

@mcollins-ttd mcollins-ttd left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Mechanically correct upgrade — all 8 pinned SHAs verified to match their tags, all target actions confirmed to use node24, tj-actions/changed-files v47.0.6 (2026-04-18) is well after the March 2025 CVE-2025-30066 fix, and no unpinned third-party actions remain. Repo-specific usage of inputs (aws-region/role-to-assume, configurationJson.pr_template, explicit cache:'npm') is unaffected by the v5/v6 breaking changes documented upstream. One issue: cdn_deployment_aws/action.yaml was also converted from CRLF to LF in the same commit, producing 84/84 line churn that hides the two intentional SHA bumps.

Comment thread .github/actions/cdn_deployment_aws/action.yaml
Comment thread .github/workflows/build-sdk-package.yml
Comment thread .github/workflows/build-secure-signal.yml
@mcollins-ttd mcollins-ttd merged commit 6ea4828 into main Jun 9, 2026
3 checks passed
@mcollins-ttd mcollins-ttd deleted the mkc-UID2-6742-node20-to-node24-actions branch June 9, 2026 06:14
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