v0.3.2

stitch --version now reports the version you actually installed. It was a hand-maintained constant stuck at 0.2.1; it now derives from the installed package metadata, so it can never drift from the release again.

pip install --upgrade stitch-lineage

v0.3.1

Copy and consistency pass over the app's user-facing text, now actually shipped: the strings module changed in #199, and this release carries the rebuilt app so an install shows them. Also fixes the frontend build break that briefly landed on main (#200).

pip install --upgrade stitch-lineage

v0.3.0

The first PyPI release of stitch — dbt ↔ Metabase column lineage, so you know what a column change breaks before you make it.

pip install stitch-lineage

stitch traces a column from its source table through your dbt models into the Metabase fields, cards and dashboards that read it. It reads your dbt artifacts and the Metabase API and writes one plain local file — .stitch/graph.json — which the CLI queries and the browser app draws.

Local-first. No server, no warehouse backend, no hosted anything, and nothing it generates needs to be committed. Metabase is read-only to stitch, with one deliberate exception: stitch mend repairs the cards a schema change broke, and every write is snapshotted, re-executed, and reverted if the card does not run.

In the box:

• stitch build — read dbt artifacts + the Metabase API into the local lineage graph
• stitch serve — the browser app: column-level lineage traces, an interactive ERD (auto-framed layout, hover-highlighted relationships, tables badged by who manages them — dbt, Snowflake, or Metabase), coverage and detail pages
• stitch doctor, stitch suggest, stitch search, stitch mend — health checks, relationship candidates, graph search, card repair

Requires Python 3.11+, a dbt project whose artifacts you can generate, and Metabase 49+ (the first release with API keys).

Alpha, in active development. Full design in SPEC.md; work is tracked as GitHub issues.