Skip to content

Commit 8f3dcf2

Browse files
committed
Adding equivalent changelog entry for D1 on smart placement.
1 parent 5b054d2 commit 8f3dcf2

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

src/content/release-notes/d1.yaml

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,17 @@ productLink: "/d1/"
55
productArea: Developer platform
66
productAreaLink: /workers/platform/changelog/platform/
77
entries:
8+
- publish_date: "2025-02-13"
9+
title: Standardized the Smart Placement behavior for Workers with D1 bindings.
10+
description: |-
11+
Previously, [Smart Placement](/workers/configuration/smart-placement/) ensured Workers with D1 bindings were created in the same location as the D1 database.
12+
13+
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.
814
- publish_date: "2025-02-04"
915
title: Fixed bug with D1 read-only access via UI and /query REST API.
1016
description: |-
1117
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.
12-
18+
1319
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.
1420
1521
- publish_date: "2025-01-13"

0 commit comments

Comments
 (0)