The rule
Upgrade one minor version at a time, and always to the latest patch of each minor version. Skipping a minor version is not supported. For example, from 5.2.1 you upgrade to 5.2.2, then 5.3.5, then the latest 5.4 patch, then the latest 6.0 patch, then the latest 6.1 patch, then the latest 6.2 patch. Each minor release is tested as an upgrade from the latest patch of the previous minor. Each patch is tested from the previous patch. Other routes are not tested, which is why skipping is not supported. Within one minor version, you can go straight to its latest patch, for example from 6.0.0 to 6.0.6. Patches are backward compatible, but a security fix can still need an action from you. Check the upgrade impact of each patch you cross in the release notes.Find your next stop
Find the row for the version you run now. Upgrade to the version in Next stop, check that it works, then repeat from that row.
Find the latest patches on GitHub releases.
Ignore release candidates. Versions before 4.0 are covered in the archive.
At each stop
- Read the version page in the table, including its patch actions.
- Upgrade with the runbook for your setup: Kubernetes, Docker Compose or one-click.
- Check that the upgrade worked, and that all migrations and background jobs finished, before you start the next stop.
Pin exact versions
- Set exact version tags, for example
ghcr.io/formbricks/formbricks:6.0.5. Never uselatestto upgrade: it jumps straight to the newest release and skips your stops. - Use the Compose file, Cube model files and migration images from the same release as the app. The configuration checklist lists every pin to change.
- On Kubernetes, use the chart with the same version as the app: since 4.0, each release publishes its chart with the app’s version number. If your values override the image tag, set it to the same version.
- Keep your PostgreSQL major version and storage setup. A newer example file for fresh installs is not a reason to change them.