A semver-compliant patch update silently corrupted financial reports through changed locale handling.
Situation
You're the platform lead at a financial services company. A routine patch update to a date-formatting library just broke production. The change was semver-compliant and passed all tests, but financial reports have been rendering incorrect dates for 12 hours before detection. You've identified the root cause and rolled back the dependency.
Stakes
The immediate incident is resolved, but you need to prevent this class of failure. What's your first step in redesigning the dependency pipeline?