Fix hidden consumer verification artifact upload - #28
Merged
Merged
Conversation
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.
Final closure fix for Consumer Pin Verification evidence capture.
The fresh merged-consumer verification proved both consumer repositories pin the exact release candidate SHA and successfully generated ledger-ready evidence, but the workflow failed at artifact upload because the evidence is written under the hidden
.verification/directory andactions/upload-artifactexcludes hidden files by default.This PR makes the minimal correction:
include-hidden-files: trueon the consumer evidence upload step;tests/test_workflow_dispatch_contracts.pyrequiring hidden evidence inclusion,if-no-files-found: error, and the.verification/evidence path.No candidate identity, consumer pin, verifier semantics, benchmark logic, package logic, or release claim is changed. The release evidence candidate remains
b8d734f4a6a92a534aed87db91e12df16b718a9e.Exact-head validation on
fca749bc53fb96255787388cc49da0d169fb4cd4is complete: CI run 33013596104 succeeded and Repro baseline run 33013596347 succeeded across its full matrix.