diff --git a/src/content/release-notes/d1.yaml b/src/content/release-notes/d1.yaml
index a28615adcde6b0f..84e001fa83895c9 100644
--- a/src/content/release-notes/d1.yaml
+++ b/src/content/release-notes/d1.yaml
@@ -5,11 +5,19 @@ productLink: "/d1/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2025-02-13"
+    title: Standardized the Smart Placement behavior for Workers with D1 bindings.
+    description: |-
+      Previously, [Smart Placement](/workers/configuration/smart-placement/) ensured Workers with D1 bindings were created in the same location as the D1 database.
+
+      Now, all Workers which use Smart Placement use the same [placement logic](/workers/configuration/smart-placement/#understand-how-smart-placement-works), even if they have D1 bindings.
+
+      You can find the corresponding Worker changelog entry [here](/workers/platform/changelog/#2025-02-13).
   - publish_date: "2025-02-04"
     title: Fixed bug with D1 read-only access via UI and /query REST API.
     description: |-
       Fixed a bug with D1 permissions which allowed users with read-only roles via the UI and users with read-only API tokens via the `/query` [REST API](/api/resources/d1/subresources/database/methods/query/) to execute queries that modified databases. UI actions via the `Tables` tab, such as creating and deleting tables, were incorrectly allowed with read-only access. However, UI actions via the `Console` tab were not affected by this bug and correctly required write access.
-      
+
       Write queries with read-only access will now fail. If you relied on the previous incorrect behavior, please assign the correct roles to users or permissions to API tokens to perform D1 write queries.
 
   - publish_date: "2025-01-13"