Skip to content
mcorucu docs
AutoCore1.0.0-rc.1 · Release Candidate
1.0.0-rc.1 · Release Candidate1 min read

Re-Upgrade After Rollback

Reconcile a successful application rollback with the target release before attempting a re-upgrade.

After application rollback, first verify that the database schema and data are compatible with the previous image. The rollback script explicitly does not roll back the database because migrations are forward-only.

Re-upgrade requires a fresh preflight, target manifest, backup gate, and compatibility decision. Preserve any data written while the previous image was active and account for provider or media side effects.

Verification

Run the target release’s upgrade dry-run, compare migration state, verify image availability, and repeat post-upgrade acceptance. Never assume that rollback followed by re-upgrade is a zero-data-loss operation.

Related articles

Upgrade ProcedureExecute a source-verified AutoCore upgrade with a backup gate, immutable image update, migrations, and verification.Application Image RollbackRoll back immutable application images without implying database migration reversal.Database Restore DecisionDecide whether a verified PostgreSQL restore is safer than retry, roll-forward, or image rollback.