Merge branch 'cloudflare:production' into changelog-apishield-1

Author: cosgrove-cf

.hyperlint/.vale.ini

@@ -1,4 +1,4 @@
-StylesPath = ./automations/styles
+StylesPath = automations/styles
 MinAlertLevel = suggestion
 IgnoredScopes = code, tt, img
 SkippedScopes = script, style, pre, figure, code
@@ -17,4 +17,4 @@ Vale.Spelling = NO
 
 [*.yaml]
 BasedOnStyles = Vale, cloudflare, cloudflare-automation
-Vale.Spelling = NO
+Vale.Spelling = NO

src/content/changelog/agents/2025-03-18-npm-i-agents.mdx

@@ -43,7 +43,7 @@ We've added a number of big new features to the Agents SDK over the past few wee
 
 - You can now set `cors: true` when using `routeAgentRequest` to return permissive default CORS headers to Agent responses.
 - The regular client now syncs state on the agent (just like the React version).
-- `useAgentChat` bug fixes for passing headers/credentials, includng properly clearing cache on unmount.
+- `useAgentChat` bug fixes for passing headers/credentials, including properly clearing cache on unmount.
 - Experimental `/schedule` module with a prompt/schema for adding scheduling to your app (with evals!).
 - Changed the internal `zod` schema to be compatible with the limitations of Google's Gemini models by removing the discriminated union, allowing you to use Gemini models with the scheduling API.
 

src/content/changelog/autorag/2025-04-07-autorag-open-beta.mdx

@@ -7,7 +7,7 @@ products:
 date: 2025-04-07T6:00:00Z
 ---
 
-[AutoRAG](/autorag) is now in open beta, making it easy for you to build fully-managed retrieval-augmented generation (RAG) pipelines without managing infrasturcture. Just upload your docs to [R2](/r2/get-started/), and AutoRAG handles the rest: embeddings, indexing, retrieval, and response generation via API.
+[AutoRAG](/autorag) is now in open beta, making it easy for you to build fully-managed retrieval-augmented generation (RAG) pipelines without managing infrastructure. Just upload your docs to [R2](/r2/get-started/), and AutoRAG handles the rest: embeddings, indexing, retrieval, and response generation via API.
 
 ![AutoRAG open beta demo](~/assets/images/changelog/autorag/autorag-open-beta.gif)
 

src/content/changelog/kv/2025-04-10-kv-bulk-reads.mdx

@@ -12,7 +12,7 @@ This makes it easier to request multiple KV pairs within a single Worker invocat
 ```js
 // Read single key
 const key = "key-a";
-const value = await env.NAMESPACE.get(keys);
+const value = await env.NAMESPACE.get(key);
 
 // Read multiple keys
 const keys = ["key-a", "key-b", "key-c", ...] // up to 100 keys

src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx

@@ -12,4 +12,4 @@ This enhancement makes it easier for customers to adopt Logpush and R2.
 
 For more details refer to our [Logs](/logs/get-started/enable-destinations/r2/) documentation.
 
-![One CLick Logpush to R2](src/assets/images/changelog/logs/Oneclick.gif)
+![One-click Logpush to R2](src/assets/images/changelog/logs/Oneclick.gif)

src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx

@@ -0,0 +1,23 @@
+---
+title: Custom fields raw and transformed values support
+description: Configure request header and response headers values can log eiterh raw or transformed value
+date: 2025-04-18T11:00:00Z
+---
+
+Custom Fields now support logging both **raw and transformed values** for request and response headers in the HTTP requests dataset.
+
+These fields are configured per zone and apply to all Logpush jobs in that zone that include request headers, response headers. Each header can be logged in only one format—either raw or transformed—not both.
+
+By default:
+
+- Request headers are logged as raw values
+- Response headers are logged as transformed values
+
+These defaults can be overidden to suit your logging needs.
+
+:::note
+
+Transformed and raw values for request and response headers are available **only via the API** and cannot be set through the UI.
+:::
+
+For more information refer to [Custom fields](/logs/reference/custom-fields/) documentation

src/content/changelog/magic-cloud-networking/2024-12-05-cloud-onramp-terraform.mdx

@@ -1,5 +1,5 @@
 ---
-title: Generate customized terrform files for building cloud network on-ramps
+title: Generate customized terraform files for building cloud network on-ramps
 description: Download cloud onramp terraform
 date: 2024-12-05T11:00:00Z
 ---

src/content/changelog/magic-firewall/2024-10-02-custom-rule-search.mdx

@@ -15,4 +15,4 @@ The Magic Firewall dashboard now allows you to search custom rules using the rul
 
 Additionally, the rule ID URL link has been added to Network Analytics.
 
-For more details abour rules, refer to [Add rules](/magic-firewall/how-to/add-rules/).
+For more details about rules, refer to [Add rules](/magic-firewall/how-to/add-rules/).

src/content/docs/workflows/build/rules-of-workflows.mdx

@@ -380,7 +380,7 @@ export class MyWorkflow extends WorkflowEntrypoint {
 
 ### Instance IDs are unique
 
-Workflow [instance IDs](/workflows/build/workers-api/#workflowinstance) are unique per Workflow. The ID is the unique identifier that associates logs, metrics, state and status of a run to a specific an instance, even after completion. Allowing ID re-use would make it hard to understand if a Workflow instance ID referred to an instance that run yesterday, last week or today.
+Workflow [instance IDs](/workflows/build/workers-api/#workflowinstance) are unique per Workflow. The ID is the unique identifier that associates logs, metrics, state and status of a run to a specific instance, even after completion. Allowing ID re-use would make it hard to understand if a Workflow instance ID referred to an instance that run yesterday, last week or today.
 
 It would also present a problem if you wanted to run multiple different Workflow instances with different [input parameters](/workflows/build/events-and-parameters/) for the same user ID, as you would immediately need to determine a new ID mapping.
 

src/util/api.ts

@@ -1,7 +1,7 @@
 import SwaggerParser from "@apidevtools/swagger-parser";
 import type { OpenAPI } from "openapi-types";
 
-const COMMIT = "9b9382ef73e94ccf9d833175658cf2fc891f13e5";
+const COMMIT = "e230d6ba9f7171cbe73e5574b24c00fd2e9bca05";
 let schema: OpenAPI.Document | undefined;
 
 export const getSchema = async () => {