chore(ci): bump governance-reusable pin to standards main - #55
Conversation
The pinned revision carries bugs that make Governance red on every consumer: the Workflow security linter runs update-actions-lock.sh from the CALLER's checkout where it does not exist (exit 127), and Allowlist Preflight runs check-actions-policy.sh with an empty GH_TOKEN (exit 3). Both are fixed on standards main. Witnessed green on hyperpolymath/blocky-writer at this exact SHA: governance run completed/success, 15/15 jobs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details
|
| Layer / File(s) | Summary |
|---|---|
Update reusable workflow pin.github/workflows/governance.yml | The governance job changes its reusable workflow reference from commit 84355587cb2a1f86e6882de83514a32db2646e7a to commit fad242d35291de1898242d6737ba02b74a59a2f2. |
Estimated code review effort: 1 (Trivial) | ~2 minutes
Merge Risk:⚪ Minimal · up to 90071
The governance workflow now uses the updated immutable standards workflow revision, with no current merge-blocking risk identified.
Poem
A rabbit checks the workflow pin
A newer commit hops right in
The governance path stays clear
One small change, precise and near
Ears up, the checks begin
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly identifies the CI change: it updates the pinned governance reusable workflow revision. |
| Description check | ✅ Passed | The description explains the governance failures, the pin update, and the expected fixes. It is directly related to the changeset. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
- Create stacked PR
- Commit on current branch
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 @coderabbitai help to get the list of available commands.
Uh oh!
There was an error while loading. Please reload this page.



Pinned revision
84355587ofgovernance-reusable.ymlcarries two bugs that make Governance red on every consumer:bash scripts/update-actions-lock.sh --verify-localin the caller's checkout, where the script does not exist — exit 127.check-actions-policy.shwith an emptyGH_TOKEN—ghrefuses, exit 3.Both are cured on
standardsmain (fad242d35291de1898242d6737ba02b74a59a2f2): the verifier is copied into\$RUNNER_TEMP, and the policy step is skipped when no credential is supplied.Witness: verified green on hyperpolymath/blocky-writer#55 at this exact SHA — governance run
completed/success, 15/15 jobs, including the two jobs that were red on that repo's default branch.Judge this PR by the set difference against your own default branch (which governance jobs are newly red), not by overall check colour — unrelated build failures may pre-date it.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com