NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #730 by repository stars
Latest stable
v0.55.0
Last release 20 days ago
02 Nov 2026
Ships on a steady schedule
a new release about every 1 weeks
Nearly every release is documented
notes for 57 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
350 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
[#601], [#615], [#628], [#629], [#640]: New SLQ string-matching functions. See Query Guide for per-driver behavior and SQLite ASCII-CI quirks.
SLQ string-matching functions. See Query Guide for per-driver behavior and SQLite ASCII-CI quirks.
contains, startswith, and endswith.icontains, istartswith, and iendswith.like and ilike: % and _ are wildcards.sq inspect now has --markdown and --html output formats that generate schema documents with embedded entity relationship diagrams.
sq inspect also gained a mermaid-erd output format (--format=mermaid-erd) that emits the bare Mermaid entity-relationship diagram source for source and table schema inspection, with no surrounding document.SLQ syntax-error reporting in both text and JSON error formats. You can set the new config option error.format.text.verbose to false if you prefer the previous (less-verbose) text error format.
sq inspect now omits an index whose key positions are all expressions (previously MySQL and SQLite reported such an index with an empty columns list).sq inspect now preserves the true key arity and position of indexes that contain functional/expression keys. A key like lower(b) in CREATE INDEX ix ON t (a, lower(b), c) is reported as an empty-string entry in the index's columns, so it is no longer indistinguishable from a real two-column (a, c). Applies to SQLite, DuckDB, MySQL, and Postgres.INTERVAL values now render in DuckDB's native, round-trippable text form (e.g. 1 year 2 months 3 days 04:05:06.789) instead of the previous ad-hoc Go-style μs string.sq inspect of a SQL Server source no longer returns tables from schemas other than the source's current schema.unsupported Scan, storing driver.Value type string into type *time.Time when a DATETIME/DATE column stores text that mattn/go-sqlite3 doesn't natively convert — most commonly Rails' microsecond-precision datetime(6) columns. sq now re-runs the same timestamp parse and falls back to the raw text only when the value is genuinely unparseable.sq <command> --format=FORMAT (e.g. sq inspect --format=xlsx) no longer fails with a spurious "diff does not support output format" error. The format check for sq diff was being applied to every command's --format flag; it's now scoped to sq diff itself.--insert into a MySQL or Postgres table no longer fails when a same-named table exists in another schema.@handle.table:alias form on the left of a pipeline (e.g. @sakila.actor:a | .a.first_name) no longer silently collapses to SELECT * FROM <table>..actor | .first_name:count, @sakila.actor:count, or join(.film_actor:count, ...)) now applies that alias instead of silently dropping it. An alias that is an argument reference (e.g. :$x) is now rejected with a clear error rather than silently discarded.join no longer fails when the participating sources contain tables with the same name (e.g. @src1.actor | join(@src2.actor, .actor_id)).Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
🐥🦆 [#437]: Beta DuckDB support. The duck driver supports most of the DuckDB type system; and includes a standard set of in-tree extensions (json, parq
duck
driver supports most of the DuckDB
type system; and includes a standard set of in-tree extensions (json,
parquet, icu, fts, httpfs, excel, inet, autocomplete,
tpch, tpcds). See the
driver docs.sq inspect now reports
foreign keys (fk.outgoing / fk.incoming per table), unique
constraints, and indexes for every SQL driver (ClickHouse skipped — no
foreign-key concept). Composite and cross-schema references are
supported; see the driver-specific caveats in the
inspect docs.sq now features a
--render-sql flag, which
prints the SQL (derived from SLQ input) that would be executed against
the target database, instead of running it. Honors --format with:
text or raw: the rendered SQL is printed.json or yaml: a structured payload is printed containing the
original SLQ, the rendered SQL, any
--arg, the
dialect and information about the sources that the query touches.# $ sq --render-sql --yaml '@sakila/pg.actor | join(@sakila/my.film_actor, .actor_id) | .first_name, .last_name, .film_id | .[0:5]'
slq: "@sakila/pg.actor | join(@sakila/my.film_actor, .actor_id) | .first_name, .last_name, .film_id | .[0:5]"
sql: SELECT "first_name", "last_name", "film_id" FROM "actor" INNER JOIN "film_actor" ON "actor"."actor_id" = "film_actor"."actor_id" LIMIT 5 OFFSET 0
dialect: sqlite3
sources:
target: "@join_xukcx3ye"
inputs:
- "@sakila/pg"
- "@sakila/my"
libsq.SLQ2SQL now returns a structured
*libsq.RenderResult type instead of string. Any libsq library
consumers must update call sites; the sq CLI is unaffected.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
🐥 [#501]: Beta Oracle support, built on the pure-Go go-ora driver. No Instant Client required. Kudos to @drluckyspin for indulging enterprise Larry ha
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#552]: Agent-focused skill content under skills/sq/ (prompts and references) to help AI assistants use sq, plus related nfpm/AUR packaging metadata.
skills/sq/ (prompts and
references) to help AI assistants use sq, plus related nfpm/AUR packaging
metadata. Kudos to @drluckyspin../site/ dir instead
of in a separate repo.md.Catalog correctly.Nothing published for this version
🐥 [#503]: Initial ClickHouse support. This is a beta release of the ClickHouse functionality; please open an issue if you find problems.
Nothing published for this version
[#470]: Previously, the --src.schema=[CATALOG.]SCHEMA flag did not allow the schema or catalog name to begin with a digit. This is now permitted. Kudo
#470: Previously, the --src.schema=[CATALOG.]SCHEMA flag did not allow
the schema or catalog name to begin with a digit. This is now permitted.
Kudos to @majiayu000.
# Inspect schema "123schema" via the @pg1 source
$ sq inspect @pg1 --src.schema=123schema
# Inspect schema "789schema" in catalog "456catalog" via the @pg1 source
$ sq inspect @pg1 --src.schema=456catalog.789schema
#542: Upgrade codebase to Go 1.26.
Nothing published for this version
Nothing published for this version
🫡: This patch release addresses issues reported by @Dialga.
🫡: This patch release addresses issues reported by @Dialga.
sq sql now uses the usql lib for SQL input mode determination
(does the SQL input execute a query or a statement?) replacing the custom
implementation introduced in v0.48.11. The usql impl is battle-tested:
there's no point reinventing that wheel.sq version handling.
sq version now returns faster by reducing the update-check timeout from
2s to 500ms. Additionally, the version check now uses the official
homebrew-core formula instead of the legacy tap. There's still future work to be
done here to make it possible to configure or disable this update-check behavior.sq now warns instead of erroring when the config file's
config.version is newer than the sq build version. This allows users to
downgrade to older sq versions for testing or debugging, at the small risk
of config schema incompatibilities (which will likely error out). There's
future work to be done to improve how sq stamps the config schema version
in sq.yml (currently it uses the build version rather than tracking actual
config schema changes).Nothing published for this version
[#502]: `sq sql` now properly executes single SQL statements (INSERT, UPDATE, DROP, etc.) instead of incorrectly running them as queries.
#502: sq sql now properly executes single SQL statements (INSERT, UPDATE,
DROP, etc.) instead of incorrectly running them as queries.
sq sql is designed to accept
only a single SQL statement/query in the SQL input string; behavior is
undefined for multiple statements in the input.#520: sq add and sq ls erroneously printed source password for SQL Server URLs
in some circumstances.
#469: Column widths were too wide when using --no-header flag. Header text
is now excluded from column width calculation when headers are disabled.
Thanks to @majiayu000 for the fix.
Nothing published for this version
Nothing published for this version
[#506]: Fixed two XLSX-related issues (sadly, both are regression fixes):
excelize library). These files have varying internal
ZIP structures that the previous detection couldn't handle. Detection now
scans ZIP local file headers instead of relying on fragile magic number
heuristics.--xlsx) being corrupted
when written to stdout. The colorization decorator was modifying the binary
data. XLSX format now bypasses colorization, like --raw output already does.#504: Updated golangci-lint to v2.7.2, along with Go dependencies
and GitHub Actions workflow versions. Other tool versions have been updated too.
Note that Go tool dependencies are now located in the tools/ directory, each
with its own go.mod. Tools are invoked viago tool -modfile, e.g.
go tool -modfile=tools/golangci-lint/go.mod golangci-lint.
See the Makefile and tools/README.md for more detail.
Use `v0.48.10` instead of this release. This release partially failed in the CI pipeline phase.
Use v0.48.10 instead of this release. This release partially failed in the CI pipeline phase.
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#446]: A `bufio.ErrTooLong` was being returned by `bufio.Scanner`, when splitting lines from input that was too long (larger than `bufio.MaxScanToken
#446: A bufio.ErrTooLong was being returned by bufio.Scanner, when splitting lines from input that was too long (larger than bufio.MaxScanTokenSize, i.e. 64KB). This meant that sq wasn't able to parse large JSON files, amongst other problems. The maximum buffer size is now configurable via the new tuning.scan-buffer-limit option. Note that the buffer will start small and grow as needed, up to the limit.
$ sq config set tuning.scan-buffer-limit 64MB # or 1024B, 64KB, 1GB, etc.
A more useful error message is also now returned when the buffer limit is exceeded (the error suggests adjusting tuning.scan-buffer-limit).
tuning.buffer-mem-limit to tuning.buffer-spill-limit. The new name better reflects the purpose of the option.Nothing published for this version
Nothing published for this version
Updated Go dependencies (was failing some security vulnerability scans).
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
[#415]: The JSON ingester could fail due to a bug when a JSON blob landed on the edge of a buffer.
Small bugfix release.
zip was determined to be of kind int, because values 0-1000 were all parseable as integers. But then the 1001st value was BX123, which obviously is not an integer. sq will now see the non-integer value, and alter the ingest DB schema to a compatible kind, e.g. text. This flexibility is powerful, but it does come at the cost of slower ingest speed. But that's a topic for another release.Nothing published for this version
Nothing published for this version
One column per quarter.