test(ci): lock image gate ruleset authority - #435
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 44 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughТесты усиливают контрактные проверки ChangesRuleset-аудит
Estimated code review effort: 4 (Complex) | ~45 minutes Possibly related PRs
Poem
🚥 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 `@tests/critical/runtime/image_runtime_contract_test.go`:
- Around line 530-537: Замените глобальные проверки strings.Count в
tests/critical/runtime/image_runtime_contract_test.go:530-537 проверками
содержимого каждого отдельного шага ValidateWorkflowRun: в каждом шаге
подтвердите ровно одну привязку RULESET_AUDIT_TOKEN и одного consumer-а
-GitHubToken, а для candidate execution сохраните проверку явной очистки
credential. В tests/critical/runtime/image_runtime_contract_test.go:712-719
аналогично проверяйте MARKETPLACE_PAT и READ_ONLY_GITHUB_TOKEN внутри ожидаемых
job/step-секций, а не по всему publisher.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: f1fa8478-b415-47cd-8f16-a662fa82abc8
📒 Files selected for processing (1)
tests/critical/runtime/image_runtime_contract_test.go
Summary
Tighten the critical image-publishing contract after the protected-path repair landed.
ValidateReleaseand the productionValidateWorkflowRun -EventOnlyValidationpathbypass_actorsfields and partial credential statesVerification
go test -tags critical ./tests/critical/runtime -run TestDockerReleaseRefFreshnessGuard -count=1Summary by CodeRabbit