m11r
February 22, 2026, 5:14am
1
I just noticed that Caddy v2.11.0 and v2.11.1 were both tagged yesterday (and made available awhile in several package managers such as Homebrew and the Cloudsmith deb repo), but aren’t showing up as GitHub releases along with all the normal binary artifacts (yet?).
Was this intentional, or just delayed due to some of the release changes described a few months ago? Thanks!
Yeah. Life got in the way of us publishing the release notes. Coming soon. Duplicate of No GitHub releases / release notes for 2.11.x · Issue #7511 · caddyserver/caddy · GitHub
2 Likes
m11r
February 22, 2026, 6:07am
3
@francislavoie No problem, life happens… appreciate the update! I thought I maybe missed some other change to the release process or something like that, so wanted to make sure.
matt
February 22, 2026, 3:06pm
4
The release is coming… the release action failed after more than an hour, I believe, so we had to redo it, and by that time some family things came up but I’ll be publishing release with notes soon. It’s about halfway done.
2 Likes
not available as docker image
Mohammed90
February 23, 2026, 3:47pm
6
Docker image release require a bit of manual process, so they tend to take longer.
master ← francislavoie:patch-1
opened 04:50AM - 23 Feb 26 UTC
https://github.com/caddyserver/caddy/releases/tag/v2.11.1
1 Like
Not complaining. Just telling it.
2 Likes
See this issue, we wrote this exactly for moments like this
opened 09:26PM - 23 Aug 25 UTC
closed 09:33PM - 23 Aug 25 UTC
If you came here because you tried to update Caddy but found that the Docker ima… ge is not the latest version, here's why:
We publish Caddy's Docker image as part of the [Docker Official Images](https://docs.docker.com/docker-hub/repos/manage/trusted-content/official-images/) program. This means when we push an update, there are multiple humans involved, plus a significant amount of CD pipeline time. These are the steps involved:
* **New Caddy release:** A new version of Caddy is tagged by @mholt. All binaries are built and published as a [GitHub release](https://github.com/caddyserver/caddy/releases), which takes about 20-25 minutes. Since these binaries (with verified checksums) are what we ship in the Docker containers, we must wait for this step to finish.
* **Docker repo update:** One of the [Caddy Docker](https://github.com/caddyserver/caddy-docker) maintainers (usually myself or @hairyhenderson, whichever of us is available first) follows the steps outlined in the [README](https://github.com/caddyserver/caddy-docker#release-instructions-for-maintainers). At the same time, we update other dependencies (such as Alpine/Windows base image versions, the Go version for the builder image, [xcaddy](https://github.com/caddyserver/xcaddy), and [dist files](https://github.com/caddyserver/dist)).
Example PR: [https://github.com/caddyserver/caddy-docker/pull/415](https://github.com/caddyserver/caddy-docker/pull/415)
* **Docker Official Images PR:** We then publish the updated Dockerfiles (via the stackbrew config) to the [Docker Official Images repo](https://github.com/docker-library/official-images).
Example PR: [https://github.com/docker-library/official-images/pull/19745](https://github.com/docker-library/official-images/pull/19745)
* **Review by DOI maintainers:** Next, we must wait for one of the Docker Official Images maintainers to review and merge the new release. This can take anywhere from minutes to days, depending on their availability (weekends, vacations, time zones, etc.).
* **Build process:** Finally, the Caddy images (across all supported architectures and variants) are built using the [DOI Jenkins job queue](https://doi-janky.infosiftr.net/). This build step can take many hours, especially if other projects have recently pushed updates and the queue is long.
---
So, with that context, we ask for your patience. We do our best to get releases published as quickly as possible, but some parts of the process are outside our direct control.
3 Likes
