chore(ci): pin actions to immutable commit SHAs - #14
Conversation
yordis
commented
Sep 2, 2026
- Mutable tags let an upstream maintainer change what runs here after the fact, and pinning is a prerequisite for turning on the organization SHA pinning policy without taking CI down.
Mutable tags let an upstream maintainer change what runs in CI after review. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryLow Risk Overview Affected actions: Reviewed by Cursor Bugbot for commit e7a03f0. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe CI and release workflows now pin GitHub Actions to immutable commit SHAs. Existing version comments, Go configuration, and workflow behavior remain unchanged. ChangesWorkflow action pinning
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This change makes CI and release automation use immutable action revisions without altering the workflows’ intended behavior. No actionable merge-blocking risk remains beyond normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) ✨ 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 |