Spitfire 0.13.0 release notes
Released: 2026-10-04
- Comparative runs, A/A calibration: while both environments run the same version, "Calibrate" runs a short comparison and records the environments' natural difference per step. Later comparisons show the raw, calibration and corrected differences; the verdict uses the corrected one and the acceptable threshold can't be narrower than the calibration's noise band. The verdict card says when there is no calibration, when it is older than 30 days or made with another test version.
- Closer to the root cause: when a run's threshold breaks or a breakpoint test breaks, the resource series at that moment are ranked by their jumps and saturation signals (CPU, memory, connection pool, queue) and a measured finding is written: "The system broke at 560 VUs; at the same time the orders-db connection pool filled up and checkout CPU went from 41% to 97%." Spitfire says only what happened at the same time, never why.
- Resource series on the run charts: a series from Prometheus or OTLP (e.g. pod CPU) is drawn over the run's own charts, aligned with the load stages. The Prometheus connection also works with Grafana Mimir; token-in-header auth added.
- Mobile: encrypted push when a threshold breaks or a spike happens during a run, when a synthetic monitor goes down and when a comparison comes out worse; high-priority abort from the app (POST /runs/{id}/abort); approving data-changing steps from the phone with biometric verification, recorded in the audit log.
Updating
Your installation tells you about a new release itself: admins see its notes and the update command for that installation at the top of the UI. The command backs up the database first and keeps the settings (Updating). You can also follow new releases with the RSS feed.