Updating

The server checks for new releases and shows a notice in the admin panel when one is available. The Beta channel updates setting in Admin > Settings > General switches the notice between stable and pre-release versions.

Before Updating

• Take a backup through the admin panel (or pg_dump for external PostgreSQL). See Backups.
• Read the release notes for breaking changes or manual steps.
• Note the image tag you are currently running, so you know what to roll back to.

Updating with Docker

1. Pull the new image:

   docker compose pull

2. Recreate the container:

   docker compose up -d

3. Confirm the new version:

   docker compose exec odeion odeion --version

Database migrations run automatically on startup; there is no separate migration step. Expect a short downtime while the container restarts.

Tag Pinning

The latest tag updates whenever you docker compose pull, which makes updates implicit. Pinning a version tag (for example registry.odeion.app/odeion/server:0.5.2) makes every update an explicit edit to your compose file, and makes rollback a one-line change. The installation wizard can generate a pinned configuration.

Rolling Back

Downgrading across database migrations is not supported: once a newer version has migrated the database, an older binary may not understand the schema. To roll back safely:

1. Stop the server: docker compose down.

2. Set the previous image tag in docker-compose.yml.

3. Start it: docker compose up -d.

4. If the new version had already run migrations, restore the backup you took before updating. See Backups.

If you skipped the backup and migrations already ran, do not start the old version against the migrated database; ask for help through the support page first.