Skip to main content
Applies to: installations crossing 5.1, including upgrades from v4 to a later v5 target. Both editions and deployment methods. Apply 5.0 prerequisites first when coming from v4.

Before

The configuration checklist covers image pins, existing credentials and storage/proxy preservation. New optional features are not prerequisites for this upgrade.

During

Use the 4.x/5.x maintenance procedure. Keep traffic and writers stopped through app and Hub migrations. Require both to exit successfully before starting the target app. A Compose up -d or an Argo sync beginning is not evidence that migrations finished.

After

Verify existing feedback sources, dashboards, SSO, uploads and the shared acceptance checks. Check the migration containers/Jobs themselves for completion and inspect any failure before continuing.

Recovery

The table and enum rename is not reversed by an older image. Restore matching configuration, images and coordinated data when rolling back across this boundary. See recovery. Source: 5.0.2 → 5.1.0.