Reading the failing build's typed events, then comparing it to the last green build.
A real assertion, not flakiness — read straight from the typed failure event, no console log to grep.
Failure: CheckoutServiceTest.appliesDiscount — AssertionError: expected 0.90 but was 1.00
Against the last green build, the only changed input is
com.example:pricing 2.3.0 → 2.4.0 — that bump changed the discount rounding.
Build Scan: https://develocity.example.com/s/o3eszckkes4ri