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 v1.12.6
dbt v1.12.6 includes improved v2 parser logging, fixes for wildcard FQN selectors, cumulative metrics parsing, and manifest persistence. Several bug fixes address parser output handling, nested model matching, and artifact uploads.
dbt v1.11.16
This patch release fixes wildcard FQN selectors to match nested models at any subfolder depth, includes semantic_manifest.json in artifact uploads, and validates tarball package download security.
v2.0.8
dbt 2.0.8 lowers the minimum Python version to 3.10, fixes TableNotFound errors during analyze operations on MapReduce, restores catalog.json writing for dbt build, and adds test helpers for integration testing.