[WAF] Update deprecation dates (#17720)

Author: pedrosousa

src/content/changelogs/api-deprecations.yaml

@@ -46,10 +46,10 @@ entries:
       - `GET /accounts/:account_id`
       - `PUT /accounts/:account_id`
 
-  - publish_date: "2025-01-15"
+  - publish_date: "2025-06-15"
     title: "Firewall Rules API and Filters API"
     description: |-
-      Deprecation date: January 15, 2025
+      Deprecation date: June 15, 2025
 
       The Firewall Rules API and the Filters API are deprecated, since Firewall Rules was deprecated in favor of [WAF custom rules](/waf/custom-rules/). Refer to [Firewall Rules to WAF custom rules migration](/waf/reference/migration-guides/firewall-rules-to-custom-rules/) for more information about this change.
 
@@ -74,10 +74,10 @@ entries:
 
       Replacement: [WAF custom rules](/waf/custom-rules/)
 
-  - publish_date: "2025-01-15"
+  - publish_date: "2025-06-15"
     title: "WAF managed rules APIs (previous version)"
     description: |-
-      Deprecation date: January 15, 2025
+      Deprecation date: June 15, 2025
 
       The APIs for managing WAF managed rules (previous version) — namely for managing packages, rule groups, rules, and overrides — are deprecated in favor of [WAF Managed Rules](/waf/managed-rules/). Refer to [WAF Managed Rules migration](/waf/reference/migration-guides/waf-managed-rules-migration/) for more information about this change.
 
@@ -100,10 +100,10 @@ entries:
 
       Replacement: [WAF Managed Rules](/waf/managed-rules/) (new version)
 
-  - publish_date: "2025-01-15"
+  - publish_date: "2025-06-15"
     title: "Rate Limiting API (previous version)"
     description: |-
-      Deprecation date: January 15, 2025
+      Deprecation date: June 15, 2025
 
       The Rate Limiting API is deprecated, since the previous version of rate limiting rules was deprecated in favor of the new [rate limiting rules](/waf/rate-limiting-rules/) based on the Ruleset Engine. Refer to [Rate limiting (previous version) deprecation notice](/waf/reference/migration-guides/old-rate-limiting-deprecation/) for more information about this change.
 

src/content/docs/waf/reference/migration-guides/firewall-rules-to-custom-rules.mdx

@@ -9,9 +9,9 @@ Cloudflare converted existing [firewall rules](/firewall/) into [WAF custom rule
 
 :::caution[Deprecation notice]
 
-**Cloudflare Firewall Rules is now deprecated.** The Firewall Rules API and Filters API, as well as the `cloudflare_firewall_rule` and `cloudflare_filter` Terraform resources, will only be available until 2025-01-15. If you have any automation based on these APIs and resources, you must migrate to the new APIs and resources before 2025-01-15 to avoid any issues.
+**Cloudflare Firewall Rules is now deprecated.** The Firewall Rules API and Filters API, as well as the `cloudflare_firewall_rule` and `cloudflare_filter` Terraform resources, will only be available until 2025-06-15. If you have any automation based on these APIs and resources, you must migrate to the new APIs and resources before 2025-06-15 to avoid any issues.
 
-On 2025-01-15, the APIs and resources mentioned above will stop working. Any remaining active firewall rules will be disabled, and the **Firewall rules** tab in the dashboard will be removed.
+On 2025-06-15, the APIs and resources mentioned above will stop working. Any remaining active firewall rules will be disabled, and the **Firewall rules** tab in the dashboard will be removed.
 
 If you have not migrated to WAF custom rules yet, you may have some invalid configuration that prevents the migration from happening. In this case, contact your account team to get help with the migration to WAF custom rules.
 
@@ -113,7 +113,7 @@ You may still find events generated by Firewall Rules in the Security Events pag
 
 The preferred API for managing WAF custom rules is the [Rulesets API](/waf/custom-rules/create-api/). The Rulesets API is used on all recent Cloudflare security products to provide a uniform user experience when interacting with our API. For more information on migrating to the Rulesets API, refer to [Relevant changes for API users](#relevant-changes-for-api-users).
 
-The Firewall Rules API and Filters API will still work until 2025-01-15. There will be a single list of rules for both firewall rules and WAF custom rules, and this list contains WAF custom rules. Thanks to an internal conversion process, the Firewall Rules API and Filters API will return firewall rules/filters converted from these WAF custom rules.
+The Firewall Rules API and Filters API will still work until 2025-06-15. There will be a single list of rules for both firewall rules and WAF custom rules, and this list contains WAF custom rules. Thanks to an internal conversion process, the Firewall Rules API and Filters API will return firewall rules/filters converted from these WAF custom rules.
 
 If you are using Terraform, the preferred way of configuring WAF custom rules is using [`cloudflare_ruleset`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/ruleset) resources configured with the `http_request_firewall_custom` phase. For more information on updating your Terraform configuration, refer to [Relevant changes for Terraform users](#relevant-changes-for-terraform-users).
 
@@ -123,11 +123,11 @@ If you are using Terraform, the preferred way of configuring WAF custom rules is
 
 ![The Custom rules tab, available in the Cloudflare dashboard under Security > WAF.](~/assets/images/waf/custom-rules/custom-rules-tab.png)
 
-For users that still have access to both products, the **Firewall rules** tab will only be available until 2025-01-15.
+For users that still have access to both products, the **Firewall rules** tab will only be available until 2025-06-15.
 
 ## Relevant changes for API users
 
-**The [Firewall Rules API](/firewall/api/cf-firewall-rules/) and the associated [Cloudflare Filters API](/firewall/api/cf-filters/) are now deprecated.** These APIs will stop working on 2025-01-15. You must migrate any automation based on the Firewall Rules API or Cloudflare Filters API to the [Rulesets API](/waf/custom-rules/create-api/) before this date to prevent any issues. Rule IDs are different between firewall rules and custom rules, which may affect automated processes dealing with specific rule IDs.
+**The [Firewall Rules API](/firewall/api/cf-firewall-rules/) and the associated [Cloudflare Filters API](/firewall/api/cf-filters/) are now deprecated.** These APIs will stop working on 2025-06-15. You must migrate any automation based on the Firewall Rules API or Cloudflare Filters API to the [Rulesets API](/waf/custom-rules/create-api/) before this date to prevent any issues. Rule IDs are different between firewall rules and custom rules, which may affect automated processes dealing with specific rule IDs.
 
 For the time being, all three APIs will be available (Firewall Rules API, Filters API, and Rulesets API). Cloudflare will internally convert your [Firewall Rules API](/firewall/api/cf-firewall-rules/) and [Filters API](/firewall/api/cf-filters/) calls into the corresponding [Rulesets API](/waf/custom-rules/create-api/) calls. The converted API calls between the Firewall Rules API/Filters API and the Rulesets API appear in audit logs as generated by Cloudflare and not by the actual user making the requests. There will be a single list of rules for both firewall rules and WAF custom rules.
 
@@ -142,7 +142,7 @@ Refer to the WAF documentation for [examples of managing WAF custom rules using
 - [`cloudflare_firewall_rule`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/firewall_rule)
 - [`cloudflare_filter`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/filter)
 
-These resources will stop working on 2025-01-15. If you are currently using these resources to manage your Firewall Rules configuration, you must manually migrate any Terraform configuration to [`cloudflare_ruleset`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/ruleset) resources before this date to prevent any issues.
+These resources will stop working on 2025-06-15. If you are currently using these resources to manage your Firewall Rules configuration, you must manually migrate any Terraform configuration to [`cloudflare_ruleset`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/ruleset) resources before this date to prevent any issues.
 
 For the time being, all three Terraform resources will be available (`cloudflare_firewall_rule`, `cloudflare_filter`, and `cloudflare_ruleset`). There will be a single list of rules for both firewall rules and WAF custom rules.
 

src/content/docs/waf/reference/migration-guides/index.mdx

@@ -5,7 +5,6 @@ sidebar:
   order: 4
   group:
     hideIndex: true
-head: []
 description: Reference guides for users migrating from deprecated Cloudflare
   features to the Cloudflare WAF.
 ---

src/content/docs/waf/reference/migration-guides/old-rate-limiting-deprecation.mdx

@@ -10,7 +10,7 @@ description: Guide on the deprecation of rate limiting rules (previous version)
   and how to migrate to the new version.
 ---
 
-**The [previous version of rate limiting rules](/waf/reference/legacy/old-rate-limiting/) is now deprecated.** If you have rules in the previous version, the Cloudflare dashboard will show the configuration for both new (**A**) and old (**B**) rate limiting rules in **Security** > **WAF** > **Rate limiting rules**. The rate limiting rules interface for the previous version will only be available in the dashboard until 2025-01-15. After this date all remaining active rules will stop working.
+**The [previous version of rate limiting rules](/waf/reference/legacy/old-rate-limiting/) is now deprecated.** If you have rules in the previous version, the Cloudflare dashboard will show the configuration for both new (**A**) and old (**B**) rate limiting rules in **Security** > **WAF** > **Rate limiting rules**. The rate limiting rules interface for the previous version will only be available in the dashboard until 2025-06-15. After this date all remaining active rules will stop working.
 
 ![The Cloudflare dashboard showing both versions of rate limiting rules under WAF.](~/assets/images/waf/reference/rate-limiting-both-versions.png)
 
@@ -55,13 +55,13 @@ If you had access to the previous version of Cloudflare Rate Limiting, you will
 
 The new rate limiting rules are based on the [Ruleset Engine](/ruleset-engine/). To configure rate limiting rules via the API, you must use the [Rulesets API](/ruleset-engine/rulesets-api/). The Rulesets API is used on all recent Cloudflare security products to provide a uniform user experience when interacting with the Cloudflare API.
 
-**The [previous Rate Limiting API](/api/operations/rate-limits-for-a-zone-list-rate-limits) is now deprecated.** You will not be able to perform any API calls after 2025-01-15.
+**The [previous Rate Limiting API](/api/operations/rate-limits-for-a-zone-list-rate-limits) is now deprecated.** You will not be able to perform any API calls after 2025-06-15.
 
 ### Relevant changes for Terraform users
 
 To configure the new rate limiting rules with Terraform, you must use the [`cloudflare_ruleset`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/ruleset) Terraform resource. Refer to the Terraform documentation for [examples of configuring the new rate limiting rules using Terraform](/terraform/additional-configurations/rate-limiting-rules/).
 
-**The [`cloudflare_rate_limit`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/rate_limit) Terraform resource is now deprecated.** You will not be able to perform configuration updates via Terraform using this resource after 2025-01-15.
+**The [`cloudflare_rate_limit`](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs/resources/rate_limit) Terraform resource is now deprecated.** You will not be able to perform configuration updates via Terraform using this resource after 2025-06-15.
 
 ## Migrate to the new rate limiting rules
 
@@ -75,14 +75,14 @@ If you were using the previous version of rate limiting rules, you will have acc
 
 The previous version of Rate Limiting was billed based on usage ($5 per million requests) while the new rate limiting rules are included in your plan and you will not have additional charges for using this feature.
 
-If you have any rules configured in the previous version of rate limiting rules, these rules will continue to run and you will still be charged based on usage. You should migrate your rules to the new system before 2025-01-15.
+If you have any rules configured in the previous version of rate limiting rules, these rules will continue to run and you will still be charged based on usage. You should migrate your rules to the new system before 2025-06-15.
 
 Once you have deleted all rules from the previous version of rate limiting rules, the Cloudflare dashboard will only show the new version.
 
 ### Enterprise customers
 
 Enterprise contracts that included the previous version of Cloudflare Rate Limiting were based on the good requests model, where customers were billed based on the predicted usage of the feature. If you were using the previous version of Cloudflare Rate Limiting, you will have access to both versions of the product with the same number of rules at no additional cost, and they will both apply to your incoming traffic (in this case, the new Rate Limiting will run first).
 
-You should migrate your rules to the new system before 2025-01-15. Once you have deleted all rules from the previous version of rate limiting rules, the Cloudflare dashboard will only show the new version.
+You should migrate your rules to the new system before 2025-06-15. Once you have deleted all rules from the previous version of rate limiting rules, the Cloudflare dashboard will only show the new version.
 
 As an Enterprise customer, you can also upgrade to [Advanced Rate Limiting](https://blog.cloudflare.com/advanced-rate-limiting/), a more feature-rich version of the new Rate Limiting implementation. Contact your account team to learn more about Advanced Rate Limiting.

src/content/docs/waf/reference/migration-guides/waf-managed-rules-migration.mdx

@@ -15,7 +15,7 @@ Once the migration finishes, the **Managed rules** tab in the Cloudflare dashboa
 
 :::caution[Deprecation notice]
 
-**The previous version of WAF managed rules is now deprecated.** The [APIs for managing the previous version of WAF managed rules](#api-changes) will stop working on 2025-01-15. The same applies to [Terraform resources](#terraform-changes) related to the previous version of WAF managed rules. You must migrate before this date to avoid any issues.
+**The previous version of WAF managed rules is now deprecated.** The [APIs for managing the previous version of WAF managed rules](#api-changes) will stop working on 2025-06-15. The same applies to [Terraform resources](#terraform-changes) related to the previous version of WAF managed rules. You must migrate before this date to avoid any issues.
 
 Refer to [Possible migration errors](#possible-migration-errors) if you are having issues migrating.