Release tag - but unclear what the actual update is

[smileBeda]

I am confused, there is a new release tag that came out a few hours ago (ChangeDetection warned me), but I do not understand what actually changed.

Since there is no changelog or similar, it is hard to detect what went down, is Caddy now included here?!
Because up and until now, I build caddy on my host:

FROM caddy:builder AS builder

RUN xcaddy build \
    --with github.com/caddy-dns/cloudflare

FROM caddy:latest

COPY --from=builder /usr/bin/caddy /usr/bin/caddy

So I would not want a second caddy being pulled in. A short changelog probably would avoid some spookiness feelings (as in.... is this tag even legit, after months of no PRs suddenly a tag is weird, one first thinks... nothing even is being released until scanning the PRs)

[williamjacksn]

Looks like the change in this tag is meant to enable container image publishing to ghcr.io/caddy-dns/cloudflare, but the image isn't visible here: https://github.com/orgs/caddy-dns/packages

I'm guessing the image permissions aren't set to allow public pulls.

[smileBeda]

... with a bundled Caddy, as far I understand, hence my concern - I and several others are building caddy on our own pulling cloudflare-caddy in from github.com/caddy-dns/cloudflare.

I am rally not sure what would happen if I now update my install - did neither have time to test nor to dig in the PRs deeply.

Generally I always am a bit skeptical when no changelogs and no release notes are available, but in this specific case it is somewhat the only option around :|

[williamjacksn]

Previously this project did not publish a container image. Now it looks like they want to.

Assuming the image you build adds caddy-dns/cloudflare and nothing else, and assuming this new project-provided image actually appears, you may have the chance to stop building an image yourself.

If you continue to build your caddy image as you described, you will not somehow get an extra copy of caddy in your image.