fix(ci): keep CodeQL Action versions consistent - #723
Conversation
Bumps [github/codeql-action/analyze](https://github.com/github/codeql-action) from 4.37.0 to 4.37.4. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](github/codeql-action@99df26d...f205ea1) --- updated-dependencies: - dependency-name: github/codeql-action/analyze dependency-version: 4.37.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…-action/analyze-4.37.4
|
Warning Review limit reached
Next review available in: 36 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)
📝 WalkthroughWalkthroughPR 헤드, 병합 미리보기, 예약 보안 스캔 워크플로의 CodeQL ChangesCodeQL 액션 버전 업데이트
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
seonghobae
left a comment
There was a problem hiding this comment.
Re-evaluate the exact current head after the workflow-version contract repair and current security checks.
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
seonghobae
left a comment
There was a problem hiding this comment.
Please re-evaluate the exact current head after the CodeQL action-version consistency repair. The direct current-head security workflows and CodeRabbit check are green, and there are no unresolved review threads.
Pull request was converted to draft
| - .github/workflows/one-shot-refresh-strix-lock.yml | ||
|
|
||
| permissions: | ||
| contents: write |
Problem
The default branch currently mixes CodeQL Action 4.37.0 for
init/analyzewith 4.37.4 forupload-sarifinscheduled-security-scan.yml. The repository contract requires one CodeQL Action ref per workflow, so the central coverage-evidence suite fails for otherwise unrelated pull requests.Change
github/codeql-action/init,analyze, andupload-sarifreference incodeql-pr.ymlandscheduled-security-scan.ymlto the same pinned 4.37.4 commit;Validation
tests/test_codeql_pr_workflow_contract.py::test_codeql_action_steps_use_one_version_per_workflowpasses on the merge tree;Supersedes #720, whose branch was edited by an automation and can no longer be rebased by Dependabot.
Summary by CodeRabbit