[1.4.2] — 2026-05-08
Fixed — Production deploy hotfixes
- Dashboard and Insights pages no longer crash for users without
weight data.data?.summaries.WEIGHTonly protected the outer
object — the optional chain stopped one level too early, so
brand-new users (wheresummariesis undefined) hit
TypeError: undefined is not an object (evaluating 'E?.summaries.WEIGHT')
on first load. Nowdata?.summaries?.WEIGHT. - Container healthcheck uses
127.0.0.1instead oflocalhost.
busybox-wgetin Alpine resolveslocalhostto IPv6::1first,
but Next.js standalone listens on IPv40.0.0.0:3000only — so the
healthcheck always returned ECONNREFUSED, Docker marked the
container unhealthy, and Traefik returned 503 from the public URL
even though the app was actually running. The Dockerfile-level
HEALTHCHECKalready used 127.0.0.1; thedocker-compose.yml
override was the one that drifted tolocalhost. Fixed.
Notes
- The 1.4.1 GHCR image never published cleanly (the docker-publish
workflow reported success in GH Actions but the
ghcr.io/mbombeck/healthlog:1.4.1tag returnedmanifest unknown
when Coolify tried to pull). The 1.4.2 release supersedes 1.4.1
and includes everything 1.4.1 was supposed to ship — the v1.4.1
source onmainwas always healthy; only the Coolify deploy
surface was broken.