chore(ci): pin GitHub Actions to immutable SHAs#6
Conversation
Pin checkout@v4, setup-node@v4, setup-python@v5, and dtolnay/rust-toolchain (with explicit toolchain: stable input so the ref is no longer the selector). Public flagship supply-chain hardening; Renovate owns digest updates after.
|
Warning Review limit reached
Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository: ZenSystemAI/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe CI workflow replaces floating GitHub Actions and Rust toolchain references with specific commit SHAs across repository hygiene, workbench, redaction-core, gate-floor, and Tauri Rust jobs. ChangesCI action pinning
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/ci.yml:
- Line 19: Disable checkout credential persistence for every listed
actions/checkout usage in .github/workflows/ci.yml at lines 19, 424, 456, 490,
and 534 by setting persist-credentials to false; no authenticated Git operations
are required in these test jobs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: ZenSystemAI/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 83dd07fd-3883-49b4-a1df-443987bce011
📒 Files selected for processing (1)
.github/workflows/ci.yml
The repo-hygiene checkout assertion hard-coded actions/checkout@v4. After pinning to an immutable SHA with a # v4 comment, match any actions/checkout@ uses string instead.
Summary
.github/workflows/ci.ymlto full SHAs.dtolnay/rust-toolchain: pin to master SHA +with: toolchain: stable(ref was doubling as toolchain selector).Why
Public flagship; all action refs were mutable tags.
Test plan
grep uses:shows only 40-hex-pinned refsSummary by CodeRabbit