dbt-core v1.11.13
Release includes a deprecation warning for older dbt versions, fixes for unit testing with versioned models and partial parsing issues, and dependency updates for Docker builds. Key improvements address non-deterministic filesystem parse order problems in model and test resolution.
dbt-core 1.11.13 - August 12, 2026
Features
- Warn users if they are using a deprecated dbt version (#15964)
Fixes
- Fix intermittent "references a model that does not exist" parsing error when unit testing versioned models, caused by non-deterministic filesystem parse order (#11139)
- Fix partial parsing ghost-duplicate that raised a false "found two data_tests" error by cleaning up disabled generic and singular test nodes on schema re-parse (#)
- Stop resolving a unit test's tested model eagerly at parse time; resolve it only in the single deterministic post-parse pass so resolution no longer depends on filesystem parse order at all (deeper fix for (#11139)
Dependencies
- Bump ca-certificates, libpq-dev, and openssh-client in Docker image to current bullseye versions to fix Docker release build failure caused by superseded package versions (#NA)
Contributors
- @ajnovice (#NA)
- @ash2shukla (#15964)
- @itsnamangoyal (#11139, #, #11139)
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.