Updating ChannelWatch

Install ChannelWatch v0.9.10 normally once with Docker, Unraid, Compose, or Helm. After that, compatible app-only releases can be handled from Settings > Updates.

ChannelWatch Update Center settings tab showing current version, latest release, runtime ABI, update status, no-auth warning, and update action buttons — **Update Center** The Update Center checks trusted release metadata, shows image-required releases clearly, and keeps the backup/apply/rollback flow in one place. Captured from ChannelWatch v0.9.10 with safe demo data.

Use Update Center first

Open ChannelWatch.
Go to Settings > Updates.
Click Check for updates.
If a compatible app update is available, click Apply update.

ChannelWatch verifies the signed manifest, verifies the signed app bundle, creates a pre-update backup, activates the bundle, restarts the app, and records the update job state so refreshes still show what happened.

Rollback

If an active bundle fails during startup, ChannelWatch's image-stable launcher rolls back to the previous runtime or the image copy. When rollback metadata is available and the UI is reachable, Settings > Updates also shows a Roll back action.

Rollback changes the active app runtime. It does not restore old settings or database state. Use Settings > Backup & Restore when you need to restore data.

Container image update required

Some releases cannot be applied inside the current container image. ChannelWatch will show container image update required when a release changes:

Python dependencies
base image or OS packages
Supervisor or container startup behavior
runtime ABI
Helm or deployment assumptions
persistent settings schema

When you see that state, update with your normal Docker, Unraid, Compose, or Helm process.

Auth-disabled installs

If CW_DISABLE_AUTH=true, anyone who can reach the UI can run admin operations, including updates and rollback. Keep auth-disabled installs on a trusted private network only.

Where update files live

Update runtime files live under /config/channelwatch-runtime/:

Path	Purpose
`active.json`	Active app bundle pointer.
`latest.json`	Last trusted update manifest.
`rollback.json`	Previous runtime pointer and backup path.
`update-job.json`	Last update/check/rollback operation state.
`update.lock`	Single-flight update lock.
`releases/vX.Y.Z/`	Extracted verified app bundle.

Downloaded app bundles are not included in normal app backup zips. Keep a separate /config backup routine for disaster recovery.