From 52d6fae57e7c7d62f795edba27a9d858a3bc8174 Mon Sep 17 00:00:00 2001
From: epenet <6771947+epenet@users.noreply.github.com>
Date: Tue, 4 Mar 2025 08:01:33 +0100
Subject: [PATCH] Update config flow unique ID blog post (#2587)

* Update config flow unique ID blog post

* Update 2025-03-01-config-flow-unique-id.md
---
 blog/2025-03-01-config-flow-unique-id.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/blog/2025-03-01-config-flow-unique-id.md b/blog/2025-03-01-config-flow-unique-id.md
index 00da1883..261f2c73 100644
--- a/blog/2025-03-01-config-flow-unique-id.md
+++ b/blog/2025-03-01-config-flow-unique-id.md
@@ -6,6 +6,10 @@ title: "New checks for config flow unique ID"
 
 ### Summary of changes
 
+Creating a config entry with a unique ID already present in the registry is deprecated, and will now log a warning.
+
+### Details
+
 When a config flow creates an entry with a colliding unique ID, the old entry is currently automatically removed and replaced with the new config entry.
 This can lead to unexpected behavior, and integrations should be adjusted to instead abort the flow.