-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Upgrade GitHub Actions for Node 24 compatibility #2984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: staging
Are you sure you want to change the base?
Upgrade GitHub Actions for Node 24 compatibility #2984
Conversation
|
@salmanmkc is attempting to deploy a commit to the Sim Team on Vercel. A member of the Team first needs to authorize it. |
Greptile SummaryThis PR upgrades GitHub Actions to their latest versions to ensure compatibility with Node 24, which will become the default runtime on March 4th, 2026, as Node 20 approaches end-of-life in April 2026. All 9 workflow files are consistently updated with the following action version upgrades: Confidence Score: 5/5
Important Files Changed
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@salmanmkc please rebase now that I've changed the head to staging instead of main |
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
1d027af to
3b6d13e
Compare
thanks, done |
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/cachev4v5actions/checkoutv4v6actions/setup-nodev4v6actions/setup-pythonv5v6Context
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
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.