Skip to content

Fix D1 jurisdiction changelog date #26315

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

Merged
merged 2 commits into from
Nov 5, 2025
Merged

Fix D1 jurisdiction changelog date #26315

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d82a1d2
Fix D1 jurisdiction changelog date
vy-ton Nov 5, 2025
7d85662
Update d1.yaml
vy-ton Nov 5, 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
2 changes: 1 addition & 1 deletion ...angelog/d1/2025-10-31-d1-jurisdiction.mdx → ...angelog/d1/2025-11-05-d1-jurisdiction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: A D1 database can set a jurisdiction at creation, which limits the
products:
- d1
- workers
date: 2025-10-05
date: 2025-11-05
---

You can now set a [jurisdiction](/d1/configuration/data-location/) when creating a D1 database to guarantee where your database runs and stores data. Jurisdictions can help you comply with data localization regulations such as GDPR. Supported jurisdictions include `eu` and `fedramp`.
Expand Down
Loading