Repository navigation
M11.3: qualify release runtime by exact OCI digest - #3
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.
Adds an exact-digest release runtime gate. The release workflow now takes the immutable digest emitted by build-push-action, pulls
ghcr.io/ploos-as/soju-web@sha256:..., verifies the resolved RepoDigest and OCI revision/version labels, checks UID/GID 1000, and requires/healthzfrom that exact image before attestation and GitHub Release creation. CI adds fail-closed validation for digest reference syntax and documentation records the M11.3 gate.