Rollback

Rollback restores the Helm release to a prior known-good revision. Database migrations may not be automatically reversible, so always review release notes and back up PostgreSQL before upgrading.

Before Rolling Back

1. Identify the last known-good Helm revision.
2. Confirm whether the target release introduced database migrations.
3. Confirm whether data restoration is required.
4. Preserve logs and events from the failed release.
5. Notify users if the platform may be unavailable during rollback.

Rollback Command

helm rollback governance-platform <revision> --namespace governance

Verify

After rollback:

• Confirm pods return to ready state.
• Confirm the browser login flow.
• Confirm core Governance Studio workflows.
• Confirm API integrations can authenticate.
• Confirm storage-backed attachments and integrity workflows still work.