ci: update and pin GitHub actions - #325
valentinkaas wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughCI workflows now pin third-party actions to commit SHAs. Checkout steps disable credential persistence. The lint workflow uses setup-uv for dependency caching. The regression workflow reference path also changes. ChangesCI workflow changes
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~15 minutes Change: Other Merge Risk: ⚪ Minimal · up to The workflow wiring remains supported and the action updates are pinned; no concrete CI failure risk remains established. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
This PR updates all GitHub actions to their newest versions. Furthermore, I ran zizmor on the workflows to pin the actions to specific hashes. That also auto-fixes things like using GitHub's native
$/.githubfeatures for workflows or settingpersist-credentials: falsefor the checkout action. I can just revert those changes though, if needed.Automatic updates of pinned actions versions will follow in a future pull request.
Summary by CodeRabbit