Merge remote-tracking branch 'refs/remotes/origin/dpena/dash-buttons' into dpena/dash-buttons

Author: dcpena

src/assets/images/changelog/d1/d1-auto-retry-success-ratio.png

@@ -65,6 +65,22 @@ export default function ProductSelect({ products, groups }: Props) {
 			select.value = option.value;
 			select.dispatchEvent(event);
 		}
+
+		const search = document.querySelector<HTMLAnchorElement>(
+			"#changelog-search-button",
+		);
+
+		if (search) {
+			if (
+				options
+					.find((opt) => opt.label === "Products")
+					?.options?.includes(option)
+			) {
+				search.href = `/search/?contentType=Changelog+entry&product=${encodeURIComponent(option.label)}`;
+			} else {
+				search.href = `/search/?contentType=Changelog+entry`;
+			}
+		}
 	};
 
 	return (

src/assets/images/changelog/dlp/ai-prompt-detection-entry.png

@@ -21,6 +21,7 @@ import {
 	FloatingPortal,
 } from "@floating-ui/react";
 import { PiCaretDownBold } from "react-icons/pi";
+import { subDays } from "date-fns";
 import { setSearchParams } from "~/util/url";
 import he from "he";
 
@@ -73,6 +74,13 @@ function InfiniteHits(props: UseInfiniteHitsProps) {
 					.map(([, value]) => value);
 
 				const title = hierarchy ? hierarchy.join(" > ") : "Documentation";
+				const today = new Date();
+				const futureDate = subDays(today, item.lastModified);
+				const options: Intl.DateTimeFormatOptions = {
+					year: "numeric",
+					month: "long",
+					day: "numeric",
+				};
 
 				return (
 					<a
@@ -84,6 +92,11 @@ function InfiniteHits(props: UseInfiniteHitsProps) {
 						<p className="line-clamp-2">
 							<Highlight attribute="content" hit={item} />
 						</p>
+						{item.lastModified && (
+							<span className="text-cl1-gray-4! dark:text-cl1-gray-7! mt-2 text-sm">
+								{futureDate.toLocaleDateString("en-US", options)}
+							</span>
+						)}
 					</a>
 				);
 			})}

src/assets/images/changelog/dlp/ai-prompt-log.png

@@ -0,0 +1,22 @@
+---
+title: D1 automatically retries read-only queries
+description: D1 now detects read-only queries and automatically attempts up to two retries to execute those queries in the event of failures with retryable errors.
+products:
+  - d1
+  - workers
+date: 2025-09-11
+---
+
+D1 now detects read-only queries and automatically attempts up to two retries to execute those queries in the event of failures with retryable errors. You can access the number of execution attempts in the returned [response metadata](/d1/worker-api/return-object/#d1result) property `total_attempts`.
+
+At the moment, only read-only queries are retried, that is, queries containing only the following SQLite keywords: `SELECT`, `EXPLAIN`, `WITH`. Queries containing any [SQLite keyword](https://sqlite.org/lang_keywords.html) that leads to database writes are not retried.
+
+The retry success ratio among read-only retryable errors varies from 5% all the way up to 95%, depending on the underlying error and its duration (like network errors or other internal errors).
+
+The retry success ratio among all retryable errors is lower, indicating that there are write-queries that could be retried. Therefore, we recommend D1 users to continue applying [retries in their own code](/d1/best-practices/retry-queries/) for queries that are not read-only but are idempotent according to the business logic of the application.
+
+![D1 automatically query retries success ratio](~/assets/images/changelog/d1/d1-auto-retry-success-ratio.png)
+
+D1 ensures that any retry attempt does not cause database writes, making the automatic retries safe from side-effects, even if a query causing changes slips through the read-only detection. D1 achieves this by checking for modifications after every query execution, and if any write occurred due to a retry attempt, the query is rolled back.
+
+The read-only query detection heuristics are simple for now, and there is room for improvement to capture more cases of queries that can be retried, so this is just the beginning.

src/assets/images/changelog/dlp/ai-prompt-policy.png

@@ -0,0 +1,37 @@
+---
+title: "New DLP topic based detection entries for AI prompt protection"
+description: Analyze and secure user prompts to popular generative AI services with new, DLP topic classifications.
+date: 2025-08-25
+---
+
+You now have access to a comprehensive suite of capabilities to secure your organization's use of generative AI. AI prompt protection introduces four key features that work together to provide deep visibility and granular control.
+
+1. **Prompt Detection for AI Applications**
+
+DLP can now natively detect and inspect user prompts submitted to popular AI applications, including **Google Gemini**, **ChatGPT**, **Claude**, and **Perplexity**.
+
+2. **Prompt Analysis and Topic Classification**
+
+Our DLP engine performs deep analysis on each prompt, applying [topic classification](/cloudflare-one/policies/data-loss-prevention/detection-entries/#ai-prompt-topics). These topics are grouped into two evaluation categories:
+
+        - **Content:** PII, Source Code, Credentials and Secrets, Financial Information, and Customer Data.
+
+        - **Intent:** Jailbreak attempts, requests for malicious code, or attempts to extract PII.
+
+To help you apply these topics quickly, we have also released five new predefined profiles (for example, AI Prompt: AI Security, AI Prompt: PII) that bundle these new topics.
+
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-detection-entry.png)
+
+3. **Granular Guardrails**
+
+    You can now build guardrails using Gateway HTTP policies with [application granular controls](/cloudflare-one/policies/gateway/http-policies/#application-granular-controls). Apply a DLP profile containing an [AI prompt topic detection](/cloudflare-one/policies/data-loss-prevention/detection-entries/#ai-prompt-topics) to individual AI applications (for example, ```ChatGPT```) and specific user actions (for example, ```SendPrompt```) to block sensitive prompts.
+
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-policy.png)
+
+ 4. **Full Prompt Logging**
+   
+    To aid in incident investigation, an optional setting in your Gateway policy allows you to [capture prompt logs](/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options/#log-generative-ai-prompt-content) to store the full interaction of prompts that trigger a policy match. To make investigations easier, logs can be filtered by ```conversation_id```, allowing you to reconstruct the full context of an interaction that led to a policy violation.
+
+    ![DLP](~/assets/images/changelog/dlp/ai-prompt-log.png)
+
+AI prompt protection is now available in open beta. To learn more about it, read the [blog](https://blog.cloudflare.com/ai-prompt-protection/#closing-the-loop-logging) or refer to [AI prompt topics](/cloudflare-one/policies/data-loss-prevention/detection-entries/#ai-prompt-topics).