Spitfire 0.8.0 release notes
Released: 2026-10-03
- A license's term now starts on the day its key is first entered on an installation; new keys must be entered within 30 days of being issued. Earlier keys still run from their issue date. New keys also work on older Spitfire versions.
- The License page shows the plan, activation date, end date, days left, add-ons and the plan's features; the key ID can be copied for upgrades and renewals on the buy page.
- Admins see a yellow banner 14 days before the end and a red one once the grace period starts; it can be dismissed for the day.
- A renewal key starts its new term the day after the old end date; Growth add-ons (users, VUs and requests/s, run length, runners and locations) are added to the plan's limits.
- Synthetic monitoring, performance budgets and PR/MR comments come with Growth yearly and Enterprise. Project pass and Quarter have the free edition's synthetic monitoring (1 monitor, at most every 15 minutes). The check looks at the key's feature list, not the plan name; earlier paid keys without a feature list have everything on.
- The Turkish UI keeps technical terms as engineers say them: SSO, endpoint, backend, observability, fault injection, dry run, uptime, runner token, header, body.
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.