Quarry 1.0.0
Stable interface
- First stable release of Quarry's CLI, local GUI, MCP server and public Python
query API. The documented commands, workspace/saved-query formats and result
contracts follow the compatibility policy in COMPATIBILITY.md. - PostgreSQL, MySQL and Redis are the stable engine scope within the documented
test matrix. Neptune/openCypher remains experimental; its local empty endpoint
is not a graph database emulator or proof of AWS/IAM compatibility. - Default query execution is read-only. CLI and MCP writes require explicit
authorization with additional prod confirmation; GUI queries stay read-only.
Python callers are responsible for authorizingallow_write=True. - Exact numeric strings, duplicate/empty column metadata, Redis JSON replies,
bounded results and active-tab exports form the stable result contract.
GUI SQL drafts and bounded result snapshots persist when browser storage is
available. Large results remain in-session.
Upgrade from 0.x
- No workspace or saved-query migration is required from 0.25.1. The 1.0 change
establishes the stable contract and package metadata; database query behavior
is unchanged from the audited 0.25.1 implementation. - Upgrading from older 0.x versions also adopts the 0.25.1 corrections: CLI
defaults to 500 rows (--max-rows 0disables the cap), big integers/exact
decimals are strings, and duplicate object-result columns get unique suffixes.
CLI JSON stays a row array; GUI/MCP/Python return QueryResult. - SQL batches, psql backslash commands and PostgreSQL data-modifying CTEs are
explicitly unsupported. Use individual authorized statements, with RETURNING
where rows are needed.
Fixed
- GUI autocomplete stays closed after Escape even when an earlier input refresh
or column lookup finishes late. Typing again enables suggestions normally.
Release validation
- Source distributions exclude local audit reports and development artifacts.
- Candidate acceptance covers clean CLI/GUI/MCP installation and upgrade from
0.25.1, including connections, saved queries, drafts, prior results and no
automatic query execution on reload. - PyPI publication requires passing tests, coverage, browser and package checks
against the exact release tag. See COMPATIBILITY.md for platform and network
boundaries; the stable package does not promote experimental Neptune support.
Install: pipx install quarry-db==1.0.0
Upgrade: pipx upgrade quarry-db