Commit the manifest that closed the v0.2.2 gate - #73
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.
Commits the machine-readable attestation produced by the successful evidence-commit run verbatim, closing the v0.2.2 gate.
Source:
release-evidencerun 33867218587 at evidence commit85ec2a6de4e971c6e77eab83e508c090c8f0b1f6. All five jobs passed, includingrelease-integrity— the manifest records"strict_gate": "success", which is what the previous run could not report becauseexact-commit-evidencewas still pointing at the old runtime commit.The file is the run's
release/evidence/release-evidence.jsonbyte for byte; no field was edited by hand.git diff --name-only 648269b..HEADreturnsdocs/RELEASE_EVIDENCE.mdandrelease/evidence/manifest.json— both on the evidence allowlist, so the gate stays green. This is the commit that gets taggedv0.2.2.