Repository navigation
fix(ci): fetch the verdict-grid renderer at the commit its hashes name - #36
Conversation
Every pull request's verdict-grid comment is orange: "The renderer pinned in metadatastician/standards@8e48b1caade0 was missing or did not match its recorded sha256." scripts/verdict-grid-lane.sh pins the renderer at standards 8e48b1c and records the sha256 of verdict-grid.sh (3ee93552…) and verdict-grid.jq (5681fcef…) at that commit. The 2 steps that fetch the renderer (fork-governance.yml and verdict-grid-publish.yml) fetched e064539 instead, a ref the template sync (#28) brought in. At e064539 neither file matches, so the lane refuses to run it. CHANGELOG records that this repository keeps 8e48b1c because e064539's renderer does not render. Both steps now fetch 8e48b1c. This is an input of actions/checkout, not a uses: ref, so actions.lock does not change. Checked: both files at 8e48b1c match the recorded sha256 (sha256sum -c); tests/workflows/verdict_grid_test.sh (188 checks), workflow_evidence_test.sh and workflow_edges_test.sh pass; check-workflow-edges.sh and check-lock-sync.sh pass. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7ZmAsYpFA9gxfQLF3F6 Signed-off-by: Claude <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. 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. |
|
|
🟠 indeterminate · the verdict grid could not be rendered · The renderer pinned in metadatastician/standards@8e48b1caade0 was missing or did not match its recorded sha256. Orange means the evidence for this lane was unavailable, not that the repository passed. |
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. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
Every pull request's verdict-grid comment is orange: "The renderer pinned in metadatastician/standards@8e48b1caade0 was missing or did not match its recorded sha256."
scripts/verdict-grid-lane.shpins the renderer at standards8e48b1cand records the sha256 of both renderer files at that commit. The 2 steps that fetch the renderer fetchede064539instead, a ref the template sync (#28) brought in. Ate064539neither file matches, so the lane refuses to run the renderer. The CHANGELOG records that this repository keeps8e48b1cbecause the renderer ate064539does not render.Changes
.github/workflows/fork-governance.yml(step "Checkout the verdict grid renderer at the pinned standards commit") and.github/workflows/verdict-grid-publish.yml(step "Checkout pinned renderer"):refmoves frome064539…to8e48b1caade08a552646adeab66558ac43b4360d.actions.lockdoes not change:refis an input ofactions/checkout, not auses:ref.8e48b1ce064539scripts/verdict-grid.sh3ee93552…1053d170…3ee93552…scripts/lib/verdict-grid.jq5681fcef…b02da89e…5681fcef…RSR Quality Checklist
Required
unsafeblocks without// SAFETY:comments.envfiles includedAs Applicable
Testing
Run locally:
8e48b1cmatch the recorded hashes (sha256sum -c --strict).tests/workflows/verdict_grid_test.sh: 188 checks pass.tests/workflows/workflow_evidence_test.shandtests/workflows/workflow_edges_test.sh: pass.scripts/check-workflow-edges.shandscripts/check-lock-sync.sh: pass.The hosted proof is this PR's own verdict-grid comment, which should render instead of showing orange.
Screenshots
Not applicable.
Generated by Claude Code