ci: keep :latest and the GitHub "Latest" release on the master line only - #126
Merged
Conversation
A maintenance release cut after a mainline one used to steal both the Docker Hub `latest` tag and GitHub's "Latest" release badge/redirect, so `docker run tmkawanabe/wheel` booted a maintenance build and the releases page top-listed it. - export RELEASE_TYPE from the version-stamp step (release|maintenance|beta). - push `tmkawanabe/wheel:latest` only when RELEASE_TYPE=release (master); a maintenance dispatch now only moves its own :maintenanceYYYY tag. - bump softprops/action-gh-release v1 -> v2 (v1 silently ignores the inputs below) and set make_latest / prerelease from RELEASE_TYPE, so maintenance releases publish as pre-releases and master keeps the Latest badge and the /releases/latest redirect. Same edit must be applied to the maintenance2026 and maintenance2023 copies of this workflow (each branch carries its own). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017xw6DdyQhrdTZMjYbKvFZi
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
2 participants
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.
Problem
When a maintenance release is cut (manual
workflow_dispatchof build and deploycontainer on a
maintenance*branch), it currently steals two things that shouldalways track the mainline (
master)::latest—docker run tmkawanabe/wheelends up booting amaintenance build.
action-gh-release@v1cannot sendmake_latest,so the API defaults every published release to "Latest". The maintenance
timestamp tag is also newer than the last
…-releasetag, so it takes thebadge, the front-page Releases panel, and the
…/releases/latestredirect, andtop-lists on
/releases.Change (this branch's own copy of
build_and_deploy.yml)RELEASE_TYPE(release/maintenance/beta) from theversion-stamp step.
tmkawanabe/wheel:latestonly whenRELEASE_TYPE == release(themasterbuild). A maintenance dispatch now only moves its own:maintenanceYYYYtag.softprops/action-gh-releasev1 → v2and setmake_latest: <is release>/prerelease: <not release>, so maintenancereleases publish as pre-releases and
masterkeeps the "Latest" badge and the/releases/latestredirect.Each branch (
master,maintenance2026,maintenance2023) carries its own copyof this workflow, so this is one of three sibling PRs with the identical edit.
Out-of-repo follow-up
tmkawanabe/wheelon Docker Hub for an Automated Build / tag rule thatwrites
latestfrom a non-mastersource and remove it.:latestat the current mainline image (retag+push, or runbuild and deploy container on
masteronce after the master PR merges).🤖 Generated with Claude Code