Add separate workflow for managing latest Docker tag#6
Merged
chaptersix merged 3 commits intomainfrom Nov 21, 2025
Merged
Conversation
Creates a new workflow (update-latest-tag.yml) that runs when a release is edited or published and automatically updates the 'latest' Docker tag to point to the release version if the release is marked as latest. Changes: - Add .github/workflows/update-latest-tag.yml - Triggers on release edited/released events - Checks if release is latest (not prerelease, not draft) - Pulls the versioned image and retags it as 'latest' - Supports both Docker Hub and GHCR - Uses environment variables to prevent command injection - Update .github/workflows/build-and-publish.yml - Remove 'Check if release is latest' step - Set TAG_LATEST to false (always) - Latest tag is now managed by the separate workflow Benefits: - Decouples latest tag management from release creation - Allows updating latest tag when release status changes - Cleaner separation of concerns Tagging strategy matches temporalio/temporal on Docker Hub: - Full version tags (e.g., 1.5.1) - Latest tag - SHA tags (additional, useful for debugging)
- Remove 'Upload build artifacts' step from build-and-publish.yml (no longer needed) - Add 'packages: write' permission to goreleaser.yml (required for pushing Docker images to GHCR)
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
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
Adds a new workflow that automatically manages the
latestDocker tag when releases are edited or marked as latest, decoupling this from the initial release process.Changes
New Workflow:
update-latest-tag.ymleditedorreleasedevents1.5.2)latestlatesttagUpdated Workflow:
build-and-publish.ymlTAG_LATESTtofalse(always)Benefits
Tagging Strategy
Matches
temporalio/temporalon Docker Hub:1.5.1)abc123f) - extra, useful for debuggingTesting
After merging:
latestlatesttaglatestpoints to the correct version