[Chore] Remove large assets from older changelog entries

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

@@ -9,8 +9,6 @@ date: 2025-04-07
 
 [AutoRAG](/ai-search/) 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/ai-search/autorag-open-beta.gif)
-
 With AutoRAG, you can:
 
 - **Customize your pipeline:** Choose from [Workers AI](/workers-ai) models, configure chunking strategies, edit system prompts, and more.

src/content/changelog/ai-search/2025-07-08-autorag-jobs-view.mdx

@@ -16,10 +16,8 @@
 - Inspect real-time logs of job events (e.g. `Starting indexing data source...`)
 - See a history of past indexing jobs under the Jobs tab of your AutoRAG
 
-![AutoRAG jobs](~/assets/images/changelog/ai-search/autorag-jobs-view.gif)
-
 This makes it easier to understand what’s happening behind the scenes.
 
 **Coming soon:** We’re adding APIs to programmatically check indexing status, making it even easier to integrate AutoRAG into your workflows.
 
 Try it out today on the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/ai/autorag).

src/content/changelog/browser-rendering/2025-07-22-br-local-dev.mdx

@@ -8,6 +8,4 @@ date: 2025-07-22T11:00:00Z
 
 You can now run your Browser Rendering locally using `npx wrangler dev`, which spins up a browser directly on your machine before deploying to Cloudflare's global network. By running tests locally, you can quickly develop, debug, and test changes without needing to deploy or worry about usage costs.
 
