From 02b4376a3d603e4d6aefa9216d7086bdddbfc0fa Mon Sep 17 00:00:00 2001 From: Jeremy Cohen Date: Wed, 13 Apr 2022 16:53:36 +0200 Subject: [PATCH] Add note to v1.1 migration guide --- website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md b/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md index fa3f3320ef5..1f577af5609 100644 --- a/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md +++ b/website/docs/docs/guides/migration-guide/upgrading-to-v1.1.md @@ -36,6 +36,7 @@ _Note: If you're contributing docs for a new or updated feature in v1.1, please - [**Incremental models**](configuring-incremental-models) can now accept a list of multiple columns as their `unique_key`, for models that need a combination of columns to uniquely identify each row. This is supported by the most common data warehouses, for incremental strategies that make use of the `unique_key` config (`merge` and `delete+insert`). - [**Generic tests**](resource-properties/tests) can define custom names. This is useful to "prettify" the synthetic name that dbt applies automatically. It's needed to disambiguate the case when the same generic test is defined multiple times with different configurations. +- [Python compatibility](install-python-compatibility): dbt Core officially supports Python 3.10 ### For users of specific adapter plugins