Release Notes

v0.9.10 - Current release

Show v0.9.10 as container image update required because it repairs Docker entrypoint and runtime launcher behavior.
Run the Docker entrypoint through /venv/bin/python so the stable image launcher can resolve Update Center runtime state with installed dependencies.
Pass core launcher arguments such as --stay-alive through runtime_launcher.py while keeping unsupported UI launcher arguments rejected.
Treat blank DVR names as optional by falling back to the DVR host or IP during settings load, settings save, health checks, /api/v1/dvrs, and core DVR connections.
Preserve settings _version metadata when defaults are merged so schema migration backups do not repeat after settings reloads.
Accept UTF-8-with-BOM settings.json files so Windows-edited configs do not block startup.
Keep v0.9.10 release notes focused on the repair instead of repeating old known-limit sections.

The v0.9.10 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

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:0.9.10 when you want repeatable deployments, or use latest when you intentionally want rolling updates.

See the app changelog for the exact v0.9.9 entries.

See the app changelog for the exact v0.9.8 entries.

See the app changelog for the exact v0.9.7 entries.

See the app changelog for the exact v0.9.6 entries.

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