Skip to content

chore(ci): bump governance-reusable pin to standards main - #78

Merged
hyperpolymath merged 2 commits into
mainfrom
chore/bump-governance-pin-to-standards-main
Sep 8, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
chore/bump-governance-pin-to-standards-main

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Pinned revision 81dbf2dd of governance-reusable.yml carries two bugs that make Governance red on every consumer:

  1. Workflow security linter runs bash scripts/update-actions-lock.sh --verify-local in the caller's checkout, where the script does not exist — exit 127.
  2. Allowlist Preflight runs check-actions-policy.sh with an empty GH_TOKEN — gh refuses, exit 3.

Both are cured on standards main (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

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>
@coderabbitai

coderabbitai Bot commented Sep 7, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 40323554-c7ac-4445-b7b2-776fa4d0d2f3

📥 Commits

Reviewing files that changed from the base of the PR and between 0605a9f and db4ae7e.

📒 Files selected for processing (1)
  • .github/workflows/governance.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⚠️ CI failures not shown inline (2)

GitHub Actions: CodeQL Advanced / 0_Analyze (javascript-typescript).txt: chore(ci): bump governance-reusable pin to standards main

Conclusion: failure

View job details

##[group]Finalizing javascript
 [command]/opt/hostedtoolcache/CodeQL/2.26.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14575 /home/runner/work/_temp/codeql_databases/javascript
 CodeQL could not process any code written in JavaScript/TypeScript. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build .
 ##[error]Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.26.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14575 /home/runner/work/_temp/codeql_databases/javascript". Exit code was 32 and last log line was: CodeQL could not process any code written in JavaScript/TypeScript. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details.

GitHub Actions: CodeQL Advanced / Analyze (javascript-typescript): chore(ci): bump governance-reusable pin to standards main

Conclusion: failure

View job details

##[group]Finalizing javascript
 [command]/opt/hostedtoolcache/CodeQL/2.26.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14575 /home/runner/work/_temp/codeql_databases/javascript
 CodeQL could not process any code written in JavaScript/TypeScript. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build .
 ##[error]Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.26.4/x64/codeql/codeql database finalize --finalize-dataset --threads=4 --ram=14575 /home/runner/work/_temp/codeql_databases/javascript". Exit code was 32 and last log line was: CodeQL could not process any code written in JavaScript/TypeScript. For more information, review our troubleshooting guide at https://gh.io/troubleshooting-code-scanning/no-source-code-seen-during-build . See the logs for more details.
🔇 Additional comments (1)
.github/workflows/governance.yml (1)

30-30: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the governance workflow to use a newer shared governance configuration.
    • Granted the governance job read-only access to workflow actions.
    • No other workflow behaviour has changed.

Walkthrough

The governance workflow now grants actions: read permission and pins the shared governance workflow to commit fad242d35291de1898242d6737ba02b74a59a2f2.

Changes

Governance workflow

Layer / File(s) Summary
Update governance workflow access and pin
.github/workflows/governance.yml
The governance job now grants actions: read permission and references the new shared governance workflow commit.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to db4ae

The governance workflow now grants the required read-only access and updates its reusable workflow to a pinned revision. No current merge-blocking risk is identified.

Suggested reviewers: metadatastician

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: updating the pinned governance reusable workflow revision.
Description check ✅ Passed The description directly explains the governance workflow failures, the revision update, the required actions: read permission, and the reported validation result.
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.

❤️ Share

A rabbit checks the workflow line
Read access joins the design
A newer pin hops into place
The job keeps its steady pace
Governance runs with a clear trace

Comment @coderabbitai help to get the list of available commands.

coderabbitai[bot]
coderabbitai Bot previously approved these changes Sep 7, 2026
The governance-reusable at standards HEAD requests `actions: read`. A caller
granting only `contents: read` fails at startup after the pin bump, reporting
no check at all. This grants the missing scope in the same PR as the bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@hyperpolymath
hyperpolymath merged commit dc203de into main Sep 8, 2026
27 of 28 checks passed
@hyperpolymath
hyperpolymath deleted the chore/bump-governance-pin-to-standards-main branch September 8, 2026 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant