ci: pin GitHub Actions to commit SHAs (7)#953
Conversation
|
@mirkosalvato1-ctrl is attempting to deploy a commit to the HackerAI Team on Vercel. A member of the Team first needs to authorize it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughChangesGitHub Actions pinning
Estimated code review effort: 1 (Trivial) | ~3 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8).github/workflows/desktop-build.ymlTraceback (most recent call last): .github/workflows/docker-sandbox.ymlTraceback (most recent call last): .github/workflows/test.ymlTraceback (most recent call last): 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 |
Why
Mutable Action tags (
@v4,@main) can be retagged, which is a supply-chain risk.This PR pins third-party Actions to full commit SHAs while keeping the tag in a comment.
Official
actions/*tags are left unchanged (common maintainer preference).Pins
pnpm/action-setup@v6 -> 0ebf47130e48azure/trusted-signing-action@v2 -> c7ab2a863ab5docker/setup-buildx-action@v4 -> bb05f3f5519ddocker/login-action@v4 -> af1e73f918a0docker/metadata-action@v6 -> dc8028041006docker/build-push-action@v7 -> 53b7df96c91fpnpm/action-setup@v6 -> 0ebf47130e48Reference: GitHub docs on using third-party actions securely.
Summary by CodeRabbit