Upgrades

Each version of ProofTrail is an image tagged with its date, such as ghcr.io/alaibe/prooftrail:2026.10.30.4, with a number after the date for a later build the same day. latest always points at the newest one, but pinning a date tag means an upgrade happens only when you choose it.

Upgrading#

1. Check the last backup in Settings › Backups is recent, or start one there.
2. Change the image tag in docker-compose.yml to the new date.
3. Pull it and recreate the containers:

docker compose pull
docker compose up -d

The web container migrates the database and reloads the compliance library when it starts; the queue worker and the scheduler follow once it is healthy. Migrations only move forward, so your data is carried over as it is.

New frameworks and checks#

An upgrade can bring new frameworks, controls and checks with it. New ones are off until you turn them on in Compliance › Frameworks. Changes to the ones you use apply at once, and the next evaluation re-runs their checks.

Going back#

To go back to the previous version, restore the backup from before the upgrade, then set the old tag. An older version doesn't run on a database that a newer one has already migrated.