Do you have a Continuous Integration (CI) Server?

It's all about managing the risk of change

Building and testing the software on each change made to the code helps to reduce the risk of introducing unwanted changes in its functionality without us realising.

The various levels of automated testing that may form part of the CI pipeline (e.g. unit, contract, integration, API, end-to-end) all act as change detectors, so we're alerted to unexpected changes almost as soon as the code that created them is committed to the code repository.

The small change deltas between builds in combination with continuous testing should result in a stable and "known good" state of the codebase at all times.