Release Notes

v1.5.3 - Current release

What changed in v1.5.3

Container image update required. Pull v1.5.3 and recreate the container with the same /config volume and existing external storage key configuration. Every published v1.4.x image needs this one-time update to receive launcher protocol 4.
v1.5.3 supplies the image foundation. It does not publish a runtime-generation payload. Future compatible releases can deliver a complete signed application and official Python package generation through Settings > Updates in the same container.
Let future compatible releases update the application and official Python packages together from Settings > Updates. ChannelWatch prepares, verifies, activates, and rolls back the complete signed runtime generation as one unit.
Keep Python interpreter, OS, glibc, Supervisor, and image-owned verifier updates on the container image path.
Require future image-floor retention to pass compatibility, restart, and rollback checks on both native AMD64 and native ARM64.
Keep channelwatch doctor on the image-owned application and Python environment, isolate it from selected-generation import paths, and report the actual diagnostic runtime identity.
Keep runtime security tests independent of the hosted test interpreter’s writable permissions while continuing to reject unsafe interpreter paths.
Verify unpublished milestone recovery before publishing the replacement image and its four native migration reports.
Make interrupted update preparation retryable after the current runtime starts again, while preserving the selected release and saved configuration.
Keep update policy button labels readable on smaller screens.
The older-client restart report in issue #22 remains open. Its cause has not been proven, and v1.5.3 does not claim to resolve it.

Current feature baseline

The v1.5.3 site describes the current ChannelWatch app surface. The main v0.9 release-line baseline includes:

multi-DVR monitoring, per-DVR status, per-DVR history, and per-DVR session isolation
stable /api/v1 routes plus feed aliases for calendar, RSS, and Atom consumers
health, readiness, startup, and Prometheus metrics endpoints
first-run setup wizard with discovery, manual add, and connection testing
backup and restore workflows in the admin UI and API
sanitized debug bundles from the UI and doctor CLI
per-DVR notification routing, delivery logs, retries, and circuit-breaker protection
notification provider plugins loaded from /config/plugins/notifications
security status reporting for API-key, RBAC-with-fallback, RBAC-only, and auth-disabled modes
Docker, Compose, Helm, and Unraid deployment assets
zero built-in telemetry, with optional user-supplied DSN storage but no wired crash-reporting client

Upgrade notes

Existing settings are migrated through the versioned settings migration pipeline, with an automatic backup before migration.
Use the web UI or CHANNELS_DVR_SERVERS for multi-DVR setup.
Remove old single-DVR env vars from new examples, but do not panic if an existing deployment still has them; the current release keeps them as warning-backed compatibility inputs.
Pin coderluii/channelwatch:1.5.3 when you want repeatable deployments, or use latest when you intentionally want rolling updates.

New docs to read first

Previous releases

v1.4.5

See the app changelog for the exact v1.4.5 entries.

v1.4.1

See the app changelog for the exact v1.4.1 entries.

v1.4.0

See the app changelog for the exact v1.4.0 entries.

v1.3.0

See the app changelog for the exact v1.3.0 entries.

Older pre-v0.7 releases are historical. For exact app changelog entries, use the app repository changelog.