ci(scheduled-security-scan): align codeql-action refs to v4.37.4 - #738
ci(scheduled-security-scan): align codeql-action refs to v4.37.4#738seonghobae wants to merge 1 commit into
Conversation
Dependabot bumped only the upload-sarif step to v4.37.4 (#719), leaving init/analyze at v4.37.0 in the same workflow. The contract test test_codeql_action_steps_use_one_version_per_workflow requires a single github/codeql-action ref per workflow file, so bump init/analyze to the same f205ea1c (v4.37.4) pin. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 28 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 Plus Run ID: 📒 Files selected for processing (1)
Comment |
|
Superseded by #731, which applies the same scheduled-security-scan CodeQL ref alignment together with the codeql-pr alignment and the Strix/stale-pin baseline repairs required for the central repository’s current gates to pass atomically. Keeping this narrower PR open would duplicate the same workflow edit and create avoidable conflicts/check load. |
Pull request was closed
What changed
Bumped the
github/codeql-action/initandgithub/codeql-action/analyzesteps in.github/workflows/scheduled-security-scan.ymlfrom99df26d4(v4.37.0) tof205ea1c(v4.37.4), matching theupload-sarifstep in the same file.Why
#719 (Dependabot) bumped only the
upload-sarifstep, leaving the workflow with mixedgithub/codeql-actionrefs. The contract testtests/test_codeql_pr_workflow_contract.py::test_codeql_action_steps_use_one_version_per_workflowrequires one ref per workflow file, so it fails on the current tree.Notes for reviewers
codeql-pr.ymlstill pins v4.37.0 but is internally consistent, so the contract passes; Dependabot will bump it as a unit.python -m pytest tests/test_codeql_pr_workflow_contract.py -q→ 3 passed.🤖 Generated with Claude Code