Merge branch 'cloudflare:production' into production

Author: Thienlta

package-lock.json

@@ -42,7 +42,7 @@
 		"@expressive-code/plugin-line-numbers": "0.41.3",
 		"@floating-ui/react": "0.27.16",
 		"@iarna/toml": "2.2.5",
-		"@lottiefiles/dotlottie-react": "0.16.0",
+		"@lottiefiles/dotlottie-react": "0.16.1",
 		"@marsidev/react-turnstile": "1.3.0",
 		"@microsoft/fetch-event-source": "2.0.1",
 		"@nanostores/react": "1.0.0",

package.json

@@ -0,0 +1,30 @@
+---
+title: Regional Email Processing for Germany, India, or Australia
+description: Customers can now choose their preferred mail processing location to be Germany, India, or Australia during onboarding
+date: 2025-09-11T23:15:00Z
+---
+
+We’re excited to announce that Email Security customers can now choose their preferred mail processing location directly from the UI when onboarding a domain. This feature is available for the following onboarding methods: **MX**, **BCC**, and **Journaling**.  
+
+### What’s new
+Customers can now select where their email is processed. The following regions are supported:  
+- **Germany**  
+- **India**  
+- **Australia**  
+
+Global processing remains the default option, providing flexibility to meet both compliance requirements or operational preferences.  
+
+### How to use it
+When onboarding a domain with MX, BCC, or Journaling:  
+1. Select the desired processing location (Germany, India, or Australia).  
+2. The UI will display updated processing addresses specific to that region.  
+3. For MX onboarding, if your domain is managed by Cloudflare, you can automatically update MX records directly from the UI.  
+
+### Availability
+This feature is available across these Email Security packages: 
+-   **Advantage** 
+-   **Enterprise** 
+-   **Enterprise + PhishGuard** 
+
+### What’s next
+We’re expanding the list of processing locations to match our [Data Localization Suite (DLS)](/data-localization/) footprint, giving customers the broadest set of regional options in the market without the complexity of self-hosting.  

src/assets/images/cloudflare-for-platforms/active-rule.png

@@ -0,0 +1,18 @@
+---
+title: Worker version rollback limit increased from 10 to 100
+description: Workers can now be deployed and rolled back to their most recent 100 versions, up from the previous limit of 10.
+products:
+  - workers
+date: 2025-09-11
+---
+The number of recent versions available for a Worker rollback has been increased from 10 to 100.
+
+This allows you to: 
+
+* Promote any of the 100 most recent versions to be the active deployment. 
+
+* Split traffic using [gradual deployments](/workers/configuration/versions-and-deployments/gradual-deployments/) between your latest code and any of the 100 most recent versions.
+
+You can do this through the Cloudflare dashboard or with [Wrangler's rollback command](/workers/wrangler/commands/#rollback)
+
+Learn more about [versioned deployments](/workers/configuration/versions-and-deployments/) and [rollbacks](/workers/configuration/versions-and-deployments/rollbacks/). 

src/assets/images/cloudflare-for-platforms/rule-expression.png

@@ -9,6 +9,8 @@ sidebar:
 
 import { GlossaryTooltip, Render, Steps } from "~/components"
 
+<Render file="survey" product="waf" />
+
 This guide will help you set up API Shield to identify and address API security best practices.
 
 :::note

src/content/changelog/email-security-cf1/2025-09-11-regional-email-processing-gia.mdx

@@ -11,6 +11,8 @@ head:
 
 import { Description, Feature, Plan, RelatedProduct, Render } from "~/components"
 
+<Render file="survey" product="waf" />
+
 <Description>
 Identify and address your API vulnerabilities.
 </Description>

src/content/changelog/workers/2025-09-11-increased-version-rollback-limit.mdx

@@ -7,7 +7,9 @@ sidebar:
 
 ---
 
-import { GlossaryTooltip, Plan, Steps, Tabs, TabItem } from "~/components"
+import { GlossaryTooltip, Plan, Steps, Tabs, TabItem, Render } from "~/components"
+
+<Render file="survey" product="waf" />
 
 <Plan type="all" />
 

src/content/docs/api-shield/get-started.mdx

@@ -6,7 +6,9 @@ sidebar:
 
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, Render } from "~/components"
+
+<Render file="survey" product="waf" />
 
 Cloudflare offers the following features to help secure your APIs: