kert 9cba4fdb3a fix(notebooks): keep the unlocked workspace on duckdb 1.x like the rest of the stack ...

The notebooks image resolves its workspace at build time with no lock,
so a rebuild after 2026-10-21 would pull duckdb 2.0.0 while api, llm,
bcda and every pipeline run the locked 1.5.x against the same .duckdb
files. Cap it at <2 until the stack moves engines together (a Renovate
major on uv.lock).

2026-10-27 13:24:14 -04:00

5.5 KiB

Raw Blame History

View Raw