dbt-core v1.11.8
This patch release includes fixes for REST catalog compilation, deferral for UDFs, dbt-docs improvements for unit tests and Saved Query nodes, and various configuration and deprecation handling improvements.
dbt-core 1.11.8 - April 08, 2026
Fixes
- Add @requires.catalogs decorator to compile command to fix REST Catalog-Linked database compilation (#12353)
- Improve logic for detecting config with missing plus prefix in dbt_project.yml (#12371)
- Add config and allow meta and docs to exist under it for macros (#12383, #9447)
DBT_ENGINEprefixed env vars picked up by CLI (#12583)- Allow deferral for UDFs (#12080)
- Resolve full node description while running udfs for better logging (#12600)
- Raise PropertyMovedToConfigDeprecation instead of MissingArgumentsPropertyInGenericTestDeprecation (#12572)
- Add @requires.catalogs decorator to test command to fix custom catalog integration support (#12662)
- Raise custom key in config deprecation warning for invalid config keys in dbt_project.yml (#12542)
- Ensure MAX_GROUPING_TOKENS and MAX_GROUPING_DEPTH default to None independently (#12694)
- Ensure property depr checks check for aliases with plus prefix (#12327)
Docs
- Enable display of unit tests (dbt-docs/#501)
- Unit tests not rendering (dbt-docs/#506)
- Add support for Saved Query node (dbt-docs/#486)
- Fix npm security vulnerabilities as of June 2024 (dbt-docs/#513)
- Bump form-data from 3.0.1 to 3.0.4 (dbt-docs/#554)
- Add support for UDF (function) resource type in lineage graph (dbt-docs/#574)
Under the Hood
- Unpin sqlparse dependency, and introduce --sqlparse CLI option for configuring sqlparse limits (#12329)
Contributors
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.