docs(uptime-kuma): prepare W8 upgrade packet #510

Merged

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

2026-05-26 21:56:40 +02:00

codex commented

2026-05-26 21:53:30 +02:00

Collaborator

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

Canary Context Pack

Product story

W8 should upgrade one small module only when the evidence says it is worth doing and rollback is boring. uptime-kuma is a plausible W8.2 pilot because it is tailnet-only and self-contained, but still stateful enough to require backup and an explicit gate.

What changed

Added a W8.2 upgrade packet for uptime-kuma with current/candidate digest evidence, release-note delta, backup/rollback contract, smoke contract, and the explicit runtime approval phrase.

Why it changed

This prepares the runtime pilot decision without mutating production or pretending W8 is complete without evidence.

Files touched

state/cycle/W8-uptime-kuma-upgrade-packet.md

Relevant context

modules/uptime-kuma/module.yaml
modules/uptime-kuma/runbook.md
state/cycle/W8-module-upgrade-prep.md
state/cycle/W8-readiness-2026-05-26.md
Uptime Kuma upstream GitHub releases and Docker Hub tag metadata

Runtime evidence

No runtime mutation. No compose/env/deploy changes. Read-only upstream checks show current desired tag 2.1.3 and candidate stable tag 2.3.2.

Known constraints

The module observed digest currently differs from Docker Hub's current 2.1.3 manifest-list/linux-amd64 digest, so the packet deliberately does not pin the module artifact digest. Runtime pilot must capture fresh live registry/runtime evidence before apply.

Explicit out-of-scope

Runtime apply/promote/restart
Compose/env image tag change
Volume backup execution
Forgejo/core upgrade

Requested decision

Approve/merge this packet so W8 can make a separate runtime-pilot decision.

Merge blockers

Packet claims a runtime change happened
Missing backup/rollback/smoke contract
Candidate evidence not source-backed

Spec sources read

modules/uptime-kuma/module.yaml — current desired/runtime metadata
modules/uptime-kuma/runbook.md — state/backup/recovery constraints
state/cycle/W8-module-upgrade-prep.md — W8 sequencing
state/cycle/W8-readiness-2026-05-26.md — candidate selection
state/cycle/W8-minio-init-pilot.md — packet style and no-op precedent
Uptime Kuma GitHub release API/pages — release delta
Docker Hub tag API — current/candidate digest metadata

Test plan

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

Closes #506

Canary status: missing — fire canary 3+3 manually before merge ## Canary Context Pack ### Product story W8 should upgrade one small module only when the evidence says it is worth doing and rollback is boring. `uptime-kuma` is a plausible W8.2 pilot because it is tailnet-only and self-contained, but still stateful enough to require backup and an explicit gate. ### What changed Added a W8.2 upgrade packet for `uptime-kuma` with current/candidate digest evidence, release-note delta, backup/rollback contract, smoke contract, and the explicit runtime approval phrase. ### Why it changed This prepares the runtime pilot decision without mutating production or pretending W8 is complete without evidence. ### Files touched - `state/cycle/W8-uptime-kuma-upgrade-packet.md` ### Relevant context - `modules/uptime-kuma/module.yaml` - `modules/uptime-kuma/runbook.md` - `state/cycle/W8-module-upgrade-prep.md` - `state/cycle/W8-readiness-2026-05-26.md` - Uptime Kuma upstream GitHub releases and Docker Hub tag metadata ### Runtime evidence No runtime mutation. No compose/env/deploy changes. Read-only upstream checks show current desired tag `2.1.3` and candidate stable tag `2.3.2`. ### Known constraints The module observed digest currently differs from Docker Hub's current `2.1.3` manifest-list/linux-amd64 digest, so the packet deliberately does not pin the module artifact digest. Runtime pilot must capture fresh live registry/runtime evidence before apply. ### Explicit out-of-scope - Runtime apply/promote/restart - Compose/env image tag change - Volume backup execution - Forgejo/core upgrade ### Requested decision Approve/merge this packet so W8 can make a separate runtime-pilot decision. ### Merge blockers - Packet claims a runtime change happened - Missing backup/rollback/smoke contract - Candidate evidence not source-backed ## Spec sources read - `modules/uptime-kuma/module.yaml` — current desired/runtime metadata - `modules/uptime-kuma/runbook.md` — state/backup/recovery constraints - `state/cycle/W8-module-upgrade-prep.md` — W8 sequencing - `state/cycle/W8-readiness-2026-05-26.md` — candidate selection - `state/cycle/W8-minio-init-pilot.md` — packet style and no-op precedent - Uptime Kuma GitHub release API/pages — release delta - Docker Hub tag API — current/candidate digest metadata ## Test plan - `PYTHONPATH=control-plane python3 -m platformctl.cli validate all --json` → exitCode 0 Closes #506

codex added 1 commit

2026-05-26 21:53:30 +02:00

docs(uptime-kuma): prepare W8 upgrade packet

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

Details

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

Details

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

Details

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

Details

canary-required / canary (pull_request) Has been skipped