Skip to content

Trigger Docker publish on unprefixed release tags - #97

Merged
kk7ds merged 1 commit into
kk7ds:masterfrom
chrodriguez:fix/docker-publish-release-tags
Nov 1, 2026
Merged

kk7ds merged 1 commit into
kk7ds:masterfrom
chrodriguez:fix/docker-publish-release-tags

Conversation

@chrodriguez

Copy link
Copy Markdown
Contributor

Fixes #96.

Release tags in this repository have no v prefix (0.8.1, 0.9.0), but docker-publish.yaml only triggers on v*. Because of this, no versioned image is published to ghcr.io.

This adds '[0-9]+.[0-9]+.[0-9]+' to the tag trigger. v* and the master trigger stay as they are. The existing type=semver rules then publish X.Y.Zand X.Y images, and latest continues to follow master.

If you move the 0.9.0 tag to this commit, the 0.9.0 and 0.9 images are published. Two-component tags such as 0.8 stay out of scope.

Releases are tagged without a "v" prefix (for example 0.9.0), so the
'v*' filter never matched them and no versioned image was published.
Also trigger on X.Y.Z tags.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: multica-agent <github@multica.ai>
@chrodriguez

Copy link
Copy Markdown
Contributor Author

Hi @kk7ds, friendly ping: this is the one-line fix from #96 and CI is green. Could you take a look when you have a moment? Thanks!

@kk7ds

kk7ds commented Nov 1, 2026

Copy link
Copy Markdown
Owner

I've been off-grid for the last few days...

@kk7ds
kk7ds merged commit cf7e858 into kk7ds:master Nov 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish versioned container image tags for releases

2 participants