Upgrade GitHub Actions for Node 24 compatibility#3
Upgrade GitHub Actions for Node 24 compatibility#3salmanmkc wants to merge 1 commit intotwosigma:masterfrom
Conversation
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
|
Hey, thanks for this! I'll review next week. I'm also working on rebasing to OpenJDK 25. Mind if I ask you whether you've been using this, how you found it, and what feedback you might have? You don't have to answer, naturally, but answers might help me get this integrated upstream! |
Been using it across various repositories, how I found it, well it was because I worked on the node 24 upgrade for actions. This link should help answer a lot https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ |
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
actions/cachev3v5actions/checkoutv3v6actions/github-scriptv6v8actions/upload-artifactv3v6Context
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
overwrite: trueif you need the old overwrite behaviorSecurity 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.