The title is a bit clickybaity, a better one would be: rolling back changes isn't as straightforward as just changing your git hash. In addition to the strateg

The title is a bit clickybaity, a better one would be: rolling back changes isn't as straightforward as just changing your git hash. In addition to the strategies mentioned, having backward-and-forward migrations for all database changes is essential. You need to have a plausible path for how to restore state to where it was before the broken change. If you've done the necessary engineering work, this can ultimately be packaged into a "rollback" button which does things like ramping down dark deploys.