Repository navigation
fix(ci): move mirror and scorecard off standards 75bd5994 (Mirror startup_failure since 2026-11-09) - #688
Merged
Conversation
Mirror to Git Forges has ended in startup_failure on every push to main since 2026-11-09 (1c22722), with mirror.yml unchanged since 2026-11-01. At 75bd5994, standards' own actions.lock records the callee's dtolnay/rust-toolchain edge as `ref: 'v1'` -> e2a55d2f. Upstream's v1 tag now resolves to 683b588c (git ls-remote), and GitHub validates the callee lock at the called SHA (scripts/lib/stale-reusable-pins.tsv, Window B). mirror-reusable is the only one of this repo's three 75bd5994 callers that pulls in dtolnay, which is why hypatia-scan and scorecard still start at the same pin. Standards HEAD re-locked to 683b588c. Move mirror and scorecard to standards b49a33e9 and re-attest the pinned-source closure with the repo's tools: - pinned-reusable-sources.json: new commit, blob, content SHA-256 and direct uses for both sources; a parent record for b49a33e9; records for dtolnay/rust-toolchain@683b588c (v1) and ossf/scorecard-action@fa7117db (v2.5.0), from standards' lock and checked against upstream; the 75bd5994 parent record shrinks to its remaining sources; the two records this change orphans are removed. - lock-closure-receipts.tsv: both groups re-emitted with audit-lock-closure.sh --emit-receipt. Interface checks: mirror-reusable only adds three optional R2 secrets and a permissions:{} visibility-guard job; scorecard-reusable's inputs, secrets and per-job permissions are unchanged. hypatia-scan stays at 75bd5994 on purpose: its newer reusable changes the scanner pins and what gets reported, so it gets its own change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDhFeexmokLqLRfZNce
|
hyperpolymath
marked this pull request as ready for review
November 17, 2026 04:35
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This was referenced Nov 17, 2026
hyperpolymath
added a commit
that referenced
this pull request
Nov 17, 2026
…fixes red Pinned source closure) (#698) ## Why `main` (dec1e7c) is red on "Pinned source closure": `audit-pinned-reusable-sources.sh --fetch-sources` reports `FATAL SOURCE-ACTIVE-MISSING`. The probable cause in the task (#688 moving mirror/scorecard) was **not** the cause — mirror and scorecard were already attested at b49a33e. The actual drift is `hypatia-scan.yml` job `scanner-credential`, bumped by #686 to `hyperpolymath/hypatia/.github/workflows/credential-read-check.yml@29a9e4a8…` while the manifest still binds `@b93f0615…`. Both commits carry the same blob (`15c597e…`). ## What Fallback only: attestation for the **current** pins, **no standards bump**. - `scripts/lib/pinned-reusable-sources.json`: commit binding b93f0615 → 29a9e4a8 (blob and content SHA-256 unchanged, re-verified from fetched objects). - `scripts/lib/lock-closure-receipts.tsv`: receipt row and comment moved to 29a9e4a8. - No workflow, `actions.lock`, SPDX or `.a2ml` change. ## Evidence (baseline origin/main → after; gawk installed locally, fresh cache each) | Check | Baseline | After | |---|---|---| | `audit-pinned-reusable-sources.sh --fetch-sources` | findings=1 (SOURCE-ACTIVE-MISSING) | findings=0 not-run=0 verified-roots=6 | | `audit-lock-closure.sh` | fatal=1 review=5 accepted=2 not-run=7 | fatal=0 review=0 accepted=3 not-run=0 source-attested-records=13 | | `check-lock-sync.sh` | rc=0 | rc=0 | | pinned-reusable-sources-test | 55/0 | 55/0 | | lock-closure-test | 45 pass / 2 fail | 47/0 | | pinned-source-entrypoints-test | 7 pass / 2 fail | 9/0 (after the CI historical-source fetch step) | | prepared-migration `preflight.sh --quiet` | — | rc=0 | | `STANDARDS_DIR=<standards @3b57589d> tests/fleet-report-back-test.sh` | — | 69 passed, 0 failed | ## Not done - **The four-pin bump to standards 3b57589 is blocked.** `governance-reusable.yml` at 3b57589 contains job-level nested reusable calls (`deed-conformance.yml@bfa851f…` line 436, `k9-conformance.yml@bfa851f…` line 445). The verifier deliberately returns NOT-RUN `SOURCE-LOCAL` for nested reusables, so the governance pin cannot be attested without extending the verifier's reviewed profile — out of scope. `hypatia-scan-reusable` at 3b57589 also adds `actions/download-artifact@9000827…`, absent from the current receipts/lock closure, so it needs a lock regeneration (tool-owned, never hand-edited) plus review. Needs an owner decision on the verifier profile first. - **actionlint and mikefarah yq v4 were not run**: installation (go install, release binaries) was denied by this session's permission classifier. No workflow file is touched here, but actionlint is unverified. The "Regenerate vendor lock" CI step (`gh actions-lock`) was not run locally either. - Compat-branch hypatia pin (75bd599) left as is. --- _Generated by [Claude Code](https://claude.ai/code/session_01J4QvDjMjpyixLqzirvwV1s)_ <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Chores** * Updated the pinned workflow source to a newer revision. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude <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
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.



Why
Mirror to Git Forgeshas ended instartup_failureon every push tomainsince 2026-11-09 (first at1c22722, 34 runs), whilemirror.ymlhas been unchanged since 2026-11-01. It is the only red workflow onmain.Diagnosis. The cause is supported by evidence below, but the failure message itself could not be read from this session.
75bd5994, standards' ownactions.lockrecords the callee's edge asdtolnay/rust-toolchain@e2a55d2fwithref: 'v1'.v1tag now resolves to683b588c(git ls-remote https://github.com/dtolnay/rust-toolchain).scripts/lib/stale-reusable-pins.tsv, Window B).75bd5994callers,mirror-reusableis the only one whose closure includes dtolnay. That explains whyhypatia-scanandscorecardstill start at the same pin.683b588c.The
startup_failureannotation text is not exposed by the APIs available to this session. Confirmation is the firstMirrorrun onmainafter merge, because Mirror runs only on push and dispatch, not onpull_request.What
.github/workflows/mirror.yml,scorecard.yml75bd5994→b49a33e9(standardsmain, 2026-11-17)scripts/lib/pinned-reusable-sources.jsonuses. Added astandards@b49a33e9parent record. Addeddtolnay/rust-toolchain@683b588c(v1) andossf/scorecard-action@fa7117db(v2.5.0) records, taken from standards' lock and checked against upstream tags. Shrank the75bd5994parent to its remaining three sources. Removed the two records this change orphans.scripts/lib/lock-closure-receipts.tsvaudit-lock-closure.sh --emit-receipt, not hand-edited. Provenance comment updated.Interface checks against
75bd5994:mirror-reusableadds only three optional R2 secrets, an R2 job gated onvars.R2_BUNDLE_MIRROR_ENABLED, and avisibility-guardjob withpermissions: {}. That guard is a privacy improvement: forge pushes now also require a public repo or an explicit*_PRIVATE_CONFIRMED.scorecard-reusablekeeps the same inputs, secrets and per-job permissions.Deliberately not in this PR:
hypatia-scanstays at75bd5994. Its newer reusable changes the scanner pins (Hypatia, panic-attack, pons) and the reporting, so it changes what is found and needs its own review.Validation (local replay of the
Pinned source closureCI job, withPINNED_SOURCE_CACHEset)pinned-reusable-sources-test.sh: 55 passed, 0 failedaudit-pinned-reusable-sources.sh --fetch-sources: findings=0, not-run=0, verified-roots=6 (also on the historical-scanner tree)scanner-caller-contract-test.sh: passedlock-closure-test.sh: 47 passed, 0 failedaudit-lock-closure.sh:fatal=0 review=0 accepted=3 not-run=0 source-attested-records=14pinned-source-entrypoints-test.sh: 9 passed, 0 failedcheck-lock-sync.sh: rc 0Follow-up, estate-wide (not done here)
About 20 or more hyperpolymath repos call
mirror-reusable; code search finds e.g. modshells, echidna, verisimdb and panic-attack. Any still pinned at75bd5994would hit the same failure. Once this PR's firstmainrun confirms the diagnosis, astale-reusable-pins.tsvrow (mirror-reusable@75bd5994→b49a33e9) letsfix-stale-reusable-pin.shand Hypatia PIN-003 repair them. I have not added that row yet, because it would act on a diagnosis that is still unconfirmed.Generated by Claude Code