ci: pin all actions/* to commit SHAs (supply-chain hardening)#826
Conversation
|
Warning Review limit reached
More reviews will be available in 44 minutes and 43 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Pins every actions/{checkout,cache,upload-artifact,download-artifact} use to a
full commit SHA (version kept as a trailing comment so Dependabot can still bump
them). Mutable tags let a compromised or force-moved upstream action run
arbitrary code in CI with repo write + secrets. Third-party actions (codecov,
commitlint, gitleaks, dependency-review, dtolnay) were already SHA-pinned; this
closes the remaining 28 actions/* references across the workflows, including the
macOS test job. SHAs resolved from each tag via the GitHub API, not hand-written.
satyakwok
force-pushed
the
ci/pin-actions-to-sha
branch
from
761ebc8 to
93e384c
Compare
1 participant
Pins every
actions/{checkout,cache,upload-artifact,download-artifact}reference (26 across 6 workflows) to a full commit SHA, with the version kept as a trailing# vNcomment so Dependabot can still bump them.Why: tags are mutable. A compromised or force-moved upstream tag runs arbitrary code in CI with repo write access + secrets. SHA-pinning is the GitHub-recommended mitigation. The other third-party actions (codecov, commitlint, gitleaks, dependency-review, dtolnay/rust-toolchain) were already SHA-pinned — this closes the remaining
actions/*gap (the one CodeRabbit flagged on #824).All SHAs were resolved from each tag via the GitHub API (
repos/<action>/commits/<tag>), not hand-written; 3 spot-checked against the live commit. No behaviour change — same action versions, just immutable references.