Skip to content

SpelunkDB 0.3.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Nov 00:28
· 554 commits to main since this release
0f2b06b

SpelunkDB 0.3.0 adds DuckDB and SQL Server, opens SQLite files on a server through SSH, lets
AI agents write where you allow it, and makes sharing connections with a team safe and
password-free.

New engines

  • DuckDB: local files (or a new empty database), nested types shown as DuckDB writes
    them, and several tabs on the same file.
  • SQL Server: T-SQL batches (GO, BEGIN … END), several result sets per batch, the
    per-tab database selector, cancelling and TLS.
  • SQLite on a server: choose a tunnel whose last hop holds the file and write its path
    there. SpelunkDB runs that server's sqlite3 (in its safe mode) through the tunnel: the file
    is never copied, and the server's own locks keep it safe.

A smoother desktop

  • An activity bar for connections, query history, saved queries and settings; the explorer
    can be hidden and resized.
  • A database selector per query tab for MySQL, MariaDB and SQL Server, that follows USE.
    Double-click a database in the explorer to open a tab already connected to it.
  • Settings open in a dialog over your tabs.
  • Copying rows as a single INSERT with every selected row.

AI agents (MCP)

  • Every engine is served: PostgreSQL, MySQL, MariaDB, SQL Server, SQLite and DuckDB, each
    behind a read-only barrier the engine itself enforces. For DuckDB, agents never reach files
    or the network.
  • Writes, only where you allow them: "Agents can: Read and write" in a connection's
    options. Writes go through a separate execute_write tool, one statement at a time in its
    own transaction. DROP, TRUNCATE, DELETE/UPDATE without WHERE, procedures,
    permissions, settings and anything that reaches files or other servers are always refused.
    Every write is audited.

Sharing connections with a team

  • Trust is no longer forever: if a git pull changes a repository connection or tunnel
    (another server, secret, tunnel or command), or adds one, it is not used until you have
    seen the change, field by field, and accepted it.
  • Shared SSH server keys: commit them as .spelunk/known_hosts, and a newcomer's first
    connection through a bastion is already verified. A different key is refused.
  • Logins without passwords: client certificates for PostgreSQL, MySQL and MariaDB (the
    private key always stays outside the repository), and short-lived tokens from AWS RDS IAM,
    Azure (Microsoft Entra ID) and Google Cloud SQL IAM.
  • Personal values asked once: when a connection needs ${user.…} variables you have not
    defined (your database user, for example), SpelunkDB asks for all of them at once and saves
    them in your user.toml.
  • spelunk check for the team repository's CI or pre-commit hook: it fails on files that do
    not load, passwords written in commands and private keys in the repository, and warns about
    risky settings.

Fixes

  • MySQL and MariaDB: verify-ca now checks only the authority that signs the server's
    certificate, as it should, so connecting by IP address works.
  • DuckDB: a file can be opened again right after its sessions close.

Also

  • Automatic updates are prepared and signed, but switched off until releases have a public
    home: Settings → Updates says so. Install this version by hand.

Installing

  • Windows: SpelunkDB_0.3.0_x64-setup.exe installs for the current user without admin
    rights; the .msi is there for managed machines. The installers are not signed yet, so
    SmartScreen may warn: "More info" → "Run anyway".
  • macOS: the .dmg for Apple Silicon (aarch64) or Intel (x64). The app is not notarized
    yet: open it with right-click → Open the first time.
  • Linux: .deb, .rpm or the AppImage.
  • CLI / MCP server: the spelunk-* archives hold the spelunk binary.

This is still a preview: expect rough edges, and please report them.

Everything in this release

  • List every commit since the previous release in its notes (dbdbcb6)
  • Add a DuckDB driver (e1eda0c)
  • Improve desktop navigation and query workflow (4748520)
  • Fix DuckDB reopen after closing sessions (1e095d0)
  • Add a SQL Server driver (c3747c1)
  • Extend the desktop workflow to SQL Server and close stray completions (6ff2549)
  • Propose ADR-018: SQLite files on a server, through SSH (77e09a0)
  • Open SQLite files on a server through SSH (e71be83)
  • Show settings in a dialog instead of a tab (11df64f)
  • Let agents write on the connections the user allows (ADR-019) (d952f73)
  • Serve MySQL, MariaDB, SQL Server and DuckDB in the MCP (ADR-020) (593e4ad)
  • Prepare signed automatic updates for the app, off until releases are public (ADR-021) (a6f0677)
  • Ask again when a trusted repository connection changes (ADR-022) (46cf49d)
  • Verify SSH servers against the team's reviewed known_hosts (ADR-022) (0e4de0b)
  • Log in without passwords: client certificates and cloud tokens (ADR-022) (e33f25a)
  • Fix verify-ca for MySQL and MariaDB: trust the authority, not the name (0cd7847)
  • Ask once for the personal variables a connection needs (ADR-022) (1897b84)
  • Add spelunk check, for a team repository's CI and pre-commit hook (ADR-022) (029d171)

Full changelog: v0.2.0...v0.3.0