Depends on your domain. I'm in embedded systems, with some safety critical parts. It costs millions of dollars to upgrade production after the release is done - we are not interested in your weekend fix, it better be right in the first place, or it is millions more to deploy the next update. That we are safety critical means that we wouldn't release anyway as we don't dare risk your change resulting in some worse safety issue than the one you are trying to fix. The minimum time for a critical fix to make it into production is 6 weeks of tests. (Yes we have extensive automated tests, they still don't catch everything - as anyone use uses the popular web platforms that release to production often has figured out)

> Great until something goes terrible wrong

Or when you have four team members, but one is on vacation and another called in sick today.

And the flipside is: don't abuse escape hatches.