Repository navigation
fix(ledger): drop stale deed-conformance inline-python entry - #1167
Merged
Merged
Conversation
#1164 replaced the python3 steps in deed-conformance.yml with bun, so the shrink-only inline-python ledger now names a file with no inline Python and check-inline-python-test.sh fails "repository ledger drifted" on main (Repo self-tests). Delete the stale line, as the gate itself instructs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P48P9ErT8UFFeDUfEQiYV7
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 55 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 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/37481515469 K9 normative contract typecheckK9 contract self-testK9 conformance fixtures |
|
Contributor
|
Add Carrot credits or activate Agent usage billing to use Autopilot |
7 of 13 tasks
hyperpolymath
added a commit
that referenced
this pull request
Oct 6, 2026
#1169) <!-- SPDX-License-Identifier: CC-BY-SA-4.0 Copyright (c) Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk> --> ## Summary `mirror.yml` has been `startup_failure` on every head since 2026-10-05 (8 of 8 latest runs, last at 44a0de4). Two defects in its lock entry: 1. The job-level record `hyperpolymath/standards@571cc73` carries **no nested `uses:` list**. The working peers key the same kind of record **with** one: `hyperpolymath/cicd-squabbler` (mirror `success` at a4cd088) and `metadatastician/burble`. 2. The callee `mirror-reusable.yml@571cc73` pins `dtolnay/rust-toolchain@6c977a6`, which has **no** record in this lock. This PR re-pins `mirror.yml` to `b935e63` (current main). There, `mirror-reusable.yml` pins only already-recorded refs. It then generates the record with the repair chain, with no hand edits to `actions.lock`. Relates to #992. It doesn't close it: the gate-text inversion that #992 describes is a separate defect. ## Type of change - [x] 🐛 Bug fix (non-breaking change that fixes an issue): `mirror.yml` creates no jobs today. - [ ] ✨ New feature: no. - [ ] 💥 Breaking change: no. - [ ] 🕳️ Soundness fix: no checker logic changes. - [ ] 📖 Documentation: no. - [ ] 🧹 Refactor / tech debt: no. - [ ] ⚡ Performance: no. - [x] 🔧 Build / CI / tooling ## 📌 New pins Head SHA: **cb6face02ef10f6e52be566a864f2ddc22ab55dc** - `mirror.yml` → **`hyperpolymath/standards/.github/workflows/mirror-reusable.yml@b935e63`** (main at 2026-10-06, after #1167). It was `@571cc73`. - `actions.lock` record **`hyperpolymath/standards@b935e63`**, with nested uses **`actions/checkout@3d3c42e5…`** (v7.0.1), **`dtolnay/rust-toolchain@7e38f4b4…`** and **`webfactory/ssh-agent@e8387483…`** (v0.10.0). All three were already recorded. - `actions.lock` record **`actions/setup-python@v2`** (commit `e9aba2c8…`). close-lock closed this pre-existing dangling transitive edge: the `asana/push-signed-commits@d615ca88` record (used by `.github/actions/signed-push`) names it, but it had no record. - `hyperpolymath/standards@571cc73` is kept, because `ci-pipeline.yml` still names it. prune-stale confirmed this. ## How has this been verified? Commands run in the worktree at the head SHA: - `scripts/complete-job-refs.sh` added 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.sh` and `GH_BIN=gh scripts/update-actions-lock.sh --verify-local`: rc=0. - `gh actions-lock --no-fix --verify`: rc=1, because `signed-push-smoke.yml` uses local path actions. This is **identical on `origin/main`**, measured in a throwaway detached worktree, so this PR doesn't cause it. The proof is the `mirror.yml` run on this branch's push. It must create jobs (not `startup_failure`). It isn't proven until that run reads green or skipped. ## Checklist - [x] My commits are **signed** (`git commit -S`): `%G?` = G. - [x] I ran the project's own checks locally: the four lock gates above pass, and `gh actions-lock --verify` fails the same way as on main. - [x] New files carry the correct SPDX identifier: there are no new files. - [x] Docs and claims: no docs change. This body says the fix is unproven until the run. - [x] No soundness hole: lock data only, and no gate logic touched. ## Notes for reviewers - Standards main is under Lock-Floor (no bypass), so this has to merge with `governance / Actions lockfile verify` and `uses ⊆ actions.lock` green. - Every `actions.lock` change came from the repair-chain tools. No sed and no hand edits. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_012kgrMQRhSmZMBbF9Ui1zBw Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
#1164 moved
deed-conformance.ymlfrom python to bun, which removed its inline-python steps. The workflow stayed listed in the shrink-only ledger.machine_readable/inline-python-allow.txt.scripts/tests/check-inline-python-test.shfails on a stale entry, soRepo self-testswent red on main after #1164. This PR deletes that one ledger line.No issue. This is a follow-up to #1164.
Type of change
📌 New pins
Head SHA: 14e7382
This PR adds or changes no pins: no
uses:SHAs, noactions.lockentries, no lockfiles, no container digests.How has this been verified?
bash scripts/tests/check-inline-python-test.shon this branch → 24 passed, 0 failed. On main, the stale entry made this test fail.Repo self-testswill still be red after this PR. Three tests were already failing on main before feat(deed): bun port of deed_lint + reusable deed-conformance gate #1164: build-registry, build-scorecards and kyaml-format. Their failure counts are identical on a clean main worktree. This PR does not touch them, and they are tracked separately.Checklist
git log --format=%G?showsGon 14e7382.Notes for reviewers
This is a one-line deletion. The ledger format is
path:count.🤖 Generated with Claude Code
https://claude.ai/code/session_01P48P9ErT8UFFeDUfEQiYV7