mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
207010e8fa
The digest-pinning section explained how to set HEALTHLOG_IMAGE_REF and never said what happens if it is left behind. It stays until someone changes it, and every deploy in between reports success while the running instance holds the previous release. Adds the warning, the two post-deploy checks that would have caught it (the version endpoint AND the running container's image, because the first alone can be served from a cache), the note that a suspiciously fast deploy is a signal, and the duplicate-key trap: the platform accepts two rows with the same key without warning and does not define which wins.