InfraAudit uses semantic versioning. Minor and patch releases are backward compatible. Major releases may include breaking changes — these are documented in the Changelog and on the GitHub releases page.
Before you upgrade
Read the changelog
Check the Changelog or the GitHub releases page for the target version. Look for migration notes, new required environment variables, or breaking changes. Back up your database
Take a database backup before upgrading. If a migration fails and you need to roll back, you’ll need a clean restore point.For Docker Compose: Note your current version
Docker Compose upgrade
Pull the latest images and restart the stack:
The API runs any pending database migrations automatically on startup. Watch the logs to confirm:
You should see output like:
If migrations fail, the API exits with a non-zero code. Check the container logs for the SQL error and open a GitHub issue with the error message if you need help.
Kubernetes upgrade
Update the image tag in your API deployment manifest:
Apply the updated manifest and wait for the rollout:
Kubernetes performs a rolling update by default — old pods continue serving traffic until the new pods pass their readiness checks. If a migration fails, the new pod will fail its readiness check and Kubernetes will not route traffic to it. Your existing pods remain available.
Pin to specific image tags (e.g. v1.3.0) rather than using latest. This gives you explicit control over when upgrades happen and prevents unexpected changes from automatic pulls.
Pinning to a specific version
For production deployments, always specify an exact version tag:
Docker Compose
Kubernetes
Edit your docker-compose.yml to specify the image version: Set the image tag in your deployment manifest: Downgrading
Downgrading is only supported within the same minor version — for example, v1.3.2 to v1.3.0. Downgrading across minor versions requires running down migrations, which may be destructive.
To downgrade within the same minor version:
- Roll back the image to the previous version tag.
- Run down migrations for any files applied during the upgrade, one at a time:
Always restore from a database backup when downgrading across minor versions. Running down migrations in production carries risk of data loss.
Upgrade schedule
There is no forced upgrade schedule. InfraAudit does not phone home or require license renewals. Upgrade at your own pace, but staying within one major version of the latest release is recommended to ensure you have current security patches.