15.35Deployment rollback
Suppose:
1.2.4
deploys and error rate immediately spikes.
You need a rollback strategy.
Conceptually:
stop routing traffic to 1.2.4
↓
restore known-good 1.2.3
Exact mechanisms depend on environment and deployment process.
The important point:
Rollback should use a known-good immutable artifact, not emergency code editing in production.