Save known-good version
Before uploading a new archive, know which deployment definitely worked and where its ZIP lives.
- ZIP saved.
- Deployment URL recorded.
- Changelog clear.
Spare bridge
Rollback plan
Rollback plan is needed before deploy, not after checkout suddenly turns into a locked door.
A good launch knows how to move forward and retreat calmly.
Define rollback triggers
Not every warning requires rollback. But checkout, auth, paid AI, privacy, and broken homepage require quick response.
- Checkout broken.
- Auth broken.
- Privacy leak.
- Home page broken.
Rollback and message
After rollback, check production, logs, and write a short note: what broke and what not to repeat.
- Production works again.
- Cause recorded.
- Repeat deploy blocked until fix.
checklist
What to check
- Known-good ZIP exists.
- Known-good Vercel deployment is known.
- Critical features listed.
- Short manual smoke test after rollback exists.
red flags
When to stop
- New deploy breaks payment.
- New deploy exposes personal data publicly.
- New deploy creates widespread 500s.
- New deploy blocks account sign-in.
done when
Definition of done
- Rollback can be done in a few clicks.
- Main pages are checked after rollback.
- Incident cause is recorded.
related doors