From 722c366fbe24d3811806a34459f5999395af5c79 Mon Sep 17 00:00:00 2001 From: cliffhall Date: Wed, 11 Nov 2026 17:26:16 -0500 Subject: [PATCH] Stop v1 releases from moving the GHCR image's latest tag (#2958) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit docker/metadata-action's default flavor (latest=auto) adds `latest` on a tag event, so every v1 release re-pointed ghcr.io/…/inspector:latest at deprecated v1. Set latest=false; the version tag is unchanged. Co-Authored-By: Claude Opus 5.5 Signed-off-by: cliffhall --- .github/workflows/main.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index ed6e72846a..6e4b999291 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -116,6 +116,12 @@ jobs: uses: docker/metadata-action@v6 with: images: ghcr.io/${{ github.repository }} + # Do NOT drop this: on a tag event the default `latest=auto` adds a + # `latest` tag, so every v1 release would move the image's `latest` + # from the current v2 release to deprecated v1 (#2958). This is the + # GHCR counterpart of `publish-all`'s `--tag v1-latest` on npm. + flavor: | + latest=false - name: Set up QEMU uses: docker/setup-qemu-action@v3