Skip to content

Commit 3d02f75

Browse files
authored
Fix D1 jurisdiction changelog date (#26315)
1 parent 5faad2e commit 3d02f75

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

src/content/changelog/d1/2025-10-31-d1-jurisdiction.mdx renamed to src/content/changelog/d1/2025-11-05-d1-jurisdiction.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: A D1 database can set a jurisdiction at creation, which limits the
44
products:
55
- d1
66
- workers
7-
date: 2025-10-05
7+
date: 2025-11-05
88
---
99

1010
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`.

src/content/release-notes/d1.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ link: "/d1/platform/release-notes/"
33
productName: D1
44
productLink: "/d1/"
55
entries:
6-
- publish_date: "2025-10-05"
6+
- publish_date: "2025-11-05"
77
title: D1 can configure jurisdictions for data localization
88
description: |-
99
You can now set a [jurisdiction](/d1/configuration/data-location/) when creating a D1 database to guarantee where your database runs and stores data.

0 commit comments

Comments
 (0)