Spitfire 0.19.0 release notes
Released: 2026-10-08
- Query suggestions from the schema (installation admins only): Connections → "Suggest from schema". From your own Spitfire server, Spitfire reads your database's catalog (schemas, tables, columns, primary keys, indexes, foreign keys, row estimates; never table data) and suggests SELECTs from it: lookup by id, by an indexed column, foreign key joins, pagination and counts. Each suggestion is checked with EXPLAIN (the query itself never runs) and full table scans are flagged; the ones you pick become a query mix step or separate steps. PostgreSQL, MySQL/MariaDB, SQL Server and Oracle.
- Consent first: before the first read the admin reads and accepts a consent text; who agreed, when, from which IP and browser, for which connection, with which text version, which scope and which warnings were shown is stored in the database and in the audit log. A new consent is asked when the connection's address, user, tunnel or production flag changes, when the scope widens or the text changes; a consent can be revoked (the record stays).
- Privilege check: the connected user's privileges are read; read-only shows green, write privileges orange, superuser/admin a red warning plus an extra checkbox. A ready script creating a least-privilege read-only user is shown for each database. SQL connections gain a "production" flag that brings a strong warning.
- Optional sample values (with a separate consent): a bounded sample of real key values is taken from a table into a data file for the parameters; the values stay on your server.
- SSH tunnel for SQL connections (PostgreSQL, MySQL/MariaDB, SQL Server, Oracle): reach the database through a bastion with a key or a password. The server's host key is always verified ("trust on first use" shows the fingerprint for you to confirm); passwords and keys are stored encrypted and never returned by the API. The tunnel works on the controller and on the runners during load tests. Only installation admins may change SSH settings.
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.