Fix published remote Action SHA propagation - #9
Merged
Conversation
avoroncov971-maker
marked this pull request as ready for review
September 8, 2026 03:02
Contributor
Author
|
@claude Please perform a READ_ONLY_ANALYSIS review of this exact PR head: repository: deedseal/proof-check Review only the three allowlisted files. Independently verify the failure mechanism from the original remote-consumer run, the environment-variable repair, full-SHA refusal behavior, receipt/head binding, and the successful remote-consumer evidence on PR #8. Do not edit files, push, approve, mark Ready, merge, release, or change repository settings. Return one exact-head disposition in the PR conversation: PASS, BLOCKED, or INDETERMINATE, with any blocking finding tied to a reproducible counterexample. |
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.
Allowlist
The remote Action failed before invoking the CLI. Pass action context using PROOF_CHECK_ACTION_REF and PROOF_CHECK_ACTION_REPOSITORY; retain full-SHA validation and local-workspace refusal. Default GITHUB_* variables are runner-owned: https://docs.github.com/en/actions/reference/workflows-and-actions/variables
Owner authorized this separate repair in chat. Regression covers remote action outside workspace with empty runner-owned variables, plus refusal when explicit remote pin is absent. No contract changes.
Repair SHA:
201bac98ac95bd173e6132510a3de3f7af064610.Local:
python3 -m pytest -q-> 358 passed, exit 0 (67.82s); focused Action tests 16 passed;git diff --checkexit 0.Remote consumer: PR #8 head
a18dc779b3da64b6aab84f528fea0fbb2bc42639uses the repair by full SHA. All three hosted checks success.Check: https://github.com/deedseal/proof-check/actions/runs/34180465267/job/101918337921
CLI: PASS, one changed path, exact consumer head; offline
proof-check verify-> VERIFIED, exit 0.Receipt artifact: 10038713415. Offline bundle: 10038715749.
This verifies remote consumption, not merge enforcement; protection remains a separate Owner act.
Original failing run: https://github.com/deedseal/proof-check/actions/runs/34180270668/job/101917770789
Draft for independent review and Owner merge; no release tag moved.