Upgrade
Upgrading Infrahub involves pulling the latest container images, running database and schema migrations, and restarting services. The specific steps vary by edition (Community vs Enterprise) and deployment method (Docker Compose vs Helm).
Before you upgrade​
Upgrade path: Upgrades are supported only from the previous minor version (N-1), for example from Infrahub 1.3 to 1.4. If you need to upgrade from N-2 or older, upgrade sequentially one minor version at a time.
Backup first: Even though a smooth migration is anticipated, we strongly recommend creating a backup before upgrading. See Backup and restore.
Release notes: Review the release notes for any version-specific upgrade instructions. In Infrahub 1.2 and later, the upgrade process was streamlined with a unified upgrade command. For earlier versions, refer to the release notes for specific instructions.
Upgrade guides​
Select the guide for your edition and deployment:
- Upgrade Community — Docker Compose, Helm, and Dev/Demo deployments
- Upgrade Enterprise — Docker Compose and Helm deployments
- Upgrade the observability stack — Force-recreate observability services after compose file changes
Known issues​
Migration failing because of transaction memory limit reached in Neo4j​
For large database/schema migrations, you may encounter a Transaction memory limit reached error in Neo4j.
To work around this, you can disable the transaction memory limit by setting the dbms.memory.transaction.total.max to 0 in your Neo4j configuration.
We are working on a more robust solution to handle large migrations without hitting this limit in future releases.