Repository navigation
fix: retain rejected attestation challenges - #24
Conversation
Use the exact certificate identity selector without the mutually exclusive signer-workflow flag, capture verifier diagnostics, and retain evidence even when the challenge fails.
|
Warning Review limit reached
Next review available in: 31 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: defaults Review profile: CHILL Plan: Pro 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 |
Fixes the exact failure observed in protected publication run
29708636210.Root cause
GitHub CLI 2.96.0 rejects simultaneous
--cert-identityand--signer-workflowselectors as mutually exclusive. The run reached pinned tool installation, isolated Lean verification, and Sigstore attestation before failing at that argument contract.Focused correction
always()so failed challenges remain visibleEvidence
6c1396d3620405f0bb33a469e185b55c8080ad56No authority is created by this correction.