[kvlonge]

Why

DuckDB 1.5.0 through 1.5.4 raise an internal binder error ("Failed to bind column reference") for some queries with repeated window functions over a GROUP BY, for example SELECT MAX(amount) OVER (PARTITION BY id) AS a, MAX(amount) OVER (PARTITION BY id) AS b FROM (SELECT 1 AS id, 1 AS amount) GROUP BY id, amount. The lockfile pinned 1.5.2, so development and CI ran an affected version.

Changes

• Lockfile: duckdb 1.5.2 to 1.5.5. The supported range in pyproject.toml is unchanged.
• Not 1.5.6: it raises a new internal cast error for some QUALIFY queries (two column-rename integration tests).
• The ingestr DuckDB ADBC driver follows the installed duckdb version, so it moves to 1.5.5 as well.

Verification

• The query above runs on 1.5.5 and fails on 1.5.2.
• dbc install duckdb=1.5.5 installs the matching ADBC driver.
• make check-ci; CI runs the DuckDB E2E suites.