Upgrading

Before replacing the binary or container image, confirm the data directory is backed up and mounted — that’s where Weaver stores its persistent state.

Docker

docker compose pull
docker compose up -d

After restart, open Weaver and check Monitoring, Logs, and Settings > General.

Homebrew

brew update
brew upgrade weaver-usenet
brew services restart weaver-usenet

If you need a same-version Homebrew packaging fix immediately, use:

brew update --force
brew reinstall weaver-usenet

Release Binary

Stop the running process, replace the binary with the new release, then start it with the same data directory and command-line flags.

Before Upgrading

Export a backup from Settings > Backup.
Confirm the data directory is persistent.
Note any reverse proxy base URL.
Check that no maintenance action is in progress.

After Upgrading

Confirm the web UI loads.
Check Monitoring for queue and bandwidth cap state.
Check Logs for migration or startup errors.
Verify API integrations if they use API keys.