diff --git a/src/content/changelog/d1/2025-10-31-d1-jurisdiction.mdx b/src/content/changelog/d1/2025-11-05-d1-jurisdiction.mdx
similarity index 98%
rename from src/content/changelog/d1/2025-10-31-d1-jurisdiction.mdx
rename to src/content/changelog/d1/2025-11-05-d1-jurisdiction.mdx
index 48f65d2e6a0bdb..2924a91cb233d8 100644
--- a/src/content/changelog/d1/2025-10-31-d1-jurisdiction.mdx
+++ b/src/content/changelog/d1/2025-11-05-d1-jurisdiction.mdx
@@ -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`.
diff --git a/src/content/release-notes/d1.yaml b/src/content/release-notes/d1.yaml
index d3c3899445926a..7a87c90f5199c3 100644
--- a/src/content/release-notes/d1.yaml
+++ b/src/content/release-notes/d1.yaml
@@ -3,7 +3,7 @@ link: "/d1/platform/release-notes/"
 productName: D1
 productLink: "/d1/"
 entries:
-  - publish_date: "2025-10-05"
+  - publish_date: "2025-11-05"
     title: D1 can configure jurisdictions for data localization
     description: |-
       You can now set a [jurisdiction](/d1/configuration/data-location/) when creating a D1 database to guarantee where your database runs and stores data.