Spitfire 0.15.0 release notes
Released: 2026-10-05
- Sequential comparison mode: with a single environment, or environments that share resources, the two releases take turns on the same environment (A, B, A, B; 2 rounds by default, up to 5). You switch the release: between turns Spitfire waits and tells you with a run.switch_needed webhook; confirm in the UI, with "spitfire cloud continue" or an API call. With a version endpoint on the environment it sees the switch itself. If no switch comes within 30 minutes (configurable) the comparison is invalid.
- In sequential mode the verdict card says "sequential comparison" and the uncertainty band is wider: the difference between rounds goes into the interval, so the band is at least 1.4 times as wide as in concurrent mode. The shared-infrastructure warning switches to sequential mode in one click.
- CLI: spitfire cloud run --compare ... --compare-mode sequential [--rounds N] [--switch-timeout 30m] [--auto-switch]; Enter on a terminal also confirms the switch. A scheduled sequential comparison on one environment needs a version endpoint.
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.