dbt-core v1.12.0rc2
Release candidate 1.12.0 includes breaking changes for flags from 1.9 and 1.10 now defaulting to true, new catalog_database field for CatalogWriteIntegrationConfig to support database-name overrides, and fixes for config rendering and partial parsing ghost-duplicates.
dbt-core 1.12.0-rc2 - July 09, 2026
Breaking Changes
- Flags introduced in 1.9 and 1.10 defaults to true (#12713)
Features
- Add catalog_database field to CatalogWriteIntegrationConfig (v1) so catalogs.yml can set a database-name override for any catalog type; works in conjunction with the dbt-adapters get_catalog_database_override method to give catalog_database highest priority in generate_database_name (#15156)
Fixes
- Reconstruct unrendered config kwarg values as readable expressions instead of raw AST repr (#15336)
- 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 (#)
Contributors
- @MichelleArk (#15336)
- @aahel (#15156)
- @itsnamangoyal (#12713, #)
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.