Skip to content

Commit

Permalink
Update 01-upgrading-to-v1.6.md (#3386)
Browse files Browse the repository at this point in the history
adding SL doc placeholder for 1.6 beta launch

Resolves #3385

Resolves #3503
  • Loading branch information
matthewshaver authored Aug 23, 2023
2 parents eab12de + 7cb2aac commit 7133ad6
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions website/docs/guides/migration/versions/01-upgrading-to-v1.6.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,14 @@ dbt Labs is committed to providing backward compatibility for all versions 1.x,

### Behavior changes

:::info Action required if your project defines `metrics`

The [spec for metrics](https://github.com/dbt-labs/dbt-core/discussions/7456) has changed and now uses [MetricFlow](/docs/build/about-metricflow).

:::

If your dbt project defines metrics, you must migrate to dbt v1.6 because the YAML spec has moved from dbt_metrics to MetricFlow. Any tests you have won't compile on v1.5 or older.

- dbt Core v1.6 does not support Python 3.7, which reached End Of Life on June 23. Support Python versions are 3.8, 3.9, 3.10, and 3.11.
- As part of the [dbt Semantic layer](/docs/use-dbt-semantic-layer/dbt-sl) re-launch (in beta), the spec for `metrics` has changed significantly. Refer to the [migration guide](/guides/migration/sl-migration) for more info on how to migrate to the re-launched dbt Semantic Layer.
- The manifest schema version is now v10.
Expand All @@ -41,6 +49,10 @@ For more detailed information and to ask questions, please read and comment on t

## New and changed documentation

### MetricFlow

- [**Build your metrics**](/docs/build/build-metrics-intro) with MetricFlow, a key component of the dbt Semantic Layer. You can define your metrics and build semantic models with MetricFlow, available on the command line (CLI) for dbt Core v1.6 beta or higher.

### Materialized views

Supported on:
Expand Down Expand Up @@ -78,3 +90,4 @@ More consistency and flexibility around packages. Resources defined in a package
- [`dbt debug --connection`](/reference/commands/debug) to test just the data platform connection specified in a profile
- [`dbt docs generate --empty-catalog`](/reference/commands/cmd-docs) to skip catalog population while generating docs
- [`--defer-state`](/reference/node-selection/defer) enables more-granular control

0 comments on commit 7133ad6

Please sign in to comment.