ci(docker): push :latest when a prerelease is promoted to Latest - #259
Merged
Conversation
Listen to release `prereleased` and `released` actions instead of `published`: - prereleased (prerelease published) -> version tag only (e.g. 0.8.0-alpha.6) - released (stable publish, or a prerelease promoted to a full/Latest release) -> version tag + :latest - push to main / manual dispatch -> :edge (unchanged) Using these two actions instead of `published` also avoids a double run on a stable publish (which fires both published and released).
thcp
added a commit
that referenced
this pull request
Jul 13, 2026
…ished` (#266) Publishing v0.8.0-alpha.7 (a draft prerelease -> published) never triggered Docker Publish: CI/Linux/Windows/macOS releases all still listen for `published` and fired correctly, but docker-publish.yml (changed in #259) only listened for [prereleased, released] -- and `prereleased` did not fire for this publish. Result: ghcr.io/stemdeckapp/stemdeck:0.8.0-alpha.7 was never pushed, while the Unraid CA template already points at that (nonexistent) tag. Fix: trigger on [published, released] -- published is the reliable trigger every other release workflow already relies on; released is kept for promoting an already-published prerelease to Latest via the release-label edit. The :latest condition now also covers a plain non-prerelease `published` (not just `released`), so a first-time stable release still gets :latest. Also add a workflow_dispatch `version` input, so a specific tag can be (re)pushed by hand to recover from a missed trigger without re-touching the release (which would needlessly re-run the OS build workflows).
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.
Implements the requested tag behavior:
:edge:<version>only:latest+:<version>Switches the release trigger from
publishedto[prereleased, released]. GitHub firesreleasedwhen a prerelease is changed to a full/Latest release, so promoting a prerelease now pushes:latest. Using these two actions also avoids the double run a stable publish would cause (it fires bothpublishedandreleased).