Docker images missing version tags since 0.0.16

[gerbyzation]

New images are only published under latest and are not tagged with their version since 0.0.16. This makes it impossible to version pin the image. Due to #158 the deployment currently is broken and we lack the means to rollback.

[nissessenap]

I think the issue is rather easy.
The latest tags are called cloudflare-exporter-0.2.2 instead of 0.2.2.
Which we can see in the release flow:

cloudflare-exporter/.github/workflows/docker-release.yaml

Line 6 in a040ea9

- '[0-9]+.[0-9]+.[0-9]+'

@haad sorry for the direct ping, but it would be great if you can take a look at this.

[gerbyzation]

Looking at the image registry these don't show as container image tags. If you mean the git tags, it does seem that the tag format has changed and is probably the reason why the image tagging is now broken.

https://github.com/lablabs/cloudflare-exporter/pkgs/container/cloudflare_exporter/versions?filters%5Bversion_type%5D=tagged
https://hub.docker.com/r/lablabs/cloudflare_exporter/tags

[gerbyzation]

There's also no changelog on the releases since the tag format change

[nissessenap]

@gerbyzation if you want a new release, you can use my fork

All I have done is merged this PR https://github.com/nissessenap/cloudflare-exporter/pull/2, which is a simplified version of #160 where I have removed the possibility to push to dockerhub.

This image is signed, you know I won't perform any changes to it, and it doesn't use root thanks to KO.

docker pull ghcr.io/nissessenap/cloudflare-exporter:0.1.0

PS. this isn't any attempt from my to take over this repo in any way, I just don't want to wait for my PR to get merged before I start using this project.

[gerbyzation]

Thanks, the github container registry does show the untagged versions so I've grabbed the digest of the previous version and pinned to that for now - not a substitute for proper version tagging though 😄

[Alabate]

@nissessenap So if I understand properly, now that #160 is merged, we just need a new release to have a new tagged image ?

[nissessenap]

Yes please, that would be great <3

[lindeskar]

Heads-up that even with #160 merged, the existing 0.2.3 image is not the KO build. The plain 0.2.3 git tag points at d7e211b (2025-10-05) — one week before #160 merged — so when the tag was pushed on 2025-11-08, the old buildkit+Dockerfile workflow ran. The resulting ghcr.io/lablabs/cloudflare_exporter:0.2.3 has no USER and fails Kubernetes' runAsNonRoot:

Error: container has runAsNonRoot and image will run as root

Two more things that fell out while digging:

• The KO output only lives at ghcr.io/lablabs/cloudflare-exporter:latest (note the dash — the new workflow pushes to ghcr.io/${{ github.repository }}, not the underscore path that the chart's default image points at).
• cloudflare-exporter-0.2.3's Chart.yaml still has appVersion: 0.0.16.

So +1 to @Alabate — a fresh release tag cut from a post-#160 commit (plus an appVersion bump) is what's needed.