dbt-core v1.12.0b3
This beta release includes fixes for OSI documents directory configuration, support for lowercase "osi" directories, a new direct_parents attribute for model nodes to improve DAG rendering, and a quoting/case-aware collision check for latest_version aliases. The manifest contract remains unchanged.
dbt-core 1.12.0-b3 - June 15, 2026
Fixes
- Allow for setting of OSI documents directory as project config (#13088)
- Support lowercase "osi" directory (#13087)
- Add a
direct_parentsattribute to model nodes carrying the nearest public ancestors only, and emit it indbt ls --output=jsonfor models. Lineage consumers can now render DAG edges fromdirect_parentsinstead ofdepends_on.nodes, which carries the full transitive closure across plugin boundaries (still required for node selection and cycle detection). The new attribute is runtime-only and is stripped during manifest serialization, so the manifest.json contract is unchanged. (#) - Make the latest_version_pointer collision check quoting/case aware so an unquoted latest-version alias differing from the pointer name only by case is correctly detected on case-insensitive warehouses (#15210)
Under the Hood
- sync JSON schemas from dbt-fusion (#N/A)
Contributors
- @QMalcolm (#13088, #13087)
- @aahel (#15210)
- @fa-assistant (#N/A)
- @sriramr98 (#)
Source: original entry ↗
More from dbt
Follow dbt to get its new changes in your feed and email digest.
dbt 2.0.0-dev.41
Added Lake Compute support for reading AWS Databricks Unity Catalog tables with PAT/OAuth M2M credentials. Fixed multiple issues including modules.re keyword argument handling, column-tag diffs in Databricks, and test config inheritance from dbt-core.
BigQuery drivers continue on ADBC.GetObjects errors
Fixed an issue where BigQuery drivers would fail on ADBC.GetObjects 404/403 errors, which was causing incorrect use of REPLACE TABLE instead of MERGE for incremental tables. The drivers now continue gracefully when encountering these errors.