ci(security): SHA-pin every third-party action to a 40-char commit SHA#320
Conversation
The scheduled `SAST — semgrep` gate flags `github-actions-mutable-action-tag` on every `uses:` pinned to a movable tag (@v4, @v6, …) — ~65 of the 69 blocking findings that have failed the nightly `security` run since 2026-06-18. security.yml already SHA-pins its own steps and documents the mandatory 40-char-SHA pinning policy; the other workflows predate that tightening. Resolve each movable tag to the commit it currently points to and pin to the 40-char SHA with a trailing `# vX.Y.Z` comment. Pin-only — no version upgrades; every SHA is exactly what the tag resolves to today. 67 substitutions across 9 workflow files. All files parse under PyYAML. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 35 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
✨ 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 |
1 participant
Why
The scheduled
SAST — semgrepgate has flaggedyaml.github-actions.security.github-actions-mutable-action-tagon everyuses:pinned to a movable tag — ~65 of the 69 blocking findings failing the nightlysecurityrun since 2026-06-18.security.ymlalready SHA-pins its own steps and documents the mandatory 40-char-SHA pinning policy (lines ~18-24); the other workflows predate that tightening and were never migrated.Companion PR #319 clears the trufflehog job and the 4
dependabot-missing-cooldownfindings. Together the two PRs return the nightlysecurityrun to green.Changes
Pin-only — every SHA is exactly what the tag resolves to today; no version upgrades. 67 substitutions across 9 workflow files, each with a trailing
# vX.Y.Zcomment.34e114876b0b11c390a56381ad16ebd13914f8d5/df4cb1c069e1874edd31b4311f1884172cec0e1049933ea5288caeca8642d1e84afbd3f7d6820020a26af69be951a213d495a4c3e4e4022e16d87065eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a8991a275c3b69536ee54be43f2070a358922e12c8d453b7df96c91f9c12dcc8a07bcb9ccacbed38856ac94ce9fb468520275223c153574b00df6fe4bcc980c7e94dd9b9319bd5eb7a0e0fe9291e23a2a2e9d7f5e7f509e45cec5c76c4d5afdd7de93d0b3df5dd903d2e4f5405488e5ef1422510ee31c8b32357cae68fefc6b5f367a0275617c9f83181ba54714f8646ba30535128ac92d33dfc9133794bfdd9b4113bb12739c298aeb8a4eeaf626c5b8d85266b0e65d89dee975228ae261d22c15adcd03578634d429ceb5ca3ab411449c66620fe7f1b3c9e10547144b0Verification
@vNtag remains in.github/workflows/..github/workflows/*.ymlparse under PyYAML.🤖 Generated with Claude Code