fix(governance): bootstrap CodeQL and Strix security gates - #730
fix(governance): bootstrap CodeQL and Strix security gates#730seonghobae wants to merge 1 commit into
Conversation
|
Warning Review limit reached
Next review available in: 13 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 (4)
Comment |
|
@coderabbitai review Please review exact bootstrap head |
|
✅ Action performedReview finished.
|
|
Superseded by #731, which contains the identical four-file CodeQL/Strix baseline repair plus the fail-closed stale protected-base pin classifier needed to unblock dependency-upgrade PR coverage. Closing this narrower duplicate avoids duplicate required-check load; #731 remains subject to exact-head checks and independent review. |
Protected-check bootstrap
The current default branch has two independent defects that form a merge deadlock:
codeql-pr.ymlandscheduled-security-scan.ymlmix CodeQL Action 4.37.0 and 4.37.4, so the existing one-version-per-workflow contract fails during central coverage evidence;aiohttp==3.14.1andcryptography==49.0.0, so Python Security fails even for otherwise clean workflow-only pull requests.A workflow-only PR cannot pass Python Security, while dependency/resolver PRs cannot receive clean central review evidence from the inconsistent CodeQL base. This PR is the minimal four-file bootstrap that fixes both causes without suppressing either gate.
Change
init,analyze, andupload-sarifsteps in the two canonical workflows to immutable v4.37.4;aiohttp==3.14.3andcryptography==50.0.0while preserving the existing direct dependency surface andprotobuf<7compatibility;Verification basis
The identical four-file tree at commit
54aa21b59c6c2cba28c7c2289ced62005b4b5906completed CodeQL, Python Security, Security Scan, Semgrep, Secret Scan, OSV, Scorecard, and SBOM successfully. This new branch rebases exactly that verified tree onto currentmainas one commit,77522a050383369187dfb5ecac055036c678e47d.Current-head checks and independent approval remain mandatory before merge. After this bootstrap, the npm-workspace resolver PR can be rebuilt against the corrected base and the obsolete duplicate CodeQL PRs remain closed.