fix(ci): add the Actions lockfile and re-pin stale reusables - #465
Conversation
Every governance and Hypatia run here is `startup_failure` — not failing,
never starting. Two causes, and the second is invisible until the first is
fixed.
NO LOCKFILE. Workflow-lockfile enforcement is active on this account and this
repository had no .github/workflows/actions.lock, so every workflow was
rejected before any job was created: no log, no check run, no row in
`gh pr checks`.
TWO STALE REUSABLE PINS — 81dbf2dd (2026-06-27) across 3 files and e9c88887
across 2. Re-pinned to standards bd0df9ead7fa, the commit that made the
governance check lockfile-aware.
That combination also explains a misdiagnosis worth recording. Because the
workflow never emitted its status context, the branch rule requiring
`governance / Validate Hypatia Baseline` looked like a PHANTOM — a rule naming
something that does not exist. It is not: the rule is correct and the workflow
is broken. Rewriting the rule would have turned "this check is broken" into
"this check is not required".
Applied the four-step cure proven across this campaign, in order, because each
step's failure is invisible until the previous one is fixed:
1. gh actions-lock generates the lockfile and normalises pins to tags.
2. Hoist SPDX back to line 1 — actions-lock inserts its own banner there and
the workflow linter requires SPDX first, so the tool that cures the
startup failures reddens all 20 workflow files unless this is undone.
3. Hand-author an empty [] lockfile entry for each of the 5 reusable-workflow
callers. gh actions-lock SKIPS callers, so without this they stay
startup_failure while everything else goes green.
4. Re-pin the callers.
Verified: all 20 workflows parse, SPDX is on line 1, and the lockfile carries
5 caller entries.
Expect previously-unseen failures — nothing here has been checked in a long
time, so the first green run is a starting point rather than a result.
Found by the estate CI/CD census (hyperpolymath/standards#583).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Jonathan D.A. Jewell <6759885+hyperpolymath@users.noreply.github.com>
|
Note Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime. Code Review ✅ ApprovedAdds the missing GitHub Actions lockfile and re-pins stale reusable workflows to resolve startup failures across governance and Hypatia runs. No issues found.
OptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
Important Your trial ends in 4 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more. Was this helpful? React with 👍 / 👎 | Gitar |
Every governance and Hypatia run here is
startup_failure— not failing, never starting. Two causes, and the second is invisible until the first is fixed.1. No lockfile
Workflow-lockfile enforcement is active on this account and this repo had no
.github/workflows/actions.lock, so every workflow was rejected before any job was created — no log, no check run, no row ingh pr checks.2. Two stale reusable pins
81dbf2dd(2026-06-27) across 3 files, ande9c88887across 2. Re-pinned to standardsbd0df9ead7fa— the commit that made the governance check lockfile-aware.Why this was misdiagnosed
Because the workflow never emitted its status context, the branch rule requiring
governance / Validate Hypatia Baselinelooked like a phantom. It isn't — the rule is correct and the workflow is broken. Rewriting the rule would have turned "this check is broken" into "this check is not required".The cure, in order
Each step's failure is invisible until the previous one is fixed:
gh actions-lock— generates the lockfile, normalises pins to tagsactions-lockputs its banner there and the linter requires SPDX first, so the tool that cures the startup failures would otherwise redden all 20 workflow files[]lockfile entries for the 5 reusable callers —actions-lockskips callers, so without this they staystartup_failurewhile everything else goes greenVerified: all 20 workflows parse, SPDX on line 1, 5 caller entries in the lockfile.
Expect previously-unseen failures. Nothing here has been checked in a long time; the first green run is a starting point, not a result.
Found by the estate CI/CD census (hyperpolymath/standards#583).
🤖 Generated with Claude Code