Skip to main content
Applies to: installations entering or updating within 5.4, both editions and deployment methods. The base-release steps apply when crossing 5.4.0; for later updates within 5.4, review the patch actions. Upgrade from: the latest 5.3 patch (5.3.5). Skipping a minor version is not supported; see Upgrade paths.

Before

Patch actions

Apply each change you cross on this release line, even when installing a later patch. These entries do not add intermediate installation stops. Read the published patch notes for other fixes too. A patch without an additional row still needs the standard checks.

During

Use the 4.x/5.x maintenance procedure. Keep traffic closed and writers stopped. Run app migrations before Hub migrations; inspect their exit status. The response-index build can exceed the historical Compose migration timeout. Do not continue over a failed or invalid index.

After

  • Verify existing password/SSO accounts, 2FA and MCP clients, including token renewal after sign-out.
  • Check dashboard queries, feedback mutations with their intended API keys, and Hub job delivery.
  • Confirm migrations and the response index completed; run the shared acceptance checks.

Recovery

Application schema changes are additive relative to 5.3, but Hub/dependency updates require their own recovery assessment. After a rollback to 5.3, accounts created there may need the issuer repair before rolling forward. Use coordinated restore when required. All changes: 5.3.5 → 5.4.0, 5.4 patches. Dependency changes Database preparation and recovery Feedback API permissions Authentication changes