Skip to content

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

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

hyperpolymath merged 1 commit into
mainfrom
chore/bump-governance-pin-to-standards-main

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Pinned revision 84355587 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>
@sonarqubecloud

sonarqubecloud Bot commented Sep 7, 2026

Copy link
Copy Markdown

@coderabbitai

coderabbitai Bot commented Sep 7, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 8f43d93a-a214-4601-aa0e-e5e99373a543

📥 Commits

Reviewing files that changed from the base of the PR and between 04aafbd and e301a63.

📒 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
⏰ Context from checks skipped due to timeout. (7)
  • GitHub Check: governance / Validate Hypatia Baseline
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: governance / Allowlist Preflight
  • GitHub Check: governance / Debt ratchet
  • GitHub Check: governance / Live Actions policy (credentialed advisory)
  • GitHub Check: governance / Guix packaging policy (Nix retired)
  • GitHub Check: backend-test
⚠️ CI failures not shown inline (4)

GitHub Actions: Workflow Security Linter / 0_lint-workflows.txt: chore(ci): bump governance-reusable pin to standards main

Conclusion: failure

View job details

##[group]Run errors=0
 �[36;1merrors=0�[0m
 �[36;1mfor f in .github/workflows/*.yml .github/workflows/*.yaml; do�[0m
 �[36;1m  [ -f "$f" ] || continue�[0m
 �[36;1m  if ! head -1 "$f" | grep -q "SPDX-License-Identifier"; then�[0m
 �[36;1m    echo "ERROR: $f missing SPDX header"�[0m
 �[36;1m    errors=$((errors + 1))�[0m
 �[36;1m  fi�[0m
 �[36;1mdone�[0m
 �[36;1mexit $errors�[0m
 shell: /usr/bin/bash -e {0}
 ##[endgroup]
 ERROR: .github/workflows/deploy-now.yaml missing SPDX header
 ##[error]Process completed with exit code 1.

GitHub Actions: Deploy Now / 0_deploy-now.txt: chore(ci): bump governance-reusable pin to standards main

Conclusion: failure

View job details

##[group]Run ionos-deploy-now/retrieve-project-info-action@v1.5.2
 with:
   api-key: ***
   project: ***
   service-host: api-eu.ionos.space
 ##[endgroup]
 (node:2819) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
 (Use `node --trace-deprecation ...` to show where the warning was created)
 ##[error]Branch chore/bump-governance-pin-to-standards-main not found in DeployNow

GitHub Actions: Workflow Security Linter / lint-workflows: chore(ci): bump governance-reusable pin to standards main

Conclusion: failure

View job details

##[group]Run errors=0
 �[36;1merrors=0�[0m
 �[36;1mfor f in .github/workflows/*.yml .github/workflows/*.yaml; do�[0m
 �[36;1m  [ -f "$f" ] || continue�[0m
 �[36;1m  if ! head -1 "$f" | grep -q "SPDX-License-Identifier"; then�[0m
 �[36;1m    echo "ERROR: $f missing SPDX header"�[0m
 �[36;1m    errors=$((errors + 1))�[0m
 �[36;1m  fi�[0m
 �[36;1mdone�[0m
 �[36;1mexit $errors�[0m
 shell: /usr/bin/bash -e {0}
 ##[endgroup]
 ERROR: .github/workflows/deploy-now.yaml missing SPDX header
 ##[error]Process completed with exit code 1.

GitHub Actions: Deploy Now / deploy-now: chore(ci): bump governance-reusable pin to standards main

Conclusion: failure

View job details

##[group]Run ionos-deploy-now/retrieve-project-info-action@v1.5.2
 with:
   api-key: ***
   project: ***
   service-host: api-eu.ionos.space
 ##[endgroup]
 (node:2819) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
 (Use `node --trace-deprecation ...` to show where the warning was created)
 ##[error]Branch chore/bump-governance-pin-to-standards-main not found in DeployNow
🔇 Additional comments (1)
.github/workflows/governance.yml (1)

19-19: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the governance workflow to use the latest approved revision of its reusable standards workflow.

Walkthrough

The governance job now references a newer pinned commit of the reusable hyperpolymath/standards workflow.

Changes

Governance workflow update

Layer / File(s) Summary
Update governance workflow reference
.github/workflows/governance.yml
The governance job now uses commit fad242d35291de1898242d6737ba02b74a59a2f2 of the reusable workflow.

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

Merge Risk: ⚪ Minimal · up to e301a

The governance workflow now uses the updated pinned reusable workflow revision, restoring its credential-aware preflight behavior without introducing mutable workflow references. No merge-blocking risk is identified.

Poem

A rabbit checks the workflow line
A newer pin is set in time
Governance hops along
The reference stays strong
And every green check sings fine

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description check ✅ Passed The description clearly explains the governance workflow pin update, the two corrected failures, and the verification result.
Title check ✅ Passed The title concisely identifies the CI governance pin update and matches the main change in the pull request.
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

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

@hyperpolymath
hyperpolymath merged commit 3c4d727 into main Sep 8, 2026
31 of 39 checks passed
@hyperpolymath
hyperpolymath deleted the chore/bump-governance-pin-to-standards-main branch September 8, 2026 06:50
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