Merge branch 'cloudflare:production' into production

Author: krishnprakash

bin/fetch-warp-releases.js

@@ -35,7 +35,12 @@ for (let track of tracks) {
 					track = track.replace("noble-intel", "linux");
 				}
 
-				const path = `./src/content/warp-releases/${track}/${item.version}.yaml`;
+				const folder = `./src/content/warp-releases/${track}`;
+				const path = `${folder}/${item.version}.yaml`;
+
+				if (!fs.existsSync(folder)) {
+					fs.mkdirSync(folder, { recursive: true });
+				}
 
 				if (fs.existsSync(path)) {
 					console.log(`${track} ${item.version} already exists.`);
@@ -66,13 +71,16 @@ for (let track of tracks) {
 				});
 
 				const releaseNotes = tokens.reduce((s, t) => s + t.raw, "");
+				const platformName = data.platformName.startsWith("noble-")
+					? "Linux"
+					: data.platformName;
 
 				fs.writeFileSync(
 					`./src/content/warp-releases/${track}/${item.version}.yaml`,
 					YAML.stringify({
 						...item,
 						releaseNotes,
-						platformName: data.platformName,
+						platformName,
 					}),
 					"utf-8",
 				);

src/components/search/InstantSearch.tsx

@@ -15,7 +15,7 @@ function SearchBox(props: UseSearchBoxProps) {
 
 	useEffect(() => {
 		const params = new URLSearchParams(window.location.search);
-		const query = params.get("query");
+		const query = params.get("q") ?? params.get("query");
 
 		if (query) {
 			refine(query);

src/content/docs/data-localization/compatibility.mdx

@@ -126,10 +126,10 @@ The table below provides a summary of the Data Localization Suite product's beha
 [^12]: Logpull not available when using Customer Metadata Boundary outside US region. Logs may be stored and retrieved with [Logs Engine](https://blog.cloudflare.com/announcing-logs-engine/) which is adding region support in 2025.
 [^13]: Logpush available with Customer Metadata Boundary for [these datasets](/data-localization/metadata-boundary/logpush-datasets/). Contact your account team if you need another dataset.
 [^14]: Access App SSL keys can use Geo Key Manager. [Access JWT](/cloudflare-one/identity/authorization-cookie/validating-json/) is not yet localized.
-[^15]: Can be localized to US FedRAMP region only. More regions coming in 2024.
+[^15]: Can be localized to US FedRAMP Moderate Domestic region only.
 [^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
 [^17]: Currently may only be used with US FedRAMP region.
-[^18]: The only connectivity option is [US FedRAMP region](/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters/#region). Regional Services only applies when using [Public Hostnames](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) set to a region.
+[^18]: The only connectivity option is [US FedRAMP Moderate Domestic region](/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters/#region). Regional Services only applies when using [Public Hostnames](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) set to a region.
 [^19]: Uses Gateway HTTP and CASB.
 [^20]: You can [bring your own certificate](https://blog.cloudflare.com/bring-your-certificates-cloudflare-gateway/) to Gateway but these cannot yet be restricted to a specific region.
 [^21]: Gateway HTTP supports Regional Services. Gateway DNS does not yet support regionalization. <br/> ICMP proxy and WARP-to-WARP proxy are not available to Regional Services users.

src/content/docs/workers/local-development.mdx

@@ -40,22 +40,24 @@ npx wrangler dev
 | D1                                  | ✅                  | ✅                   |
 | Durable Objects                     | ✅                  | ✅                   |
 | Email Bindings                      | ❌                  | ✅                   |
-| Hyperdrive                          | ✅                  | ✅                   |
+| Hyperdrive                          | ✅[^2]              | ✅                   |
 | Images                              | ✅                  | ✅                   |
 | KV                                  | ✅                  | ✅                   |
 | mTLS                                | ❌                  | ✅                   |
 | Queues                              | ✅                  | ❌                   |
 | R2                                  | ✅                  | ✅                   |
 | Rate Limiting                       | ✅                  | ✅                   |
 | Service Bindings (multiple workers) | ✅                  | ✅                   |
-| Vectorize                           | ✅[^2]              | ✅                   |
+| Vectorize                           | ✅[^3]              | ✅                   |
 | Workflows                           | ✅                  | ❌                   |
 
 With any bindings that are not supported locally, you will need to use the [`--remote` command](#develop-using-remote-resources-and-bindings) in wrangler, such as `wrangler dev --remote`.
 
 [^1]: Using Workers AI always accesses your Cloudflare account in order to run AI models and will incur usage charges even in local development.
 
-[^2]: Using Vectorize always accesses your Cloudflare account to run queries, and will incur usage charges even in local development.
+[^2]: Using Hyperdrive with local development allows you to connect to a local database (running on `localhost`) but you cannot connect to a remote database. To connect to a remote database, use remote development.
+
+[^3]: Using Vectorize always accesses your Cloudflare account to run queries, and will incur usage charges even in local development.
 
 ## Work with local data