-![Local Dev video](~/assets/images/browser-rendering//localshorterbrowserrendering.gif)
-
 Get started with this [example guide](/browser-rendering/workers-bindings/screenshots/) that shows how to use Cloudflare's [fork of Puppeteer](/browser-rendering/puppeteer/) (you can also use [Playwright](/browser-rendering/playwright/)) to take screenshots of webpages and store the results in [Workers KV](/kv/).

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

@@ -11,5 +11,3 @@ Now, you no longer need to navigate multiple pages to manually create an R2 buck
 This enhancement makes it easier for customers to adopt Logpush and R2.
 
 For more details refer to our [Logs](/logs/logpush/logpush-job/enable-destinations/r2/) documentation.
-
-![One-click Logpush to R2](src/assets/images/changelog/logs/Oneclick.gif)

src/content/changelog/rules/2025-01-09-rules-overview.mdx

@@ -8,8 +8,6 @@ date: 2025-01-09
 
 **Rules Overview** gives you a single page to manage all your [Cloudflare Rules](/rules/).
 
-![Rules Overview Interface](~/assets/images/changelog/rules/rules-overview.gif)
-
 What you can do:
 
 - **See all your rules in one place** – No more clicking around.

src/content/changelog/rules/2025-04-24-custom-errors-ga.mdx

@@ -18,6 +18,4 @@ What's new:
 - **Refreshed UI and new name for Error Pages** – Formerly known as “Custom Pages,” Error Pages now offer a cleaner, more intuitive experience for both zone and account-level configurations.
 - **Powered by Ruleset Engine** – Custom Error Rules support [conditional logic](/ruleset-engine/rules-language/) and override Error Pages for 500 and 1000 class errors, as well as errors originating from your origin or [other Cloudflare products](/ruleset-engine/reference/phases-list/). You can also configure [Response Header Transform Rules](/rules/transform/response-header-modification/) to add, change, or remove HTTP headers from responses returned by Custom Error Rules.
 
-![Custom Errors GA](~/assets/images/changelog/rules/custom-errors.gif)
-
 Learn more in the [Custom Errors documentation](/rules/custom-errors/).

src/content/changelog/rules/2025-05-30-configuration-rules-webp.mdx

@@ -12,8 +12,6 @@ You can now enable [Polish](/images/polish/activate-polish/) with the `webp` for
 
 - [WebP](/images/polish/compression/#webp) is now a supported [value](/rules/configuration-rules/settings/#polish) in the **Polish** setting for Configuration Rules.
 
-![New webp option in Polish setting of Configuration Rules](~/assets/images/changelog/rules/configuration-rules-webp.gif)
-
 This gives you more precise control over how images are compressed and delivered, whether you're targeting modern browsers, running experiments, or tailoring performance by geography or device type.
 
 Learn more in the [Polish](/images/polish/) and [Configuration Rules](/rules/configuration-rules/) documentation.

src/content/changelog/workers/2025-03-17-rerun-build.mdx

@@ -9,9 +9,7 @@
 
 You can now retry your Cloudflare Pages and Workers builds directly from GitHub. No need to switch to the Cloudflare Dashboard for a simple retry!
 
-![Workers Builds GitHub Reruns](src/assets/images/changelog/workers/builds-rerun.gif)
-
-Let’s say you push a commit, but your build fails due to a spurious error like a network timeout. Instead of going to the Cloudflare Dashboard to manually retry, you can now rerun the build with just a few clicks inside GitHub, keeping you inside your workflow.
+Let\u2019s say you push a commit, but your build fails due to a spurious error like a network timeout. Instead of going to the Cloudflare Dashboard to manually retry, you can now rerun the build with just a few clicks inside GitHub, keeping you inside your workflow.
 
 For Pages and Workers projects connected to a GitHub repository:
 

src/content/changelog/workers/2025-03-22-next-js-vulnerability-waf.mdx

@@ -9,13 +9,12 @@
 ---
 
 import { Image } from "astro:assets";
-import managedRuleNextJsAuth from "~/assets/images/changelog/workers/high-res-CVE-2025-29927.gif";
 
 **Update: Mon Mar 24th, 11PM UTC**: Next.js has made further changes to address a smaller vulnerability introduced in the patches made to its middleware handling. Users should upgrade to Next.js versions `15.2.4`, `14.2.26`, `13.5.10` or `12.3.6`. **If you are unable to immediately upgrade or are running an older version of Next.js, you can enable the WAF rule described in this changelog as a mitigation**.
 
 **Update: Mon Mar 24th, 8PM UTC**: Next.js has now [backported the patch for this vulnerability](https://github.com/advisories/GHSA-f82v-jwr5-mffw) to cover Next.js v12 and v13. Users on those versions will need to patch to `13.5.9` and `12.3.5` (respectively) to mitigate the vulnerability.
 
 **Update: Sat Mar 22nd, 4PM UTC**: We have changed this WAF rule to opt-in only, as sites that use auth middleware with third-party auth vendors were observing failing requests.
 
 **We strongly recommend updating your version of Next.js (if eligible)** to the patched versions, as your app will otherwise be vulnerable to an authentication bypass attack regardless of auth provider.
 
@@ -28,18 +27,11 @@
 1. Head to Security > WAF > Managed rules in the Cloudflare dashboard for the zone (website) you want to protect.
 2. Click the three dots next to **Cloudflare Managed Ruleset** and choose **Edit**
 3. Scroll down and choose **Browse Rules**
 4. Search for **CVE-2025-29927** (ruleId: `34583778093748cc83ff7b38f472013e`)
 5. Change the **Status** to **Enabled** and the **Action** to **Block**. You can optionally set the rule to Log, to validate potential impact before enabling it. Log will not block requests.
 6. Click **Next**
 7. Scroll down and choose **Save**
 
-<Image
-	src={managedRuleNextJsAuth}
-	alt="Enable the CVE-2025-29927 rule"
-	width="1280"
-	height="1039"
-/>
-
 This will enable the WAF rule and block requests with the `x-middleware-subrequest` header regardless of Next.js version.
 
 ### Create a WAF rule (manual)
@@ -63,13 +55,13 @@
 
 ### Next.js CVE-2025-29927
 
 We've made a WAF (Web Application Firewall) rule available to all sites on Cloudflare to protect against the [Next.js authentication bypass vulnerability](https://github.com/advisories/GHSA-f82v-jwr5-mffw) (`CVE-2025-29927`) published on March 21st, 2025.
 
 **Note**: This rule is not enabled by default as it blocked requests across sites for specific authentication middleware.
 
 - This managed rule protects sites using Next.js on Workers and Pages, as well as sites using Cloudflare to protect Next.js applications hosted elsewhere.
 - This rule has been made available (but not enabled by default) to all sites as part of our [WAF Managed Ruleset](/waf/managed-rules/reference/cloudflare-managed-ruleset/) and blocks requests that attempt to bypass authentication in Next.js applications.
 - The vulnerability affects almost all Next.js versions, and has been fully patched in Next.js `14.2.26` and `15.2.4`. Earlier, interim releases did not fully patch this vulnerability.
 - **Users on older versions of Next.js (`11.1.4` to `13.5.6`) did not originally have a patch available**, but this the patch for this vulnerability and a subsequent additional patch have been backported to Next.js versions `12.3.6` and `13.5.10` as of Monday, March 24th. Users on Next.js v11 will need to deploy the stated workaround or enable the WAF rule.
 
 The managed WAF rule mitigates this by blocking _external_ user requests with the `x-middleware-subrequest` header regardless of Next.js version, but we recommend users using Next.js 14 and 15 upgrade to the patched versions of Next.js as an additional mitigation.

src/content/changelog/workers/2025-08-01-containers-in-vite-dev.mdx

@@ -77,8 +77,6 @@ vite dev
 
 in your terminal.
 
-![Local Dev video](~/assets/images/workers/changelog/worker-with-containers-in-vite.gif)
-
 #### Resources
 
-Learn more about [Cloudflare Containers](https://developers.cloudflare.com/containers/) or the [Cloudflare Vite plugin](https://developers.cloudflare.com/workers/vite-plugin/) in our developer docs.
+Learn more about [Cloudflare Containers](https://developers.cloudflare.com/containers/) or the [Cloudflare Vite plugin](https://developers.cloudflare.com/workers/vite-plugin/) in our developer docs.