Bare wildcard FQN selectors like -s "f_*" now match nested models regardless of subfolder depth, and the v2 parser's log output relays via --log-format otel, fixing a latent bug where a stray stderr line could abort runs under --warn-error. Also fixed cumulative metrics parsing, compiled_code persistence to manifest.json with --use-v2-parser, and tarball download path validation.
dbt-core
npx @buildinternet/releases get dbt-coreBare wildcard FQN selectors like -s "f_*" now match nested models regardless of subfolder depth. Also validates that tarball package download locations stay within the dbt downloads directory, and includes semantic_manifest.json in artifacts uploaded by --upload-to-artifacts-ingest-api.
dbt build --write-catalog writes catalog.json again; since 2.0.0-preview.218 the implied index default overrode the explicit flag and silently skipped the catalog. Also fixed spurious TableNotFound errors during analyze and lowered the minimum Python version for the dbt and dbt-oss PyPI wheels to 3.10.
Flags introduced in dbt 1.9 and 1.10 now default to true, and a new dbt login command handles platform authentication. The release also bundles the opt-in dbt-state plugin, adds a --use-v2-parser flag that delegates parsing to the Fusion parser, and ships numerous parser fixes including a duplicate-metric partial-parsing error and a circular-selector recursion crash on Windows.
Lake Compute can now read AWS Databricks Unity Catalog tables using Databricks profile PAT or OAuth M2M credentials, with declaration-aware validation and dbt debug attach parity. Fixed modules.re functions silently dropping keyword arguments like flags, maxsplit, and count, plus Databricks tag diffs that emitted unchanged columns and keys.
Both Legacy and Foundry BigQuery drivers now continue on ADBC.GetObjects 404/403 responses, fixing a case where incremental tables could be written with REPLACE TABLE instead of MERGE.
Added a PyPI banner for the dbt-oss package mirroring the existing dbt-core banner, without the dbt-core namespace deprecation notice.
Fixed Dimension to satisfy the metricflow-semantic-interfaces protocol and bumped the metricflow floor to 0.213.0. Also added a PyPI description banner pointing users to the v2 install docs.
2.0.2
Released September 15, 2026
dbt v2 CLI branding is renamed from Fusion/dbt-core to dbt (proprietary) and dbt-oss (OSS), changing --version/--help output and several Fusion-branded warning and error messages. Also adds agent skills installation from installed packages and project skill-paths gated on the new ai_provider flag, native Databricks metric view materializations, and a new adbc_clickhouse driver.
Installs agent skills (AgentSkills-format SKILL.md directories) from installed packages and the project's own skill-paths when packages are installed, gated on the new ai_provider flag. Also adds native Databricks metric view materializations and an adbc_clickhouse driver with connection-level settings, and renames v2 CLI branding from Fusion/dbt-core to dbt (proprietary) and dbt-oss (OSS).
2.0.0-dev.39
ClickHouse now supports connection-level settings — profile custom_settings, v1-parity synchronous-operation defaults, default database wired to the profile schema, literal '?' in SQL, and dbt identified as dbt/<version> in the HTTP User-Agent — via the new adbc_clickhouse driver.
Adds a new adbc_clickhouse driver for ClickHouse, which now configures connection-level settings, defaults the database to the profile schema, supports literal '?' in SQL, and identifies dbt as dbt/<version> in the HTTP User-Agent.
2.0.0-dev.38
The ClickHouse adapter now supports connection-level settings via profile custom_settings, wires the default database to the profile schema, handles literal '?' in SQL, and identifies dbt as dbt/ in the HTTP User-Agent, all through the new adbc_clickhouse driver.
2.0.0-dev.37
ClickHouse adapters now support dbt unit tests and expanded materialized view functionality, including on_schema_change and refresh-schedule updates. Databricks views respect full refresh when view_update_via_alter is enabled, and materialized view query changes trigger a required full refresh.
