Skip to main content

Trying out v1.3 (beta)


Breaking changes​

There are no breaking changes for code in dbt projects and packages. We are committed to providing backwards compatibility for all versions 1.x. If you encounter an error upon upgrading, please let us know by opening an issue.

For consumers of dbt artifacts (metadata)​

The manifest schema version will be updated to v7 to reflect three changes associated with Python models:

  • Renamed raw_sql to raw_code
  • Renamed compiled_sql to compiled_code
  • A new top-level node property, language ('sql' or 'python')

For users of state-based selection: This release includes logic providing backward and forward compatibility for older manifest versions. While running dbt Core v1.3, it should be possible to use state:modified --state ... selection against a manifest produced by dbt Core v1.0 and higher.

For users of dbt Metrics​

The metric spec used to define metrics in dbt has been changed. Those changes are:

  • Renamed type to calculation_method
  • Renamed sql to expression
  • Renamed expression calculation method metrics to derived calculation method metrics

These changes will be backwards compatible for a full minor version - support for them will be deprecated in v1.4.0 of dbt-core.

For maintainers of adapter plugins​

GitHub discussion forthcoming


  • The statement and create_table_as macros accept a new argument, language, with a default value of 'sql'

New and changed documentation​

  • Python models are natively supported in dbt-core for the first time, on data warehouses that support Python runtimes.

  • Updates made to Metrics reflect their new syntax for definition, as well as additional properties that are now available.

Docs in progress: Issues labeled "dbt-core v1.3"