From 23cef6f427426dfdb05bb0ee4502cf9296d568be Mon Sep 17 00:00:00 2001 From: librelad Date: Tue, 11 Aug 2026 21:17:35 +0100 Subject: [PATCH] docs(roadmap): record the notification channel in the updater refinements Co-Authored-By: Claude Opus 5 --- docs/roadmap/app-version-updater-and-cve.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/roadmap/app-version-updater-and-cve.md b/docs/roadmap/app-version-updater-and-cve.md index 9079929..4beb7bb 100644 --- a/docs/roadmap/app-version-updater-and-cve.md +++ b/docs/roadmap/app-version-updater-and-cve.md @@ -150,6 +150,7 @@ Why not the sketched `off|security|all` severity split: severity is a property o - **Check now forces a live registry lookup** — `updater check` (non-`auto`) sets `UPDATER_REGISTRY_FORCE=1`; previously the flag existed but nothing set it, so the button silently reused the 6h digest cache. Force also overrides `CFG_UPDATER_REGISTRY_INTERVAL=0`, making 0 mean "manual-only" as originally intended. - **Registry stamp out of /tmp** — the task-processor unit runs with systemd `PrivateTmp`, so the /tmp stamp existed once per namespace (daemon vs CLI, daemon's resetting every restart). Now at `/logs/updater_registry_checked`. - **Failed-auto honesty** — the scan emits each app's `auto_attempted_digest` (the one-shot no-retry stamp). When it matches `available_digest`, the UI stops claiming "installs automatically": the per-app detail says the build failed and won't retry, the fleet row gets an `auto failed` chip, and the Overview board counts it as *waiting for you* (warn) instead of quietly-installing (ok). +- **Failure notifications (2026-08-11)** — `libreportal notify` + `configs/general/general_notifications`: email (rides the Mail settings), ntfy, Gotify, Discord, Slack, Telegram, Pushover. One hook in the task processor reports every terminal task; the notify command applies the policy (`CFG_NOTIFY_EVENTS=failures|all|off`, cancelled never notifies). A failed auto-update now reaches the user with "already rolled back, won't retry" copy without the WebUI being open. Verified end-to-end through the live daemon against a mock endpoint. - **`CFG_TIMEZONE` label corrected** — it only sets containers' TZ; scheduled tasks follow the host clock. The old "System Timezone - Timezone for scheduled tasks" label promised a knob that never existed. ## 7. Build phases (each independently shippable)