dbt Core
Analytics engineering framework for transforming data in the warehouse
dbt 2.0 dev.44 adds ClickHouse clusters, grants and clone ahead of the next v2 release.
◆Recent moves
- 2d ago
dbt 1.12.7 fixes source freshness and cache-selected-only
A 1.12 patch: source freshness falls back to per-source checks when batch metadata fails, --cache-selected-only now works for compile, show and docs, and state:modified stops flagging list and dict configs by mistake. Maintenance on the 1.x bridge while new capability lands on the v2 dev channel.
View source ↗ - 2d ago
dbt 2.0 dev.44 adds ClickHouse clusters, grants and clone
The v2 dev channel brings ClickHouse closer to parity with the main warehouses: cluster support, distributed materializations, grants and clone. Lake Compute's Databricks reach also widens, continuing the work on reading other warehouses' tables from v2.
View source ↗ - 8d ago
dbt 1.11.17 fixes git package installs under new libcurl
1.11.17 supplies git credentials through a credential helper rather than the clone URL, fixing dbt deps on redirecting repos with newer Ubuntu libcurl, and recognizes dbt State configs on snapshots and tests. Upkeep on an older line while 1.13 heads to GA.
View source ↗ - 9d ago
dbt-core 1.13 RC drops Python 3.10, accepts v2-only config
The 1.13 release candidate drops Python 3.10 and lets 1.x projects carry v2-only dbt_project.yml keys and v2 check nodes without errors. It also fixes git-package credentials in dbt deps. Most of it exists so teams can run v1 and v2 against the same project during migration.
View source ↗ - 1mo 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 ↗ - 1mo 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 ↗