From 6ce3f6569527aa09a3083e2b5b972a300ffff322 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Sun, 13 Sep 2026 12:12:04 +0200 Subject: [PATCH] LIVE-TEST (controller v0.238.0 slice 4 Scenario F), REVERTED IN THE SAME SESSION: uptime-kuma 2.4.0 -> alpine:3.20 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Scenario F of the guarded-update live validation, the same way the 2026-09-01 spike did it: the new "version" is an image that starts and exits immediately, so the app never becomes healthy and must be HELD — and then restored from its named copy. catalog_since moves with the image line; the revert restores it. Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS --- templates/uptime-kuma/.felhom.yml | 2 +- templates/uptime-kuma/docker-compose.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/templates/uptime-kuma/.felhom.yml b/templates/uptime-kuma/.felhom.yml index 0a373d4..bd18ab0 100644 --- a/templates/uptime-kuma/.felhom.yml +++ b/templates/uptime-kuma/.felhom.yml @@ -10,7 +10,7 @@ subdomain: "status" slug: "uptime-kuma" # catalog_since: the date THIS repo last changed this app's pinned images. Any commit that # changes an image: line must set this to the same day (see CLAUDE.md). -catalog_since: "2026-07-18" +catalog_since: "2026-09-13" # --- Resource hints (displayed on deploy screen) --- resources: diff --git a/templates/uptime-kuma/docker-compose.yml b/templates/uptime-kuma/docker-compose.yml index f489cbf..b15fd61 100644 --- a/templates/uptime-kuma/docker-compose.yml +++ b/templates/uptime-kuma/docker-compose.yml @@ -8,7 +8,7 @@ services: uptime-kuma: - image: louislam/uptime-kuma:2.4.0 + image: alpine:3.20 container_name: uptime-kuma restart: unless-stopped environment: