Repository navigation
fix(ci): lock record with nested uses for mirror.yml (startup_failure) - #1169
Merged
Merged
Conversation
mirror.yml has been startup_failure on every head since 2026-10-05. Its lock record 571cc734 carries no nested `uses:`, and the callee at that SHA pins dtolnay/rust-toolchain@6c977a6, which has no record. Working peers (cicd-squabbler, mirror green; burble) key the same kind of record WITH a nested uses list. Relates to #992. Repin mirror.yml to b935e63 (its mirror-reusable pins only recorded refs) and generate the record via the repair chain: complete-job-refs -> build-dep-records -> close-lock -> prune-stale. close-lock also closed a pre-existing dangling transitive edge, actions/setup-python@v2, named by the asana/push-signed-commits record. The 571cc73 record stays: ci-pipeline.yml still names it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012kgrMQRhSmZMBbF9Ui1zBw
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 56 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
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 |
Contributor
K9 contract conformancerun https://github.com/hyperpolymath/standards/actions/runs/37498174105 K9 normative contract typecheckK9 contract self-testK9 conformance fixtures |
|
Contributor
|
Add Carrot credits or activate Agent usage billing to use Autopilot |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mirror.ymlhas beenstartup_failureon every head since 2026-10-05 (8 of 8 latest runs, last at 44a0de4). Two defects in its lock entry:hyperpolymath/standards@571cc734carries no nesteduses:list. The working peers key the same kind of record with one:hyperpolymath/cicd-squabbler(mirrorsuccessat a4cd088) andmetadatastician/burble.mirror-reusable.yml@571cc734pinsdtolnay/rust-toolchain@6c977a6, which has no record in this lock.This PR re-pins
mirror.ymltob935e63(current main). There,mirror-reusable.ymlpins only already-recorded refs. It then generates the record with the repair chain, with no hand edits toactions.lock.Relates to #992. It doesn't close it: the gate-text inversion that #992 describes is a separate defect.
Type of change
mirror.ymlcreates no jobs today.📌 New pins
Head SHA: cb6face
mirror.yml→hyperpolymath/standards/.github/workflows/mirror-reusable.yml@b935e63937b1f1b5cbaeea7e375947d7b924038f(main at 2026-10-06, after fix(ledger): drop stale deed-conformance inline-python entry #1167). It was@571cc734.actions.lockrecordhyperpolymath/standards@b935e63937b1f1b5cbaeea7e375947d7b924038f, with nested usesactions/checkout@3d3c42e5…(v7.0.1),dtolnay/rust-toolchain@7e38f4b4…andwebfactory/ssh-agent@e8387483…(v0.10.0). All three were already recorded.actions.lockrecordactions/setup-python@v2(commite9aba2c8…). close-lock closed this pre-existing dangling transitive edge: theasana/push-signed-commits@d615ca88record (used by.github/actions/signed-push) names it, but it had no record.hyperpolymath/standards@571cc734is kept, becauseci-pipeline.ymlstill names it. prune-stale confirmed this.How has this been verified?
Commands run in the worktree at the head SHA:
scripts/complete-job-refs.shadded 1 ref.build-dep-records.sh, the 09-22 census generator that matched burble's record exactly, reported "RECORD …@b935e63 (nested uses: 3)".scripts/close-lock.sh: pass 1 found 1 dangling edge, pass 2 found 0.scripts/prune-stale.sh: done, 0 oracle vetoes..githooks/validate-actions-lock.sh(uses ⊆ actions.lock): rc=0.scripts/check-lock-sync.sh: rc=0, "in sync … Job-level reusable-workflow refs included".scripts/check-actions-lock-gate.shandGH_BIN=gh scripts/update-actions-lock.sh --verify-local: rc=0.gh actions-lock --no-fix --verify: rc=1, becausesigned-push-smoke.ymluses local path actions. This is identical onorigin/main, measured in a throwaway detached worktree, so this PR doesn't cause it.The platform error confirms the cause. It comes from the run page of main run 37485803576 (
curlof the public page; the API gives only the generic "workflow file issue"):lockfile missing pin for actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1. That pin has a top-level record, so GitHub is resolving the callee's steps through the job-level record's nesteduses:. The571cc734record has none, and the newb935e63record lists exactly this pin.The proof is the first
mirror.ymlrun on main after merge. It must create jobs, notstartup_failure. This workflow triggers only on a push tomainor a dispatch. I did not dispatch it on this branch: the reusable runsgit push --force <forge> main, and doing that from an unmerged branch could push the wrong tree to the mirrors. It is not proven until that post-merge run reads green or skipped.Checklist
git commit -S):%G?= G.gh actions-lock --verifyfails the same way as on main.Notes for reviewers
governance / Actions lockfile verifyanduses ⊆ actions.lockgreen.actions.lockchange came from the repair-chain tools. No sed and no hand edits.🤖 Generated with Claude Code
https://claude.ai/code/session_012kgrMQRhSmZMBbF9Ui1zBw