Omit specifying Caddy version to always use latest #1020
Mmm. Pinning versions is generally a best practice? It means we don't get weird breakage when caddy decides to introduce non-backwards compatible changes and our CI falls over or worse still peoples production environments fall over.
Actually best practice seems to be now to directly download caddy binary from its api:
instead of building it from source
From what I remember, in the dunglas docker, it was changed to a specific version because sometimes the mercure package wasn't ready on time and there was an error during the build. You need to keep a close eye on this.
FROM caddy:2.7-builder-alpine doesnt limit patch version so no wonder it breaks when new version comes up
Either patch version should be set in both places (FROM and xcaddy)
or download from api like in newest symfony docker as I mentioned above: https://github.com/dunglas/symfony-docker/blob/main/Dockerfile#L115
IIRC it broke on the 2.6 > 2.7 transition. Which is to be expected under semver. We went from specifying latest to 2.6 specifically due to that. Then bumped it to 2.7.3 when the plugin was updated.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?