deps: duckdb 1.4.4 cannot attach migrated DuckLake catalog — align project pin with 1.5.x #633
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found during P39 recon:
connect.ducklake()fails from the host project venv and the api container (both duckdb 1.4.4 via uv.lock) withOnly DuckLake versions 0.1, 0.2, 0.3-dev1 and 0.3 are supported— the catalog metadata has been migrated to a newer DuckLake version, presumably by the notebooks workspace venv (duckdb 1.5.4), which attaches fine.Impact today: dormant — ingest targets the monolith, lake publish + notebooks run in the notebooks container, api does not use ducklake. But any host-side lake read (the documented
connect.ducklake()dev path) is dead.Fix: bump project duckdb floor to ≥1.5.4,
uv lock, full test suite; verify the 1.4.4-writtenaco.duckdbmonolith opens under 1.5.4 (read and write path via duckdb_batch preflight). If tests object, defer with findings here rather than forcing — nothing in P39's critical path needs it.Spec: docs/superpowers/specs/2026-08-17-cy2027-notebook-gpci-pqm-design.md (D4).