chore: upgrade publish-docker workflow to v1.14.0#67
Open
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.
Summary
publish-docker.yamlfrom@v1.13.1to@v1.14.0Context
The
v1.13.1workflow tags container images with av0.0.0-prefix (e.g.v0.0.0-main-20260505-220850) while the kustomize bundle still uses the unprefixed format (main-20260505-220850). The infra repo's ImageUpdateAutomation was using the kustomize bundle tag to update the container imagenewTag, causingImagePullBackOfffailures because the unprefixed container image tag didn't exist.This PR is paired with infra repo changes that split the ImagePolicy into two — one for the kustomize bundle OCIRepository tag (
main-.*) and one for the container image (v0.0.0-main-.*) — so the correct tag format is used for each.Test plan
v0.0.0-main-*tagmain-*tag