Skip to content

v0.1.8 — live Fivetran status & a Python-version guardrail

Released: 2026-05-30

A small, focused release between the layered-architecture work of v0.1.7 and the Quack-headlined cycle still in flight. Two things land: tycoon data status now reads Fivetran live (with a write-through cache), and the package gains a Python-version ceiling so a too-new interpreter can't silently break dbt.

The larger v0.1.8 cycle plan — Quack multi-client DuckDB, DuckLake cloud-bucket backup, and operate-in-prod ergonomics — is tracked in docs/proposals/v0.1.8-scope.md and continues toward a later cut.

Live Fivetran read in data status (#50)

tycoon data status previously rendered the Fivetran Sources panel from the most recent tycoon data fivetran sync snapshot, so freshness was bounded by whenever you last ran sync — and stale data showed without warning. As of v0.1.8, data status makes a live list_connectors() call on every run and writes the result through to .tycoon/metadata.duckdb (the cache now populates as a side effect of viewing status). If the API is unreachable — incomplete credentials, auth failure, network down, 5xx — it falls back to the last cached snapshot with a clear warning and stays non-fatal. tycoon data fivetran sync remains the cron-friendly bulk-populate command for unattended runs.

This closes the design Q3 deviation noted at the v0.1.7 close.

Fixed: requires-python ceiling (#55)

pyproject.toml declared requires-python = ">=3.12" with no upper bound. On a machine whose default interpreter is Python 3.14, the environment resolved to 3.14 — where dbt-core 1.11.8 / dbt-duckdb 1.10.1 have no support yet, so tycoon data transform run failed. v0.1.8 caps the range at >=3.12,<3.14 and re-locks so a supported interpreter is chosen by default (uv selects or fetches a compatible 3.12/3.13). If you hit this on an older build, the workaround is uv sync --python 3.12. The ceiling lifts once dbt ships 3.14 wheels.

What's next

The Quack headline and the backup / notification / scheduling tracks remain open in the v0.1.8 milestone and roll forward — see the scope proposal for live track status.