Closed coolaj86 closed 4 months ago
See the release notes, it's intentional. https://github.com/caddyserver/caddy/releases/tag/v2.8.0
Caddy does not follow semver. Think of v2
as the product version, and .8
as the major version, if you prefer to think of it that way.
There's a bunch more to the stack trace, but I believe that what's given here is sufficient to understand and identify the problem.
I imagine that there's some rationale as to why this isn't technically a breaking change because it of "Core" vs "Community" API guarantees or some such.
That doesn't matter as much to me as that a deploy failed unexpectedly, so it looks like we should assume that minor versions can be major breaking changes from now on.