You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
actions.lock still pins hyperpolymath/standards for 7 callers moved to metadatastician/standards #212
.github/workflows/actions.lock on main (7a5b8c4) does not match the workflows. In v0.2.0 the lockfile tool, gh-actions-lock, reports each mismatch as a stale error.
Seven caller workflows have entries for hyperpolymath/standards@740c9d7d4ed4d1f319a04c92b28218beb75668d7, but #203 changed their uses: lines to metadatastician/standards:
codeql.yml
governance.yml
hypatia-scan.yml
mirror.yml
rust-ci.yml
scorecard.yml
secret-scanner.yml
The estate wrapper accepts a stale entry only when the workflow contains that exact owner/repo/...@ref reusable dependency. These seven don't, so update-actions-lock.sh --verify-local from standards fails on main today.
The follow-up PR that removes the duplicate Hypatia job from static-analysis-gate.yml adds one more stale entry: erlef/setup-beam@v1.24.1 for that workflow.
How it was found
On 2026-11-17 I built gh-actions-lock v0.2.0 (d5dca22) from source and ran --verify-local --json=valid,findings at the echidnabot root. Two runs gave these results:
Run through the estate wrapper (GH_BIN=<shim> bash scripts/update-actions-lock.sh --verify-local, taken from standards ea2f4d8, the pin in governance.yml): exit 1 on main's tree.
Fix mode, which regenerates the lock: the result must not be used. The tool doesn't recognise reusable workflows, so it dropped every hyperpolymath/standards caller entry and 15 transitive SHA pins. The estate wrapper says GitHub's startup enforcement needs those entries. In that session the tool also couldn't verify any pin, because GraphQL was unavailable.
What to do
From the echidnabot root, with your own gh auth, run the estate wrapper rather than bare gh actions-lock. The wrapper keeps the reusable-workflow and transitive coverage:
Commit the lockfile change on its own, then rebase or merge the job-removal PR on top of it. Per the owner's rules the lockfile is tool-owned and must not be edited by hand.
#185 - fix(ci): re-pin standards reusables and repair actions.lock [merged] #207 - docs(state): record 2 open CI items that wait for the owner [merged] #203 - ci: name the standards repository by its current owner in 5 callers [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Nov 17, 2026
🔗 Related PRs
#185 - fix(ci): re-pin standards reusables and repair actions.lock [merged]
#207 - docs(state): record 2 open CI items that wait for the owner [merged]
#203 - ci: name the standards repository by its current owner in 5 callers [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
ci(static-analysis-gate): drop the second Hypatia scan (#213)