deploy: switch docker-compose back to :latest

Pinning to :1.4.2 was a one-shot safety measure today after the
:1.4.1 GHCR tag never published and we needed Coolify to deploy a
known image. Now that :1.4.2 is verifiably live and the healthcheck
fix is in the image, switch back to :latest so future GHCR builds
auto-roll to production without a docker-compose edit.

Self-hosters who prefer pinning can override via
docker-compose.override.yml — the upstream compose default stays
on :latest as before.
This commit is contained in:
Marc-André Bombeck committed 2026-05-08 18:14:12 +02:00
1 parent 7cb9221339
commit cfbd822862
1 file changed
+1 -1
+1 -1
View File
@@ -9,7 +9,7 @@ services:
# to the last release that's verifiably running on self-host installs to
# rule out runtime / Docker-network issues. No `build:` block on purpose:
# we want Coolify to PULL the prebuilt image, not build from source.
image: ghcr.io/mbombeck/healthlog:1.4.2
image: ghcr.io/mbombeck/healthlog:latest
container_name: healthlog-app
ports:
- "3000:3000"