For rollback, stop new workers first, restore the compatible application image, apply the documented database down/forward-fix plan, and validate Keycloak client compatibility. Prisma migrations are forward-only in production; destructive changes require expand/migrate/contract phases and an explicit restore point.
Updates and rollback
Resolve new dependency and image versions in a review branch, record licenses and digests, run schema diff, migration tests, container scans, and the full test suite. Never use mutable image tags.