Fast deploy puts your latest push ahead of the previous one

Until now, several pushes in a row left each deployment queued behind the one before it: the version you actually wanted live went out last, after builds that had become pointless.
Your project's “Deployment” tab now carries a “Fast deploy” switch: once it is on, a new deployment cancels the one still running for that container and takes its place, without waiting for it to finish.
The effect stays scoped to the container concerned: redeploying your “api” container never interrupts a build in progress on your “web” container.
The setting is off by default, and a deployment dropped this way carries its own reason in the history, so you can tell it apart from a manual cancellation.