Repository navigation
Publish qualified runtime backports through retained Catalog revisions - #22
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
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.
Update thirteen numeric infrastructure template revisions to consume eleven published component images with qualified Ubuntu security backports. Preserve every existing revision, service definition, question, firewall option and plugin boundary; installation continues to use numeric image tags.
Record each producer, immutable image digest, runtime SBOM, raw/effective scan and publication receipt. Preserve Scheduler v0.8.20 provenance while adding v0.8.21 with verified native SBOM provenance. Keep unfixed findings and historical environment acceptance separate from component publication.
Validation: deployable-image audit passes for 22 templates, 192 image references, 80 locked images and 142 localized questions; all new component identities are published and independently read back. Existing native package and component functional evidence is reused. Catalog CI validates retained/new version lookups and integration contracts; no production deployment is part of this PR.