Repository navigation
v1.17.1 — the DuckDB extension loads into DuckDB 2.0
mentat 1.17.1: the DuckDB extension loads into DuckDB 2.0
Changed
-
One DuckDB extension binary works with DuckDB v1.5.6 and 2.0. The
extension now uses DuckDB's stable C API, with v1.5.6 as the minimum
version. Up to 1.17.0 it was locked to exactly v1.5.6, and DuckDB 2.0
refused to load it:The file was built specifically for DuckDB version 'v1.5.6' and can only be loaded with that version of DuckDB. (this version of DuckDB is 'v2.0.0')The DuckDB Community Extensions registry builds with DuckDB 2.0 now, so
this is what letsINSTALL mentat FROM communitywork for 2.0 users. A
DuckDB patch release also no longer needs a new mentat release.Tested on one binary: the smoke test under the v1.5.6 CLI and a 2.0 CLI
built at the registry's DuckDB commit (d54cbbe3, which reports itself as
v2.0.0), plus the SQLLogicTest suite and the concurrency test under the
duckdb Python packages 1.5.6 and 2.0.0.dev2610192346. The DuckDB
extension's code did not change.
Security
- Cargo.lock updates rustls-webpki to 0.103.16
(RUSTSEC-2026-0382)
and webpki-roots to 1.0.10
(RUSTSEC-2026-0381).
Both are used only by duckdb-rs's downloader at build time and are not in
any shipped binary.
PostgreSQL, SQLite, library
No change. ALTER EXTENSION pg_mentat UPDATE is a no-op step from 1.17.0.
The asset mentat-duckdb-v1.5.6-linux_amd64.tar.gz keeps its name; v1.5.6
is the minimum DuckDB version now, not the only one.