chore: pin third-party actions to commit SHAs - #320
Conversation
Tags are mutable, so a moved tag silently changes what runs in CI. The version each SHA came from is kept as a trailing comment. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe release job now references ChangesRelease workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The release workflow keeps the same action version while preventing mutable-tag changes, with no remaining merge-blocking risk identified. 🚥 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 |
Pins every non-GitHub-owned action in this repo to a full-length commit SHA, keeping the version tag as a trailing comment.
A tag is a moving pointer — whoever controls the upstream repo (or compromises that maintainer's account) can repoint it and change what executes here. These steps run with
contents: writeor cloud credentials in scope, so that matters.No version changes: each SHA is the exact commit the pinned tag resolved to today. Part of a sweep across the org so
sha_pinning_requiredcan be turned on afterwards.Summary by CodeRabbit