Don't use "latest" for arch dependent builds for simplicity#319
Merged
rickyrombo merged 1 commit intomainfrom Aug 13, 2025
Merged
Don't use "latest" for arch dependent builds for simplicity#319rickyrombo merged 1 commit intomainfrom
rickyrombo merged 1 commit intomainfrom
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.
In main, the builds were doing both "latest" and sha-based tags on each arch image, then trying to combine all four together into the "latest" and sha-based tag for the combined manifest.
This PR splits it out so that the arch dependent builds are just sha based, and an extra metadata extraction step gets their tags instead of sharing the one for the outputs in the merge phase.