A team that happily deploys on Friday afternoon is not braver than one that does not. They have just made deployment boring on purpose.
Three things get you there. First, an automated test suite that runs on every change and actually fails when something breaks. Second, small, frequent releases, so any one deploy carries little risk and is easy to reason about.
Third, fast rollback and real observability — if something does slip through, you see it in minutes and undo it in one click, not one hour.
None of this is exotic. It is the baseline we set up on every engagement, because the alternative — batching changes and holding your breath — is slower and more stressful for everyone.