Release Notes

v1.1.2 - Current release

Signed in-app update for the v1.1.0 image line. An operational v1.1.0 or v1.1.1 installation does not need a newer image.
Prevent completed recordings from later being reported as interrupted when the public recording response omits the job ID. Resolve the exact file-to-job identity from DVR metadata for completion and periodic reconciliation, without matching by title or time. Addresses #15 and duplicate #17.
Keep failed, malformed or unmatched identity lookups unknown instead of treating them as proof that an active recording disappeared. Use one additional file-list read for a reconciliation snapshot and retain explicit failure/cancellation handling.

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

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

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

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

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

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