[RFC][PATCH 1/4] ci: tag builds must not tag containers with latest

0 views
Skip to first unread message

Felix Moessbauer

unread,
Sep 17, 2025, 8:48:38 AM (9 days ago) Sep 17
to kas-...@googlegroups.com, Felix Moessbauer
When pushing tags, we must not overwrite the ":latest" container image
tag. Otherwise bugfix tags overwrite the tag that should point to the
latest master version.

Signed-off-by: Felix Moessbauer <felix.mo...@siemens.com>
---
.github/workflows/release.yml | 1 -
1 file changed, 1 deletion(-)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index f4b5f3237..ac3e0a3e6 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -41,7 +41,6 @@ jobs:
provenance: false
outputs: type=registry,rewrite-timestamp=true
tags: |
- ghcr.io/${{ github.repository }}/${{ matrix.image-name }}
ghcr.io/${{ github.repository }}/${{ matrix.image-name }}:${{ env.RELEASE_VERSION }}
ghcr.io/${{ github.repository }}/${{ matrix.image-name }}:latest-release
annotations: ${{ env.DOCKER_METADATA_OUTPUT_ANNOTATIONS }}
--
2.51.0

Jan Kiszka

unread,
Sep 19, 2025, 3:49:23 AM (7 days ago) Sep 19
to Felix Moessbauer, kas-...@googlegroups.com
Thanks, applied already.

This pattern also dates back to the time of non-reproducible images.
There, I wanted to avoid that the released image is deviating from latest.

Jan

--
Siemens AG, Foundational Technologies
Linux Expert Center
Reply all
Reply to author
Forward
0 new messages