From 34bb5eec8e64ba0e8925858d331458024999d033 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Tue, 15 Aug 2023 10:00:36 -0400 Subject: [PATCH] adding migration guide link this pr adds the migration guide link to the 1.6 migration guide. Closes #3921 --- .../docs/guides/migration/versions/01-upgrading-to-v1.6.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/guides/migration/versions/01-upgrading-to-v1.6.md b/website/docs/guides/migration/versions/01-upgrading-to-v1.6.md index ea231ce7f9a..d13f3bf2344 100644 --- a/website/docs/guides/migration/versions/01-upgrading-to-v1.6.md +++ b/website/docs/guides/migration/versions/01-upgrading-to-v1.6.md @@ -22,13 +22,13 @@ dbt Labs is committed to providing backward compatibility for all versions 1.x, ### Behavior changes - 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 Semantic layer re-launch (in beta), the spec for `metrics` has changed significantly. Migration guide coming soon: https://github.com/dbt-labs/docs.getdbt.com/pull/3705 +- 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. - dbt Labs is ending support for Homebrew installation of dbt-core and adapters. See [the discussion](https://github.com/dbt-labs/dbt-core/discussions/8277) for more details. ### For consumers of dbt artifacts (metadata) -The [manifest](/reference/artifacts/manifest-json) schema version has updated to `v10`. Specific changes: +The [manifest](/reference/artifacts/manifest-json) schema version has been updated to `v10`. Specific changes: - Addition of `semantic_models` and changes to `metrics` attributes - Addition of `deprecation_date` as a model property - Addition of `on_configuration_change` as default node configuration (to support materialized views)