Allow release-assets.githubusercontent.com in source-provenance egress policy#1212
Conversation
…s policy The slsa_with_provenance action downloads the slsa-source-corroborator binary from GitHub releases, which redirects through release-assets.githubusercontent.com. This endpoint was missing from the harden-runner allowed list for the attest-source-governance job, causing the egress block and failing the main build. https://claude.ai/code/session_01FzXNiF3f5iEnRPX3SWfd2A
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR adds one endpoint ( ChangesRunner Hardening Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
The slsa_with_provenance action downloads the slsa-source-corroborator
binary from GitHub releases, which redirects through
release-assets.githubusercontent.com. This endpoint was missing from
the harden-runner allowed list for the attest-source-governance job,
causing the egress block and failing the main build.
https://claude.ai/code/session_01FzXNiF3f5iEnRPX3SWfd2A
Summary by CodeRabbit