Skip to content

Upgrade GitHub Actions for Node 24 compatibility#386

Closed
salmanmkc wants to merge 1 commit intogoogle:mainfrom
salmanmkc:upgrade-github-actions-node24
Closed

Upgrade GitHub Actions for Node 24 compatibility#386
salmanmkc wants to merge 1 commit intogoogle:mainfrom
salmanmkc:upgrade-github-actions-node24

Conversation

@salmanmkc
Copy link

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 Release Files
actions/upload-artifact bbbca2d b7c566a Release generate_release_rcs.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

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.

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
@salmanmkc salmanmkc force-pushed the upgrade-github-actions-node24 branch from 50859f3 to 6a0432e Compare March 11, 2026 21:49
@timothyfroehlich
Copy link
Member

Why do the hashes point to older versions? For instance, the hash that you're trying to set for upload-artifact corresponds to v6.0. We're already on v7.0, as the comment next to it notes.

@salmanmkc
Copy link
Author

Closing — this PR contained a version downgrade (upload-artifact v7→v6 SHA) due to a stale version map. The underlying issue has been fixed. A corrected PR will be opened if needed.

@salmanmkc salmanmkc closed this Mar 11, 2026
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