From 956d29032f6c3af7866f51f6ae644988728e4e6c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Fri, 8 May 2026 17:40:08 +0200 Subject: [PATCH] fix(deploy): pin to :1.4.0 (the :1.4.1 GHCR tag never published) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The docker-publish workflow's run for the v1.4.1 tag reported success in GH Actions, but no `1.4.1` tag landed on the ghcr.io registry (`docker pull ghcr.io/mbombeck/healthlog:1.4.1` returns 'manifest unknown'). Coolify tries to pull, fails, and never replaces the old container — so the site stays 503 with no upstream at all. Repinned to `:1.4.0` which is verifiably present on GHCR (2h old). Healthcheck fix from the previous commit (127.0.0.1) stays. The :1.4.1 publish failure is a separate followup — likely related to the docker-publish workflow not handling the squash-merge release flow correctly for the tag-on-main scenario. Tracked for v1.4.2. --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index 2ad7d68fd..dea412392 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -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.1 + image: ghcr.io/mbombeck/healthlog:1.4.0 container_name: healthlog-app ports: - "3000:3000"