dbt Core: dbt v1.13.0rc1

Source available — automated, not human-reviewed

Component: dbt-core · Channel: prerelease. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-04.

Breaking-change evidence from the source

Breaking Changes - Drop support for Python 3.10, which has reached end-of-life ([#TBD](https://github.com/dbt-labs/dbt-core/issues/TBD))

Read the original context ↗

Source flags breaking changes — review applicability

📄 .MD

🔧 Bug Fixes 6 ⚠️ Breaking & Deprecations 1

⚡ Executive Summary (TL;DR)

dbt Core v1.13.0rc1. Source highlight: dbt-core 1.13.0-rc1 - November 04, 2026

Visit dbt Core Official Site ↗ Official Release Source ↗ All dbt Core Releases 📡 dbt Core RSS

Who Does This Impact? (Role-Based Analysis)

💻 Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

📊 Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

⚙️ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

⚠️ Breaking Changes & Deprecations (1)

Breaking Changes - Drop support for Python 3.10, which has reached end-of-life ([#TBD](https://github.com/dbt-labs/dbt-core/issues/TBD))

🔧 Bug Fixes & Patches (6)

Recognize Databricks Python model config keys (`access_control_list`, `notebook_access_control_list`) in jsonschema validation so they no longer raise spurious `CustomKeyInConfigDeprecation` warnings (dbt-databricks#1661) (#N/A)
Macro namespace resolution no longer lets an internal search_package shadow adapter or root overrides. When search_package is itself an internal package (e.g. dbt or dbt_postgres), the adapter override is now consistently preferred over the base dbt implementation, and a root-project macro always wins. (#16540)
Accept the dbt v2-only `info_schema`, `check-paths` and `checks` keys in dbt_project.yml, ignoring them with a note that they are specific to the dbt v2 engine (#16640)
Ignore manifest nodes with resource types dbt-core doesn't support, such as dbt v2 checks, when loading a manifest for --state and --defer (#16849)
Supply credentials for `dbt deps` git packages through a git credential helper instead of embedding them in the clone URL, so clones of redirecting repositories keep working with libcurl 7.81.0-1ubuntu1.30 and later (#16861)
Recognize Databricks use_materialization_v2 config in JSON schema validation (#16879)

📄 View Raw Release Notes (Original Developer Log)

## dbt-core 1.13.0-rc1 - November 04, 2026 ### Breaking Changes - Drop support for Python 3.10, which has reached end-of-life ([#TBD](https://github.com/dbt-labs/dbt-core/issues/TBD)) ### Fixes - Recognize Databricks Python model config keys (`access_control_list`, `notebook_access_control_list`) in jsonschema validation so they no longer raise spurious `CustomKeyInConfigDeprecation` warnings (dbt-databricks#1661) ([#N/A](https://github.com/dbt-labs/dbt-core/issues/N/A)) - Macro namespace resolution no longer lets an internal search_package shadow adapter or root overrides. When search_package is itself an internal package (e.g. dbt or dbt_postgres), the adapter override is now consistently preferred over the base dbt implementation, and a root-project macro always wins. ([#16540](https://github.com/dbt-labs/dbt-core/issues/16540)) - Accept the dbt v2-only `info_schema`, `check-paths` and `checks` keys in dbt_project.yml, ignoring them with a note that they are specific to the dbt v2 engine ([#16640](https://github.com/dbt-labs/dbt-core/issues/16640)) - Ignore manifest nodes with resource types dbt-core doesn't support, such as dbt v2 checks, when loading a manifest for --state and --defer ([#16849](https://github.com/dbt-labs/dbt-core/issues/16849)) - Supply credentials for `dbt deps` git packages through a git credential helper instead of embedding them in the clone URL, so clones of redirecting repositories keep working with libcurl 7.81.0-1ubuntu1.30 and later ([#16861](https://github.com/dbt-labs/dbt-core/issues/16861)) - Recognize Databricks use_materialization_v2 config in JSON schema validation ([#16879](https://github.com/dbt-labs/dbt-core/issues/16879)) - Fix `dbt deps` failing with "could not read Username" when installing a git package from a `subdirectory` with credentials in the URL, by supplying credentials to the checkout's `git reset --hard` as well ([#16861](https://github.com/dbt-labs/dbt-core/issues/16861)) ### Contributors - [@aahel](https://github.com/aahel) ([#16640](https://github.com/dbt-labs/dbt-core/issues/16640), [#16849](https://github.com/dbt-labs/dbt-core/issues/16849)) - [@ash2shukla](https://github.com/ash2shukla) ([#16861](https://github.com/dbt-labs/dbt-core/issues/16861), [#16861](https://github.com/dbt-labs/dbt-core/issues/16861)) - [@piotrbator2](https://github.com/piotrbator2) ([#16540](https://github.com/dbt-labs/dbt-core/issues/16540)) - [@sd-db](https://github.com/sd-db) ([#N/A](https://github.com/dbt-labs/dbt-core/issues/N/A)) - [@tauhid621](https://github.com/tauhid621) ([#TBD](https://github.com/dbt-labs/dbt-core/issues/TBD), [#16879](https://github.com/dbt-labs/dbt-core/issues/16879))

← Older Version dbt Core v2.0.11

Newer Version → Latest Tracked Version ✓