Spitfire 0.60.0 release notes
Released: 2026-10-28
- One-click update (Docker, opt-in): ./install.sh docker --updater on turns it on, and the License → Version and updates card shows an Update now button. The database is backed up first, running tests are waited for, and only a release from the signed list is installed; the progress stays on the page while the controller restarts.
- Only a separate small updater container reaches the Docker socket; the controller never does. Off by default; the request and its outcome go into the audit log.
- If an update goes wrong, the UI shows the error, the backup's path and the rollback command.
- With one-click update off, the update is laid out in numbered steps, and the page reloads with the new release once the command is done.
- Guard: when a test's own p95 or error rate crosses your limit, Spitfire steps the load down with a live req/s ceiling, climbs back slowly once things calm down, and stops the run at the stop limit. Every step shows in the event feed, on the run page and in the report. In the editor under "Thresholds and guard", with presets; off by default.
- Opt-in health data sharing: Spitfire sends nothing unless an installation admin turns it on. Then only an error/health summary goes out once a day (version, OS, counts of Spitfire's own fixed error messages, crash function names, runner counts). Never test content, URLs, hostnames, IPs, users, e-mails or the license; the card shows the exact payload. SPITFIRE_TELEMETRY=off disables it entirely.
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.