chore(ci): bump governance-reusable pin to standards main - #55
Conversation
The pinned revision 84355587 of governance-reusable.yml carries two bugs that make Governance red on every consumer that uses it: - Workflow security linter runs 'bash scripts/update-actions-lock.sh --verify-local' inside the CALLER's checkout, where that script does not exist (exit 127). - Allowlist Preflight runs check-actions-policy.sh with an empty GH_TOKEN, so gh refuses and the script returns 3. Both are already fixed on standards main: the script is copied out of the standards checkout into RUNNER_TEMP, and the policy step is skipped when no credential is supplied. 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 reference.github/workflows/governance.yml | The governance job now references commit fad242d35291de1898242d6737ba02b74a59a2f2 of the shared governance workflow. |
Estimated code review effort: 1 (Trivial) | ~2 minutes
Merge Risk:⚪ Minimal · up to 0d0f7
The governance workflow now uses an updated pinned shared workflow revision intended to fix baseline governance failures. No current merge-blocking risk is identified.
Poem
A rabbit checks the workflow line
A newer governance commit will shine
The job points to standards anew
With one small change in view
Hop, hop, the update is through
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly and concisely identifies the governance pin update, which is the main change in the pull request. |
| Description check | ✅ Passed | The description accurately explains the governance workflow failures, the pin update, and the expected validation outcome. |
| 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.
🔍 Hypatia Security ScanFindings: 58 issues detected
View findings[
{
"reason": "Issue in scorecard.yml",
"type": "missing_workflow",
"file": "scorecard.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "codeql.yml lists `language: javascript-typescript` but the repo has no source files in any CodeQL-scannable language. The analyze job will exit 'no source files' on every run. Switch the matrix to `actions` (which scans workflow files — every repo has those).",
"type": "codeql_language_matrix_mismatch",
"file": "codeql.yml",
"action": "switch_codeql_matrix_to_actions",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in boj-build.yml",
"type": "missing_timeout_minutes",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in ci.yml",
"type": "missing_timeout_minutes",
"file": "ci.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in ci.yml",
"type": "missing_timeout_minutes",
"file": "ci.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in hypatia-scan.yml",
"type": "missing_timeout_minutes",
"file": "hypatia-scan.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in instant-sync.yml",
"type": "missing_timeout_minutes",
"file": "instant-sync.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
standards main advanced 5 commits since this branch was cut. Both cures (RUNNER_TEMP verifier copy; GH_TOKEN presence guard) survive at the new head, but a pin is verified by a green run, not by a YAML diff — so pin to the head the sweep will actually use and re-run the witness. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🔍 Hypatia Security ScanFindings: 59 issues detected
View findings[
{
"reason": "Issue in scorecard.yml",
"type": "missing_workflow",
"file": "scorecard.yml",
"action": "create",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "codeql.yml lists `language: javascript-typescript` but the repo has no source files in any CodeQL-scannable language. The analyze job will exit 'no source files' on every run. Switch the matrix to `actions` (which scans workflow files — every repo has those).",
"type": "codeql_language_matrix_mismatch",
"file": "codeql.yml",
"action": "switch_codeql_matrix_to_actions",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in boj-build.yml",
"type": "missing_timeout_minutes",
"file": "boj-build.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in casket-pages.yml",
"type": "missing_timeout_minutes",
"file": "casket-pages.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in ci.yml",
"type": "missing_timeout_minutes",
"file": "ci.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in ci.yml",
"type": "missing_timeout_minutes",
"file": "ci.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in hypatia-scan.yml",
"type": "missing_timeout_minutes",
"file": "hypatia-scan.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in instant-sync.yml",
"type": "missing_timeout_minutes",
"file": "instant-sync.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Pinned revision `7fdc2705` 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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Pinned revision `7fdc2705` 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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Pinned revision `bd0df9ea` 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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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](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> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 (a3308ea8d0cc513727c8ad149b1132317a886c98): the script is copied from the standards checkout into$RUNNER_TEMP, and the policy step is skipped when no credential is supplied.Pilot for an estate-wide pin bump. Pass criterion is the set difference against this repo's own baseline (run 33820393808:
Allowlist Preflight+Workflow security linterred) — both gone, no new red job.Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com