Extend EoL for cname_flattening deprecation

src/content/release-notes/api-deprecations.yaml

@@ -35,6 +35,29 @@ entries:
         * `POST /accounts/{account_id}/devices/registrations/revoke`
         * `POST /accounts/{account_id}/devices/registrations/unrevoke`
 
+  - publish_date: "2025-06-08"
+    title: "Zone Setting: cname_flattening"
+    description: |-
+      Deprecation date: June 8, 2025
+
+      The Zone Settings API endpoints for managing zone-level CNAME flattening are deprecated.
+      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage this setting.
+
+      Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Zone Settings endpoints.
+
+      Note that, with the deprecated zone setting, values `"off"` and `"apex"` have the same behavior. These are represented as `{"flatten_all_cnames": false}` in the new API.
+      The zone setting `"on"` corresponds to `{"flatten_all_cnames": true}` in the new API.
+
+      Affected APIs:
+
+      - `GET /zones/:zone_id/settings`
+      - `PATCH /zones/:zone_id/settings`
+
+      Deprecated APIs:
+
+      - `GET /zones/:zone_id/settings/cname_flattening`
+      - `PATCH /zones/:zone_id/settings/cname_flattening`
+
   - publish_date: "2025-03-20"
     title: "Cloudflare Radar: Attack top industry and vertical endpoints"
     description: |-
@@ -153,29 +176,6 @@ entries:
       - `GET /zones/:zone_id/access/apps/:app_id`
       - `PUT /zones/:zone_id/access/apps/:app_id`
 
-  - publish_date: "2025-03-21"
-    title: "Zone Setting: cname_flattening"
-    description: |-
-      Deprecation date: March 21, 2025
-
-      The Zone Settings API endpoints for managing zone-level CNAME flattening are deprecated.
-      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage this setting.
-
-      Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Zone Settings endpoints.
-
-      Note that, with the deprecated zone setting, values `"off"` and `"apex"` have the same behavior. These are represented as `{"flatten_all_cnames": false}` in the new API.
-      The zone setting `"on"` corresponds to `{"flatten_all_cnames": true}` in the new API.
-
-      Affected APIs:
-
-      - `GET /zones/:zone_id/settings`
-      - `PATCH /zones/:zone_id/settings`
-
-      Deprecated APIs:
-
-      - `GET /zones/:zone_id/settings/cname_flattening`
-      - `PATCH /zones/:zone_id/settings/cname_flattening`
-
   - publish_date: "2025-03-14"
     title: "Account Settings: default_nameservers and use_account_custom_ns_by_default"
     description: |-