chore(uptime-kuma): stage W8 desired image update #513

Merged

pdurlej merged 1 commit from codex/w8-uptime-kuma-upgrade-pr into main

2026-05-26 23:30:10 +02:00

codex commented

2026-05-26 23:10:18 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Canary Context Pack

Product story

W8 needs one real low-risk runtime pilot candidate. uptime-kuma has a current upstream security/bugfix release and a small rollback surface, but it is still stateful. This PR stages desired metadata only so runtime remains a separate operator decision.

What changed

Updated modules/uptime-kuma/module.yaml desired source/artifact from 2.1.3 to 2.3.2, including the Docker Hub manifest-list digest. Updated the W8 Uptime Kuma packet to record that desired metadata has been staged.

Why it changed

#510 established 2.3.2 as the W8.2 candidate. This PR makes the desired artifact explicit before any backup/recreate/smoke step.

Files touched

modules/uptime-kuma/module.yaml
state/cycle/W8-uptime-kuma-upgrade-packet.md

Relevant context

#506/#510 Uptime Kuma upgrade packet
#507/#511 W8.3 stateful/sidecar gate
modules/uptime-kuma/runbook.md
Uptime Kuma upstream release 2.3.2
Docker Hub tag metadata for louislam/uptime-kuma:2.3.2

Runtime evidence

No runtime mutation. spec.runtime.image_observed intentionally remains louislam/uptime-kuma:2.1.3@sha256:dac5... until an explicit runtime pilot runs and smokes.

Known constraints

uptime-kuma is stateful (home-platform_uptime_kuma_data). Runtime apply requires backup-before and the explicit phrase w8-uptime-kuma-runtime-approved.

Explicit out-of-scope

RS2000 backup/recreate/smoke
Compose/env changes
Updating spec.runtime.image_observed
Any broad W8/core upgrade

Requested decision

Approve/merge this repo-only desired metadata update. Runtime remains blocked until explicit operator approval.

Merge blockers

Treating this PR as deploy approval
Accidentally changing runtime observed evidence
Missing rollback/backup link in the packet

Spec sources read

modules/uptime-kuma/module.yaml — desired/runtime metadata
modules/uptime-kuma/runbook.md — state and recovery constraints
state/cycle/W8-uptime-kuma-upgrade-packet.md — candidate packet
state/cycle/W8-stateful-sidecar-gate.md — stateful runtime gate
Docker Hub tag metadata for louislam/uptime-kuma:2.3.2 — digest evidence
Uptime Kuma GitHub release 2.3.2 — release evidence

Test plan

PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json → exitCode 0

Refs #389
Refs #506

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story W8 needs one real low-risk runtime pilot candidate. `uptime-kuma` has a current upstream security/bugfix release and a small rollback surface, but it is still stateful. This PR stages desired metadata only so runtime remains a separate operator decision. ### What changed Updated `modules/uptime-kuma/module.yaml` desired source/artifact from `2.1.3` to `2.3.2`, including the Docker Hub manifest-list digest. Updated the W8 Uptime Kuma packet to record that desired metadata has been staged. ### Why it changed #510 established `2.3.2` as the W8.2 candidate. This PR makes the desired artifact explicit before any backup/recreate/smoke step. ### Files touched - `modules/uptime-kuma/module.yaml` - `state/cycle/W8-uptime-kuma-upgrade-packet.md` ### Relevant context - #506/#510 Uptime Kuma upgrade packet - #507/#511 W8.3 stateful/sidecar gate - `modules/uptime-kuma/runbook.md` - Uptime Kuma upstream release `2.3.2` - Docker Hub tag metadata for `louislam/uptime-kuma:2.3.2` ### Runtime evidence No runtime mutation. `spec.runtime.image_observed` intentionally remains `louislam/uptime-kuma:2.1.3@sha256:dac5...` until an explicit runtime pilot runs and smokes. ### Known constraints `uptime-kuma` is stateful (`home-platform_uptime_kuma_data`). Runtime apply requires backup-before and the explicit phrase `w8-uptime-kuma-runtime-approved`. ### Explicit out-of-scope - RS2000 backup/recreate/smoke - Compose/env changes - Updating `spec.runtime.image_observed` - Any broad W8/core upgrade ### Requested decision Approve/merge this repo-only desired metadata update. Runtime remains blocked until explicit operator approval. ### Merge blockers - Treating this PR as deploy approval - Accidentally changing runtime observed evidence - Missing rollback/backup link in the packet ## Spec sources read - `modules/uptime-kuma/module.yaml` — desired/runtime metadata - `modules/uptime-kuma/runbook.md` — state and recovery constraints - `state/cycle/W8-uptime-kuma-upgrade-packet.md` — candidate packet - `state/cycle/W8-stateful-sidecar-gate.md` — stateful runtime gate - Docker Hub tag metadata for `louislam/uptime-kuma:2.3.2` — digest evidence - Uptime Kuma GitHub release `2.3.2` — release evidence ## Test plan - `PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json` → exitCode 0 Refs #389 Refs #506

codex added 1 commit

2026-05-26 23:10:19 +02:00

chore(uptime-kuma): stage W8 desired image update

base-is-main / guard (pull_request) Successful in 1s

Details

canary-required / collect-diff (pull_request) Successful in 5s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 5s

Details

platformctl plan / auto-apply scope (pull_request) Successful in 24s