Allow optional Cargo image provenance - #1
Merged
Conversation
Keeps deterministic byte verification, base-image attestation, and Liskov OIDC manifest/image binding mandatory while allowing derived-image provenance publication to be disabled.\n\nRefs BKLG-20260803-0d11.
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.
What changed
attest-runtime-imageboolean input to the reusable Cargo image workflowWhy
GitHub does not store artifact attestations for every private-repository organization plan. That optional evidence must not block customer-managed runtime images from using Liskov's independently verified OIDC and exact-digest upload path.
Validation
pnpm typecheckpnpm testpnpm check:distRefs BKLG-20260803-0d11.