From e09a594bdde908842b9e33852081971d42cbe600 Mon Sep 17 00:00:00 2001
From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com>
Date: Wed, 10 Jan 2024 12:43:33 +0000
Subject: [PATCH] Update constraints.md

remove callout
---
 website/docs/reference/resource-properties/constraints.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/docs/reference/resource-properties/constraints.md b/website/docs/reference/resource-properties/constraints.md
index 841307c4025..5ec12b100d7 100644
--- a/website/docs/reference/resource-properties/constraints.md
+++ b/website/docs/reference/resource-properties/constraints.md
@@ -3,10 +3,6 @@ resource_types: [models]
 datatype: "{dictionary}"
 ---
 
-:::info New functionality
-This functionality is new in v1.5.
-:::
-
 Constraints are a feature of many data platforms. When specified, the platform will perform additional validation on data as it is being populated in a new table or inserted into a preexisting table. If the validation fails, the table creation or update fails, the operation is rolled back, and you will see a clear error message.
 
 When enforced, a constraint guarantees that you will never see invalid data in the table materialized by your model. Enforcement varies significantly by data platform.