fix(actions): pin security.yml jobs off starved floating ubuntu-latest - #1072
fix(actions): pin security.yml jobs off starved floating ubuntu-latest#1072seonghobae wants to merge 3 commits into
Conversation
Live GitHub Actions queue audit while investigating hours-long queued checks on other PRs found that this repo's own security.yml (Tests and package quality, Property and coverage-guided fuzzing, CodeQL/supply chain/SBOM) still requests the unpinned floating ubuntu-latest image. ContextualWisdomLab/.github already root-caused and fixed this exact starvation pattern for its central required review workflows in #1870; this repo's own security.yml was outside that fix's scope. Pin all 3 jobs to ubuntu-24.04 as defensive, evidence-based consistency with the established org pattern. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KPmJErfkcHer4UVEgrQxUX
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough보안 워크플로의 세 작업이 Changes보안 워크플로 러너 고정
Estimated code review effort: 1 (매우 낮음) | ~5분 Merge Risk: ⚪ Minimal · up to Security workflow jobs now use the explicit Ubuntu 24.04 runner, with matching metadata coverage and changelog documentation. No current merge-readiness risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (2 skipped: 2 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
Small follow-up per CodeRabbit's diff-scoped docstring check on #1072: the test function this PR's assertion change lives in never had a docstring on main. This repo's own interrogate gate excludes tests/ (pyproject.toml), so this isn't a required-check fix -- just cleaning up the one warning CodeRabbit's real review flagged for a fully green pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KPmJErfkcHer4UVEgrQxUX
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Coordination note, not an action needed from anyone right now: this PR's Generated by Claude Code |
Current exact boundary
main@a080297d2546bb61e89520d637cabc202db331ec730801abfc53d46fb377c1be8b48857d89f6588cahead_by=3,behind_by=0; effective protected-base delta remains exactly 3 filesValid intent
The repo-local
.github/workflows/security.ymlstill used floatingubuntu-latestfor all three local quality/security jobs. Central.github#1870already established the same defensive pin pattern for required review infrastructure after a live 30-run sample found 14 queued and 0 clean successes. This PR applies that already-reviewed owner pattern locally without claiming runner-image pinning can cure the current hosted-capacity backlog.Changes retained after restack
.github/workflows/security.yml: all 3runs-onvalues are explicitubuntu-24.04.tests/test_repository_security_metadata.py: requires exactly threeubuntu-24.04jobs and rejectsubuntu-latestin this workflow.CHANGELOG.md: records the local defensive runner pin under0.2.0 - Unreleased.Non-force restack evidence
Protected
mainadvanced by #1073 from the original PR base2e414d15...toa080297d.... #1073 changesnim_benchmarksource/docs/tests and does not overlap this PR's three-file delta. The branch was advanced with a normal two-parent descendant commit, preserving both histories; no force-push or destructive rebase was used. Fresh compare from current protected main to this head isbehind_by=0, and the only effective files remain the workflow, its repository contract test, and CHANGELOG.Exact-head gates
The CodeQL "compatibility analysis" checks on this PR follow a known dispatch-and-poll design: a job dispatches a
codeql-scanevent to.github, polls for an authenticated verdict, and deliberately exits non-zero with "pending" until the dispatch workflow republishes a terminal verdict and reruns this exact job itself — self-resolving, not a real failure requiring a fix here.Keep Draft until current-head required checks, review, and thread gates are terminal-valid. Do not use no-op retriggers, bypass merge, self-approval, or gate weakening.
Generated by Claude Code