I think if you're afraid to ship after 4pm, then you should write better code and/or test it better. There are things I'm afraid to do late (say upgrading 3rd party software), but shipping a new version of my software? Don't see why not.
Your wording seems to indicate that you work by yourself. That's fine, but things change when large teams and systems are involved. You can't vouch for every single change or the inter-dependencies between all systems.
It's pretty elitist too. "Your code only breaks because you suck" doesn't make for good software engineering practices. Everyone makes mistakes.
If you have a micro service that takes requests over / foo and /bar and returns JSON that needs to fit certain properties, and you’re submitting a change to fix a corner case bug or add a new property that isn’t read, sure.
If you are working on low level networking infrastructure that is used in tandem with thousands of different workloads you need to support, won’t work.
Eventually, your totally avoidable gamble will backfire.
You know where I did get pings all the time? In companies that had strict release windows and would never deploy on Friday. Which in result motivated people to "push now & hotfix later" to meat the release cutoff date.
Things can and do break. It's impossible to test everything. That's why.