Previous incidents

We identified the bad dependency, pinned it back to a known-good version, and added an automated test so this specific failure cannot ship again. The fix is already deployed now and we are monitoring.