fix(ci): codeql-action v4.38.1 -> v4.38.0 SHA pin + dependabot hold (estate-wide startup_failure) - #119
Conversation
v4.38.1 (tag AND commit SHA 1c5b675) fails GitHub workflow-startup validation estate-wide: codeql/hypatia runs die with startup_failure, zero jobs, no API error text. Full investigation: nexia-list#100. Rollback to the v4.38.0 commit b96794f015dfd88f77b49b1c93e0fa7110f94c63 (green on deed-ecosystem; satisfies repo SHA-pin policy). actions.lock re-keyed where present; dependabot held unconditionally (versions-scoped ignores were bypassed in SHA form - nexia-list#101). Canonical fix: hyperpolymath/standards#973.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (13)
🔇 Additional comments (2)
📝 SummarySummary by CodeRabbit
WalkthroughThe CodeQL workflow now uses the pinned v4.38.0 action. Dependabot ignores updates for ChangesCodeQL action pinning
Priority: ⬆️ High Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to CodeQL remains pinned while Dependabot updates are held, avoiding the reported failing release; the change is ready to merge with normal checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. A rabbit checks the workflow line Comment ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
|
Summary
Estate-wide incident:
github/codeql-actionv4.38.1 fails GitHub workflow startup on every repo that took it — CodeQL/Hypatia runs die withstartup_failure, zero jobs dispatched, no error text in any API surface. The evidence chain (full detail: nexia-list#100):@v4.38.1tag (via dependabot #94)@1c5b675(4.38.1 SHA)@v4.38.1@1c5b675The v4.38.1 tag exists (peels to
1c5b675) and byte-identical workflow content runs under a fresh path — so the failure is the version value itself at GitHub's start-validation layer, not content, permissions (probes withsecurity-eventsstart fine), or the default-setup conflict.Changes here
codeql-reusable.yml,hypatia-scan-reusable.yml:codeql-action/*re-pinned1c5b675(v4.38.1) →b96794f0(v4.38.0 commit; wrong# v3comments corrected to# v4.38.0).actions.lock: re-keyed to the v4.38.0 SHA entries (dependabot bumped the reusable pins without regenerating the lock).dependabot.yml: full hold ongithub/codeql-action— scopedversions:ignores do NOT hold for this bot path (nexia-list#101 re-raised the bump in SHA form within an hour, copying the inline warning comment verbatim while swapping the SHA).Follow-ups
Consumer rollbacks shipped in the same batch: nexia-list (merged ✅), hypatia, vexometer, rsr-template-repo, metadatastician/burble (each with the same dependabot hold). Reconsider the hold when upstream clears v4.38.1 or a newer release verifies green on one canary repo.