Deployment Rollback

Outcome: Use Deployment Rollback to release or recover the change safely, with a clear record. User context: Release 3.2 raises the error rate five times, while version 3.1 and the data schema are compatible. Automation restores 3.1, checks service health and traffic, and records the incident. Reverting source code alone cannot undo deployed files, permanent data changes, queued jobs, or outside effects. Delivery concept or operation: Deployment Rollback. Why it fits: Use this term when release health crosses a set limit and a tested good version can be restored safely. Do not use it when: Do not promise one-click rollback until you test data-schema fit, stateful work, outside effects, monitoring, and when to fix forward. Delivery requirements: Name the code repository and target. List preconditions, changes, review and CI checks, conflict and data-loss risks, release order, and the rollback or recovery command. Repository safeguards: Keep unpublished work and a clear history. Do not run destructive steps without an explicit backup. Check the exact code diff and remote target before publishing. Acceptance criteria: Review the intended diff and pass all required checks. Keep the target version traceable. Practice failure recovery and keep published history clear. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Repository, branch, team activity, release environment, approval owner, protected checks, and rollback target.