Skip to content

[D1] Adding equivalent changelog entry for D1 on smart placement. #20126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

[D1] Adding equivalent changelog entry for D1 on smart placement. #20126

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8f3dcf2
Adding equivalent changelog entry for D1 on smart placement.
Oxyjun Feb 20, 2025
132f7da
Cross-referencing to the Worker changelog entry.
Oxyjun Feb 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion src/content/release-notes/d1.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
Loading