Deprecation & warnings overview

When using dbt, you may see warnings or other changes that need your attention. These changes help us move forward with the latest version of dbt and improve the experience for all users.

Use this page to understand the different types of changes, what to do, and where to find more information.

Deprecations

Features in your project code (models, YAML, macros) that still work but will be removed.

Impact: Currently warnings; will cause errors in future versions.

Action: Update your project code to use the new syntax.

Behavior change flags

Settings in your dbt_project.yml file that let you opt in or out of new behaviors during migration periods.

Impact: Controls whether dbt uses old or new behavior; defaults change over time.

Action: Set flags to control timing of adoption.

Deprecated CLI flags

Command-line flags passed to dbt commands that are being removed in Fusion.

Impact: Some ignored (with warnings); --models flag will error in Fusion.

Action: Update job definitions and scripts to remove or replace these flags.

Preparing for Fusion

If you're upgrading to Fusion, you should:

• Resolve all deprecations to avoid causing errors in Fusion.
• Review behavior change flags to understand how Fusion will behave (new behavior is always enabled).
• Update deprecated CLI flags to avoid errors in Fusion.

Related docs

• Full deprecations list
• Behavior change flags
• Upgrading to Fusion
• Fusion readiness checklist
• Events and logging

Was this page helpful?

Privacy policyCreate a GitHub issue

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.