LoginSign Up
← Back to all sparks
D

dbt Core

ANALYTICS
Velocity6.3

Analytics engineering framework for transforming data in the warehouse

www.getdbt.com ↗

dbt's 1.x releases now point users at v2 straight from the command line.

fusion-migrationv2-transitionsemantic-layeradapterscli
◆Current state
dbt 2.0 GA split the project into a proprietary 'dbt' binary and dbt-oss, and the 2.0 dev channel has since added read-only Databricks Unity Catalog access through Lake Compute. The 1.x line is still shipping: 1.13.0b1 adds an opt-in --use-v2-parser that hands parsing to the Fusion parser, and today's 1.12.6 prints a v2 availability notice on dbt --version and relays Fusion parser logs through the otel log format.
◆Where it's heading
The 1.x branch is being turned into an on-ramp for v2: a PyPI banner in 1.12.5, a CLI notice in 1.12.6, deprecated-version warnings and the Fusion parser opt-in in 1.13. Meanwhile 2.0 work concentrates on adapter parity (ClickHouse, Databricks) and Lake Compute.
◆Prediction
Expect 1.13 to reach GA with the v2 parser opt-in and more migration prompts, and 2.0.x to extend Lake Compute past read-only Unity access. The entries don't show an end-of-life date for 1.x.

◆Recent moves

  1. 15d ago

    dbt 1.12.6 points users to v2 and fixes Fusion parser logging

    1.12.6 is the clearest example of 1.x acting as a funnel to v2: dbt --version now announces v2 with an install link. It also cleans up how Fusion parser output is relayed, so a stray stderr line no longer aborts runs under --warn-error, and fixes nested wildcard selectors and v2 cumulative-metric parsing.

    View source ↗
  2. 15d ago

    dbt 1.11.16 fixes nested wildcard selectors, adds tarball path check

    A maintenance patch on the 1.11 line: bare wildcard FQN selectors now match nested models, semantic_manifest.json joins the uploaded artifacts, and tarball package downloads are checked against path escape. The path validation is the part that matters, a supply-chain hardening for teams still pinned to 1.11 while 2.0 and 1.13 take the new work.

    View source ↗
  3. 15d ago

    dbt-core 1.13 beta adds opt-in Fusion parser and dbt login

    The first 1.13 beta turns dbt-core into a bridge to v2: --use-v2-parser delegates parsing to the Fusion parser, the dbt-state plugin ships bundled but opt-in, dbt login appears, and 1.9/1.10 behavior flags now default to true, which is a breaking change. It also adds OpenTelemetry trace hooks and a v2 notice on dbt --version. Everything new is behind flags, so this is a migration path rather than a direction change on its own.

    View source ↗
  4. 1mo ago

    Lake Compute gains Databricks Unity Catalog read access

    A dev-channel build adds Databricks Unity Catalog read access via Lake Compute, using PAT/OAuth M2M credentials and declaration-aware validation. This is the first post-2.0 expansion of the Lake Compute surface — read-only for now — following directly from the v2.0 GA that introduced the capability. Bug fixes address silent keyword-argument drops and Databricks column-tag diff noise.

    View source ↗
  5. 1mo ago

    dbt v2.0.0

    ⚡ SPARK

    dbt 2.0.0 GA ('Benjamin Franklin') is the release the 2.x cycle has been building toward: proprietary/OSS branding now formalized, agent skills shipped, Databricks metric views supported natively. This marks the end of the Fusion-branded period and the start of a dual-product reality.

    View source ↗
  6. 1mo ago

    dbt v1.12.5

    A patch release on the 1.x maintenance track: fixes a Dimension protocol conformance issue and bumps the metricflow floor to 0.213.0. Adds a PyPI banner pointing users to v2 install docs — housekeeping for the 1.x end-of-life transition.

    View source ↗