Skip to content

fix: promote images from :latest so unchanged images get the release version #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chutch3 merged 1 commit into from
Jun 23, 2026
Merged

fix: promote images from :latest so unchanged images get the release version #90

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 11 additions & 7 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,9 @@ jobs:
id-token: write

promote-images:
# Tag every built image with the release's semantic version, by promoting the
# already-tested :<sha> image (no rebuild). One version for the whole platform.
# Tag every custom image with the release's semantic version, by retagging its
# current :latest (no rebuild). One version for the whole platform — unchanged
# images get their existing digest aliased under the new version too.
name: Promote images to ${{ needs.release.outputs.version }}
needs: release
if: needs.release.outputs.released == 'true'
Expand Down Expand Up @@ -74,13 +75,16 @@ jobs:
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}

- name: Promote each image :sha -> :version
# GITHUB_SHA is the released code (the release commit only bumps version/
# changelog), and build.yml already pushed its :<sha> image.
- name: Promote each image :latest -> :version
# Retag every image's current :latest (its most-recent main build, whether
# or not it changed this cycle) with the release version. Server-side
# manifest retag — no rebuild, no layer push. Using :latest (not :<sha>)
# means unchanged images, which were never built at the release commit,
# still get tagged — so the whole platform ends up on one version.
run: |
set -euo pipefail
for image in $(uv run ci images .); do
repo="${REGISTRY}/${REGISTRY_NAMESPACE}/${image}"
docker buildx imagetools create "${repo}:${GITHUB_SHA}" --tag "${repo}:${VERSION}"
echo "Promoted \`${repo}:${VERSION}\` (from \`:${GITHUB_SHA}\`)." >> "$GITHUB_STEP_SUMMARY"
docker buildx imagetools create "${repo}:latest" --tag "${repo}:${VERSION}"
echo "Promoted \`${repo}:${VERSION}\` (from \`:latest\`)." >> "$GITHUB_STEP_SUMMARY"
done
Loading