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

Application Image Rollback

Roll back immutable application images without implying database migration reversal.

The source rollback script selects a previous image tag, supports --dry-run, pulls the target, recreates services, and verifies health/readiness. It explicitly warns that the database is not rolled back because migrations are forward-only.

Code
./infra/scripts/rollback.sh "$PREVIOUS_IMAGE_TAG" --dry-run

The command is a source reference for the AutoCore repository, not a public production command with real paths or tags. Use the authorized delivery procedure for a buyer installation.

Database boundary

This operation does not roll back the database. Confirm schema compatibility before changing application images.

Verification

Confirm image availability, schema compatibility, health, readiness, routing, and data preservation. Then decide whether re-upgrade remains safe.

Related articles

Re-Upgrade After RollbackReconcile a successful application rollback with the target release before attempting a re-upgrade.Rollback PlanningDecide between roll-forward, application rollback, and database restore before changing an AutoCore release.Database Restore DecisionDecide whether a verified PostgreSQL restore is safer than retry, roll-forward, or image rollback.