francislavoie
commented
11 months ago I've already explained in detail the situation we're in, in #307.
Like I said, even if we automate parts of it (we will, we just need to find time, we're busy people with lives and full-time jobs), there are parts that must be done manually, because actual decisions have to be made that aren't so cut-and-dry.
We recently locked down opening new issues for now because we want to avoid a slew of duplicate issues which add nothing to the discussion (like this one does, honestly) because the limiting factor is our own time and vacation schedule. But we'll loosen it up again soon.
I posted a workaround in #307. Use that for now if you absolutely need v2.7.3.
mholt
I have my own automated caddy builds that check for new stable and beta releases, but I frequently get errors because certain beta releases (and now stable releases) do not have docker releases for both caddy and caddy builder.
I still don't quite understand why docker releases for caddy are not automated, but it really causes issues with my own timely releases of docker builds (with the cloudflare dns plugin).
I end up missing versions that never get built and never have an idea if it's just delayed or not being built at all (like the last beta release).
Is there no way to automate this at all like most other software? Surely, if there is a will, there is a way.
See issue: https://github.com/caddyserver/caddy-docker/issues/307
Furthermore, it looks like people who haven't contributed to caddy-docker are unable to open issues, which is why I had to open an issue here.
I'm really getting the impression that the caddy team isn't open to discussion on how the docker release process can be improved.