Spitfire 0.5.13 release notes
Released: 2026-09-30
- Regression alerts against the baseline: when a test has a baseline run, every finished run is compared with it (p95, p99, error rate, requests/s; with the test's tolerances). Slack, Teams and e-mail messages list what got worse; a clear regression also sends the new run.regressed event (off by default on new channels). You hear that a nightly test slowed down before any threshold breaks.
- Failed request samples: the run page shows a few failed requests per step and outcome (target, error, failed check, a few response headers, the first 2 KB of the body). Tokens in the address are masked, cookies are never kept, steps that do not fail cost nothing; errorSamples "off" in the test's options turns them off.
- Test version history: versions, who saved them and the diff with the current one on the test page; an old version is restored as a new one (history is kept).
- Client certificates (mTLS) and private CAs: a new Client certificate type under Connections; HTTP, WebSocket and SSE steps pick it. The key is stored encrypted and never enters the test definition; saving checks the certificate and key belong together, the Test button checks it has not expired.
- Data retention setting (License page): days kept for per-second data and logs, runs (at least 7; baselines are never deleted) and the audit log (at least 30). The page shows what would be deleted before you save. The audit log stays append-only: only this pass may delete entries older than 30 days, and it records that it did.
- Tests → Open JSON: a test definition file (e.g. from spitfire.tr/en/examples) opens in the new-test editor.
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.