Skip to content

v4.0.1 — registry entry and published images

Choose a tag to compare

@PhilflowIO PhilflowIO released this 10 Sep 21:11
· 469 commits to main since this release
0fde7c5

No functional change to the server. src/ is untouched since 4.0.0; this release exists so two things can reach people who are not building from source.

Fixed

The registry entry named environment variables that do not exist. It advertised DAV_BASE_URL, DAV_USERNAME and DAV_PASSWORD, while the code reads CALDAV_SERVER_URL, CALDAV_USERNAME and CALDAV_PASSWORD. Configuring the server from the MCP Registry produced a process that exited during startup. The names were written during a schema migration in April and never matched the code at any point (#69, #70).

Added

Published container images. ghcr.io/philflowio/dav-mcp now carries every release, tagged with the exact version, the minor line and latest:

docker run -d -p 3000:3000 --env-file .env ghcr.io/philflowio/dav-mcp:4.0.1

Previously the only documented path was cloning and building. The image is verified against a live CalDAV backend before it is pushed, so a release cannot publish an image that was never observed booting (#68).

The registry entry documents the OAuth2 path. AUTH_METHOD and the six GOOGLE_* variables are now declared, with secrets marked as such.

Changed

The container runtime is distroless — non-root (uid 65532), no shell, no package manager, both base images pinned by digest, and roughly a quarter of the previous size. Thanks to @camden-bock for the work (#64).

The image healthcheck follows PORT. It previously probed :3000 regardless, reporting a healthy server as unhealthy whenever the port was overridden.

Internal

CI builds the image on every pull request, boots it against a live CalDAV server, waits for Docker's own healthy verdict and asserts the non-root user and absence of a shell. Nothing built the image before (#66).