Repository navigation
fix(ci): re-attest hypatia credential-read-check at its current pin (fixes red Pinned source closure) - #698
Merged
Conversation
The "Pinned source closure" job is red on main: the manifest binds the scanner-credential job to hyperpolymath/hypatia@b93f0615, but hypatia-scan.yml has called @29a9e4a8 since #686. Both commits carry the same blob (15c597e), so only the commit binding and its receipt row move; blob and content SHA-256 are unchanged and were re-verified from fetched objects. This is attestation for the CURRENT pins only. The four standards pins are not bumped (see PR description). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDjMjpyixLqzirvwV1s
|
Contributor
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
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
main(dec1e7c) is red on "Pinned source closure":audit-pinned-reusable-sources.sh --fetch-sourcesreportsFATAL 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 ishypatia-scan.ymljobscanner-credential, bumped by #686 tohyperpolymath/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.actions.lock, SPDX or.a2mlchange.Evidence (baseline origin/main → after; gawk installed locally, fresh cache each)
audit-pinned-reusable-sources.sh --fetch-sourcesaudit-lock-closure.shcheck-lock-sync.shpreflight.sh --quietSTANDARDS_DIR=<standards @3b57589d> tests/fleet-report-back-test.shNot done
governance-reusable.ymlat 3b57589 contains job-level nested reusable calls (deed-conformance.yml@bfa851f…line 436,k9-conformance.yml@bfa851f…line 445). The verifier deliberately returns NOT-RUNSOURCE-LOCALfor nested reusables, so the governance pin cannot be attested without extending the verifier's reviewed profile — out of scope.hypatia-scan-reusableat 3b57589 also addsactions/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.gh actions-lock) was not run locally either.Generated by Claude Code
Summary by CodeRabbit