Merge branch 'production' into kathayl-patch-2

Author: daisyfaithauma

.github/CODEOWNERS

@@ -123,6 +123,8 @@
 /src/content/docs/workers/runtime-apis/bindings/ @irvinebroque @mikenomitch @GregBrimble @cloudflare/pcx-technical-writing
 /src/content/docs/workers/platform/ @irvinebroque @tanushree-sharma @GregBrimble @cloudflare/deploy-config @cloudflare/pcx-technical-writing
 /src/content/docs/workers/configuration/compatibility-dates/ @irvinebroque @mikenomitch @GregBrimble @cloudflare/deploy-config @cloudflare/pcx-technical-writing
+/src/content/docs/workers/configuration/compatibility-flags/ @irvinebroque @mikenomitch @GregBrimble @cloudflare/deploy-config @cloudflare/pcx-technical-writing
+
 /src/content/docs/workers/reference/migrate-to-module-workers/ @irvinebroque @GregBrimble @cloudflare/deploy-config @cloudflare/pcx-technical-writing
 /src/content/docs/workers/reference/security-model/ @irvinebroque @GregBrimble @cloudflare/pcx-technical-writing
 /src/content/compatibility-dates/ @irvinebroque @kflansburg @mikenomitch @GregBrimble @cloudflare/pcx-technical-writing

astro.config.ts

