dbt Core Release Notes

• New: The dbt Remote dbt MCP server now supports Admin API calls! This allows users to troubleshoot job-related errors in agents like Claude and Cursor.

• New: The Developer agent is now in beta. Use the Developer agent to write or refactor dbt models from natural language, generate documentation, tests, semantic models, and SQL code from scratch, giving you the flexibility to modify or fix generated code. For more information, refer to the Developer agent.

• Enhancement: The Studio IDE now validates dbt YAML using Fusion aligned JSON Schema from dbt-jsonschema across dbt platform release tracks, including for development environments on dbt Core. This improves autocomplete and structural feedback in the editor. Diagnostics can occasionally disagree with what your environment accepts; use dbt runs and previews as the source of truth. For context, review Migrate to the latest YAML spec and dbt YAML validation in Studio. This will be a phased rollout starting the week of April 6th.

• Enhancement: The Studio IDE status bar now offers more control, more detailed information, and quicker access to settings for deferral, dbt version, and project status. For more information, refer to the Studio IDE docs. These updates roll out in phases to existing accounts starting April 6.

• Enhancement: In Snowflake Private endpoints, output validation errors now display inline beneath the text area (instead of as a page-level banner). The Submit request button is also disabled when the output is invalid (for example, empty, malformed JSON, or missing required fields).

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_ENGINE prefixed 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

• @ChenyuLInx (#486)
• @QMalcolm (#12583)
• @aahel (#574)
• @aranke (#506, #513)
• @ash2shukla (#12371, #12383, #9447, #12080, #12600, #12542, #12327)
• @gshank (#501)
• @kalluripradeep (#12353, #12572)
• @michelleark (#12694, #554, #12329)
• @rrittsteiger (#12662)

Enhancement

The environment Connection profiles page has been updated. The profile name is now a clickable button that opens the view/edit drawer, the Connection column links to the connection details page in a new tab, and in edit mode a swap icon button lets you change the assigned profile. The previous ellipsis menu has been removed. For details, refer to About profiles.

The Model Timing tab displays an informative banner for dbt Fusion engine runs instead of the timing chart. The banner explains "Model timing is not yet available for Fusion runs" and provides context about threading differences. Non-Fusion runs continue to show the timing chart normally.

Beta

Apache Spark is now supported in the dbt Fusion engine CLI, enabling faster compilation and execution for Spark-based dbt projects. Fusion currently supports only Apache Spark 3.0. For more information, refer to Connect Apache Spark to Fusion.

Enhancement

Cost Insights charts now include an Assets filter (Models / Tests / All) on the Cost, Usage, Query run time, and Builds tabs. Use the dropdown on each chart to filter the data you want to view; your selection is stored per tab. The former Model builds tab is now labeled Builds. For more information, refer to Explore cost data.

Deferral now supports user-defined functions (UDFs). When you run a dbt command with --defer and --state, dbt resolves function() calls from the state manifest. This lets you run models that depend on UDFs without first building those UDFs in your current target.

Fix

Status messages that exceed the 1024 character limit are now automatically truncated to prevent validation errors and run timeouts. Previously, long status messages could cause runs to fail with unhandled exceptions or result in lost status information. The system now logs when truncation occurs to help identify and optimize verbose status messages.

Resolved an issue where retrying failed runs that were triggered from Git tags would use the wrong commit. Previously, when runs were triggered from Git tags instead of branches, the system would enter a detached HEAD state, causing retries to use the latest commit on HEAD rather than the original tagged commit. The fix now correctly preserves and uses the original Git tag reference when retrying runs, ensuring consistency between the initial run and any retries.

New

The dbt MCP server now includes product docs tools (search_product_docs and get_product_doc_pages) that let your AI assistant search and fetch pages from docs.getdbt.com in real time. Get responses grounded in the latest official dbt documentation rather than relying on training data or web searches, so you can stay in your development flow and trust the answers. This allows you to stay in your development flow and trust. These tools are enabled by default with no additional configuration. Restart your MCP server if you don't see the product docs tools in your MCP config. For more information, refer to the dbt MCP repo.

The new Semantic Layer YAML specification is now available on the dbt platform Latest release track. For an overview of the changes and steps how to migrate to the latest YAML spec, refer to Migrate to the latest YAML spec.

Behavior change

Snowflake plans to increase the default column size for string and binary data types in May 2026. dbt-snowflake versions below v1.10.6 may fail to build certain incremental models when this change is deployed. Assess impact and take any required actions.

New projects in trial, starter, or Enterprise accounts now default to Fusion Latest for all new environments with a supported adapter (Redshift, Snowflake, BigQuery, and Databricks). You can revert to another version by changing the dbt version in your environment settings.

New

• New: Advanced CI (dbt compare in orchestration) is now supported in the dbt Fusion engine. For more information, review Advanced CI.
• Beta: The dbt-salesforce adapter available in the dbt Fusion engine CLI is now in beta. For more information, refer to Salesforce Data 360 setup.
• Enhancement: The Analyst permission now has the project-level access to read repositories. Review Project access for project permissions for more information.
• Enhancement: After a user accepts an email invite to access an SSO-protected dbt platform account, the UI now prompts them to log in with SSO to complete the process. This replaces the previous "Joined successfully" message, helping avoid confusion when users accept an invite but do not complete the SSO login flow.
• New: Profiles let you define and manage connections, credentials, and attributes for deployment environments at the project level. dbt automatically creates profiles for existing projects and environments based on the current configurations, so you don't need to take any action. This is being rolled out in phases during the coming weeks.
• New: Python UDFs are now supported and available in dbt Fusion engine when using Snowflake or BigQuery.
• Enhancement: Minor enhancements and UI updates to the Studio IDE, file explorer that replicate the VS Code IDE experience.
• Enhancement: Profile creation now displays specific validation error messages (such as "Profile keys cannot contain spaces or special characters") instead of generic error text, making it easier to identify and fix configuration issues.
• Private beta: Cost Insights shows estimated warehouse compute costs and run times for your dbt projects and models, directly in the dbt platform. It highlights cost reductions and efficiency gains from optimizations like state-aware orchestration across your project dashboard, model pages, and job details. Refer to Set up Cost Insights and Explore cost data to learn more.
• New: The dbt Semantic Layer now supports Omni as a partner integration. For more information, refer to Available integrations.
• Enhancement: We clarified documentation for cumulative log size limits on run endpoints, originally introduced in October 2025. When logs exceed the cumulative size limit, dbt omits them and displays a banner. No functional changes were made in February 2026. For more information, review Run visibility.
• New: The immutable_where configuration is now supported for Snowflake dynamic tables. For more information, refer to Snowflake configurations.
• Fix: The user invite details now show more information in invite status, giving admins visibility into users who accepted an invite to an SSO-protected account but haven't yet logged in via SSO. Previously, these invites were hidden, making it appear as if the user hadn't been invited. The Invites endpoints of the dbt platform Admin v2 API now include these additional statuses:
  • 4 (PENDINGEMAIL_VERIFICATION)
  • 5 (EMAIL_VERIFIED_SSO).
• Enhancement: Improved performance on Runs endpoint for Admin V2 API and run details in dbt platform when connecting with GCP.