From 0319c2e9451d37e01fb369cddad9584232220730 Mon Sep 17 00:00:00 2001 From: Natalie Fiann Date: Mon, 23 Sep 2024 15:22:36 +0100 Subject: [PATCH] Updated breaking changes section --- .../docs/docs/collaborate/govern/model-contracts.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/website/docs/docs/collaborate/govern/model-contracts.md b/website/docs/docs/collaborate/govern/model-contracts.md index e186609b746..700cbab972e 100644 --- a/website/docs/docs/collaborate/govern/model-contracts.md +++ b/website/docs/docs/collaborate/govern/model-contracts.md @@ -206,9 +206,13 @@ At the same time, for models with many columns, we understand that this can mean When comparing to a previous project state, dbt will look for breaking changes that could impact downstream consumers. If breaking changes are detected, dbt will present a contract error. Breaking changes include: -- Removing an existing column -- Changing the `data_type` of an existing column -- Removing or modifying one of the `constraints` on an existing column (dbt v1.6 or higher) +- Removing an existing column. +- Changing the `data_type` of an existing column. +- Removing or modifying one of the `constraints` on an existing column (dbt v1.6 or higher). +- Removing a contracted model constitutes a breaking change. A model is considered 'removed' if it is deleted, renamed, or disabled (by config: enabled): + - if the model is versioned, dbt will throw an error. + - if the model is unversioned, dbt will raise a warning. + More details are available in the [contract reference](/reference/resource-configs/contract#detecting-breaking-changes).