What a deploy actually does
Build, upload, switch, verify, and the moment where two versions run at once.
A deploy is not one action, it is four, and knowing which one failed tells you what to do about it.
- Build
Turn source into something runnable. Fails here mean nothing changed, so you are safe. - Upload
Move the result to where it will run. - Switch
Point traffic at the new version. This is the risky instant. - Verify
Confirm it actually works with real traffic.
During the switch, both versions are briefly live at once. Someone will load a page from the old version and have their next request served by the new one. This is precisely why the expand-then-contract pattern from the Data track exists: both versions must be able to coexist for a few seconds.
The safest shape is small and frequent. A deploy containing one change has one suspect when something breaks. A deploy containing three weeks of work has forty, and you will be bisecting them at the worst possible time.
What to remember
- Build, upload, switch, verify: failures at each stage mean different things.
- Two versions run simultaneously during the switch.
- Rolling back code does not roll back data or side effects.
Terms in this lesson
Show field notes toggles a search param the loader reads. With it off, the slow promise is never created, so nothing streams.