Cut minor release with DuckDB 2.0 support (target Q4 2026)

[db-tycoon-stephen]

Summary

DuckDB 2.0 is reportedly targeted for Q4 2026. Tycoon currently pins duckdb==1.5.2, so we'll need a coordinated minor release to move to the 2.0 line when it ships.

Current pins (pyproject.toml)

• duckdb==1.5.2
• dbt-duckdb==1.10.1
• dlt[duckdb]==1.26.0

A DuckDB 2.0 bump is rarely a standalone change — dbt-duckdb and dlt's DuckDB extra will need matching compatible releases, and any storage-format changes in DuckDB 2.0 may require migration handling for existing project catalogs.

Tracking scope

• Watch DuckDB 2.0 release notes for breaking changes (SQL surface, storage format, extension API)
• Confirm dbt-duckdb 2.0-compatible release lands; pin floor accordingly
• Confirm dlt[duckdb] 2.0-compatible release lands; pin floor accordingly
• Audit our DuckDB usage for any deprecated APIs flagged in 1.x → 2.0 migration guide
• On-disk migration story: do existing *.duckdb files in user projects need conversion? If yes, surface via tycoon doctor / migration command
• Cut a minor release (v0.2.0 or whichever number lines up) once all the above is green
• CHANGELOG + docs/releases/v<x>.md narrative per the standard release flow

Open questions

• Q4 2026 is a rumor — track upstream announcements before committing to a calendar release date
• Does the Quack protocol (#42) land in DuckDB 2.0 GA, or stay nightly? If GA, that simplifies its integration story.

Out of scope

• Pre-2.0 speculative refactoring. Wait for actual release notes before changing code.

[db-tycoon-stephen]

Mirrored in Jira for roadmap tracking: PTC-16 (Epic: PTC-4 (Engine upgrades)). Dev work continues here; the Jira issue exists so PRs/commits referencing PTC-16 show up on the Releases roadmap.