caddycmd.LoadConfig had a fourth parameter added
What happened?
2026/02/21 18:17:56 [INFO] Building Caddy 2026/02/21 18:17:56 [INFO] exec (timeout=0s): /home/m/packages/pkgroot/x86_64-linux/go-xcaddy/bin/go mod tidy -e go: downloading code.pfad.fr/check v1.1.0 go: downloading github.com/letsencrypt/pebble/v2 v2.10.0 go: downloading go.opentelemetry.io/otel/sdk/log/logtest v0.16.0 go: downloading github.com/letsencrypt/challtestsrv v1.4.2 2026/02/21 18:18:02 [INFO] exec (timeout=0s): /home/m/packages/pkgroot/x86_64-linux/go-xcaddy/bin/go build -buildmode=pie -ldflags -linkmode=external -extldflags '-pie -Wl,-z,relro -Wl,--as-needed -Wl,--undefined-version -Wl,-z,now -Wl,-z,noexecstack ' -X 'github.com/caddyserver/caddy/v2.CustomVersion=FrankenPHP v1.11.2 PHP 8.5 Caddy' -tags=nobadger,nomysql,nopgx -o /home/m/packages/buildroot/bin/frankenphp # github.com/dunglas/frankenphp/caddy /home/m/packages/source/frankenphp/caddy/php-server.go:116:22: assignment mismatch: 3 variables but caddycmd.LoadConfig returns 4 values 2026/02/21 18:18:17 [INFO] Cleaning up temporary folder: /tmp/buildenv_2026-02-21-1816.2659677130 2026/02/21 18:18:17 [FATAL] exit status 1 ✗ Command execution failed: Command exited with non-zero code: 1
I'll add it and update the caddy ref. I'm not sure why my build matrix started failing, I guess it somehow automatically pulls in a newer caddy version than we specify in the go.mod file?
Started today at midnight, runs yesterday were unaffected.
Build Type
Custom (tell us more in the description)
Worker Mode
No
Operating System
GNU/Linux
CPU Architecture
x86_64