Repository navigation
Pin the Buildah RPM in the runtime cache key - #94
Merged
ty-everett merged 2 commits intoOct 18, 2026
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.
A production rebuild reused an OS package layer cached before the Buildah security update and failed the final 1.43.5 assertion. Make the exact 1.43.5-1.fc44 RPM an input to the runtime installation layer and verify it there, so the package change invalidates the cache and any failure occurs before copying application code.
Validation: the amd64 release-security workflow builds and scans the runtime; production promotion remains gated on the separate immutable image workflow and live capability canary. Failed production run 39098173015 deployed nothing.