@@ -177,6 +177,7 @@ export default defineConfig({
 				? [
 						starlightLinksValidator({
 							errorOnInvalidHashes: false,
+							errorOnLocalLinks: false,
 							exclude: [
 								"/api/",
 								"/api/operations/**",

package-lock.json

@@ -39,11 +39,11 @@
 		"@types/node": "^22.8.7",
 		"@types/react": "^18.3.12",
 		"@types/react-dom": "^18.3.1",
-		"algoliasearch": "^5.12.0",
+		"algoliasearch": "^5.13.0",
 		"astro": "^4.16.9",
 		"astro-breadcrumbs": "^3.2.0",
-		"astro-icon": "^1.1.1",
-		"astro-live-code": "^0.0.3",
+		"astro-icon": "^1.1.2",
+		"astro-live-code": "^0.0.4",
 		"date-fns": "^4.1.0",
 		"detype": "1.0.12",
 		"dompurify": "3.1.6",
@@ -53,16 +53,16 @@
 		"hastscript": "^9.0.0",
 		"he": "^1.2.0",
 		"instantsearch.css": "^8.5.1",
-		"instantsearch.js": "^4.75.3",
+		"instantsearch.js": "^4.75.4",
 		"lz-string": "^1.5.0",
 		"marked": "^14.1.3",
-		"mermaid": "^11.3.0",
+		"mermaid": "^11.4.0",
 		"node-html-parser": "^6.1.13",
 		"patch-package": "^8.0.0",
 		"playwright": "^1.48.2",
 		"prettier": "^3.3.3",
 		"prettier-plugin-astro": "^0.14.1",
-		"puppeteer": "^23.6.1",
+		"puppeteer": "^23.7.0",
 		"react": "^18.3.1",
 		"react-dom": "^18.3.1",
 		"react-textarea-autosize": "^8.5.4",
@@ -73,8 +73,8 @@
 		"rehype-title-figure": "^0.1.2",
 		"sharp": "^0.33.5",
 		"solarflare-theme": "^0.0.2",
-		"starlight-image-zoom": "^0.8.0",
-		"starlight-links-validator": "^0.12.4",
+		"starlight-image-zoom": "^0.9.0",
+		"starlight-links-validator": "^0.13.0",
 		"starlight-package-managers": "^0.7.0",
 		"svgo": "^3.3.2",
 		"tailwindcss": "^3.4.14",

package.json

@@ -1629,6 +1629,7 @@
 /cloudflare-one/connections/connect-networks/install-and-setup/tunnel-guide/local/tunnel-useful-commands/ /cloudflare-one/connections/connect-networks/configure-tunnels/local-management/tunnel-useful-commands/ 301
 /cloudflare-one/connections/connect-networks/install-and-setup/deploy-cloudflared-replicas/ /cloudflare-one/connections/connect-networks/deploy-tunnels/deploy-cloudflared-replicas/ 301
 /cloudflare-one/connections/connect-networks/install-and-setup/tunnel-permissions/ /cloudflare-one/connections/connect-networks/configure-tunnels/local-management/tunnel-permissions/ 301
+/cloudflare-one/connections/connect-networks/install-and-setup/installation /cloudflare-one/connections/connect-networks/downloads/update-cloudflared/ 307
 /cloudflare-one/connections/connect-networks/deploy-tunnels/tunnel-permissions/ /cloudflare-one/connections/connect-networks/configure-tunnels/ 301
 /cloudflare-one/connections/connect-networks/install-and-setup/ports-and-ips/ /cloudflare-one/connections/connect-networks/deploy-tunnels/tunnel-with-firewall/ 301
 /cloudflare-one/connections/connect-networks/install-and-setup/tunnel-useful-terms/ /cloudflare-one/connections/connect-networks/get-started/tunnel-useful-terms/ 301

public/_redirects

@@ -57,7 +57,7 @@ if (lines) {
 		x.includes(`</docs-tag name="${tag}">`),
 	);
 
-	if (!startTag || !endTag) {
+	if (startTag === -1 || endTag === -1) {
 		throw new Error(`[GitHubCode] Unable to find a region using tag "${tag}".`);
 	}
 

src/assets/images/rules/normalization/url-normalization-settings.png

@@ -0,0 +1,26 @@
+---
+link: "/cache/changelog/"
+productName: Cache
+productLink: "/cache/"
+productArea: Application performance
+productAreaLink: /fundamentals/reference/changelog/performance/
+entries:
+  - publish_date: "2024-11-07"
+    title: Shard Cache by cache key
+    description: |-
+      For custom cache keys, enterprise customers can now shard their cache using up to three values for previously restricted headers `accept*`, `referer`, and `user-agent`. Sharding the cache can improve cache `HIT` ratio and performance. However, overly sharding your cache, can have the opposite effect.
+
+  - publish_date: "2024-11-07"
+    title: Versioning
+    description: |-
+      Cache now supports versioned environments allowing customers to stage configurations and purge staged environments. Note that Cache Reserve is only supported for your production environment.
+
+  - publish_date: "2024-09-05"
+    title: New Cache Rules templates for one-click rule creation
+    description: |-
+      The new **Rules** > **Templates** page in the Cloudflare dashboard provides one-click templates for creating cache rules, making it easy to optimize your caching strategy. Access these pre-built templates directly from each product's rule builder, and explore the [Examples gallery](/rules/examples/) in the developer documentation for real-world use cases.
+
+  - publish_date: "2024-07-19"
+    title: Generic tiered cache
+    description: |-
+      [Generic Global Tiered Cache](/cache/how-to/tiered-cache/#generic-global-tiered-cache) topology leverages all Cloudflare data centers as upper-tier cache network. It now hashes content within a region reducing duplication in upper-tier caches, which increases cache `HIT` ratio.

src/components/GitHubCode.astro

@@ -31,7 +31,7 @@ entries:
     description: |-
       The default [content type](/queues/configuration/javascript-apis/#queuescontenttype) for messages published to a queue is now `json`, which improves compatibility with the upcoming pull-based queues.
 
-      Any Workers created on or after the [compatibility date](/workers/configuration/compatibility-dates/#queues-send-messages-in-json-format) of `2024-03-18`, or that explicitly set the `queues_json_messages` compatibility flag, will use the new default behaviour. Existing Workers with a compatibility date prior will continue to use `v8` as the default content type for published messages.
+      Any Workers created on or after the [compatibility date](/workers/configuration/compatibility-flags/#queues-send-messages-in-json-format) of `2024-03-18`, or that explicitly set the `queues_json_messages` compatibility flag, will use the new default behaviour. Existing Workers with a compatibility date prior will continue to use `v8` as the default content type for published messages.
   - publish_date: "2024-02-24"
     title: Explicit retries no longer impact consumer concurrency/scaling.
     description: |-

src/content/changelogs/cache.yaml

@@ -56,7 +56,7 @@ entries:
     description: |-
       Vectorize `/query` HTTP endpoint has the following changes:
       - `returnVectors` request body property is deprecated in favor of `returnValues` and `returnMetadata` properties.
-      - Response format has changed to the below format to match [Workers API change]:(/workers/configuration/compatibility-dates/#vectorize-query-with-metadata-optionally-returned)
+      - Response format has changed to the below format to match [Workers API change]:(/workers/configuration/compatibility-flags/#vectorize-query-with-metadata-optionally-returned)
 
       ```json
       {