Upgrade GitHub Actions for Node 24 compatibility#2841
Upgrade GitHub Actions for Node 24 compatibility#2841salmanmkc wants to merge 1 commit intowavetermdev:mainfrom
Conversation
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
|
|
WalkthroughTwo GitHub Actions workflow files are updated with newer action versions. The build-helper.yml workflow bumps the upload-artifact action from v5 to v6 in two locations, the upload snapcraft logs action from v5 to v6, and the download-artifacts action from v4 to v7 in two locations. The testdriver-build.yml workflow upgrades the upload-artifact action from v5 to v6. No changes are made to control flow, conditional logic, or functional behavior—only version updates to external actions. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 🧹 Recent nitpick comments
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
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/download-artifactv4v7actions/upload-artifactv5v6Context
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.