Repository navigation
Conversation
Keep the released-version guard intact while validating CI maintenance. Use the existing next-patch dev0 convention without declaring a stable release.
CyMule
changed the title
Contributor
Author
|
@cubic-dev-ai review |
Contributor
@CyMule I have started the AI code review. It will take a few minutes to complete. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
No issues found across 3 files
Shadow auto-approve: would not auto-approve. This PR does not meet the repository auto-approval settings.
Re-trigger cubic
This branch has not been deployed
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
Docker publishing no longer pulls both architecture images onto the runner just to retag them. The tags are now created inside Quay.
The multiarch tags are built from the tested
amd64-<sha>andarm64-<sha>images, not the movingamd64/arm64tags. A concurrent run therefore cannot swap in a different image between tagging and publishing.Why
The baseline publish run spent 14m16s downloading layers that were already in Quay. Build/test jobs, tag names, and the source and destination repositories stay the same.
Notes
This PR also bumps the version to
0.27.13-dev0with a changelog entry, like #4521. Whichever PR merges second needs the usual rebase.Validation
actionlint passes. The exact publish commands ran against a local two-architecture registry: the cache tags kept their source digests, and all three public tags listed both architectures with their layers present. Production timing will be measured after merge.