Add concurrency control to publish workflow#34
Merged
Conversation
Serialize publishes per image so concurrent tag pushes cannot race. Uses cancel-in-progress: false to let in-flight builds finish rather than aborting them. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
If two version tags are pushed in quick succession, concurrent publishes of the same image could race — the verify build could read stale registry cache from a concurrent push, or two pushes could overwrite each other's
latesttag non-deterministically. A concurrency group serializes publishes per image to prevent this.Related Issues
Fixes #20
Changes
concurrencygroup scoped topublish-${{ matrix.image }}on the publish jobcancel-in-progress: falseso in-flight builds complete rather than being aborted