Cloudflare Workers Cache is no longer private beta (withastro#14198)

Author: ascorbic

src/content/docs/en/guides/caching.mdx

@@ -38,7 +38,7 @@ If you deploy to Netlify, Vercel, or Cloudflare, you can use their respective ad
 
 Astro's first-party adapters for Netlify, Vercel, and Cloudflare each provide an experimental CDN cache provider that maps cache directives to the platform's native cache headers and invalidation API. Rather than storing responses in memory, these push your caching directives to the host's edge network, and cache hits are served straight from the CDN without invoking your server function.
 
-During the experimental phase these providers need to be manually enabled, as shown below. In a future release, the Netlify and Vercel providers will be enabled automatically by their adapters. The Cloudflare provider requires a feature that is currently in private beta.
+During the experimental phase these providers need to be manually enabled, as shown below. In a future release, they will be enabled automatically by their adapters.
 
 Each provider automatically tags cached responses with the request path, so [`cache.invalidate({ path })`](/en/reference/api-reference/#cacheinvalidate) works on platforms that only support tag-based purges.
 
@@ -97,10 +97,6 @@ The provider sets `Vercel-CDN-Cache-Control` and `Vercel-Cache-Tag` headers. Bot
 <Since pkg="@astrojs/cloudflare" v="14.0.0" />
 </p>
 
-:::caution[Private beta]
-The Cloudflare provider requires the Cloudflare Workers Cache feature, which is currently in private beta. Without beta access, the headers are ignored and calling `cache.invalidate()` will throw an error.
-:::
-
 Import `cacheCloudflare()` from `@astrojs/cloudflare/cache` and set it as your cache provider:
 
 ```js title="astro.config.mjs" ins={3, 7-9}
@@ -116,7 +112,9 @@ export default defineConfig({
 });
 ```
 
-The provider sets `Cloudflare-CDN-Cache-Control` and `Cache-Tag` headers. The adapter enables Worker caching automatically when a Cloudflare cache provider is configured. Both tag-based and path-based invalidation are supported.
+The provider sets `Cloudflare-CDN-Cache-Control` and `Cache-Tag` headers. Both tag-based and path-based invalidation are supported.
+
+The adapter enables the Cloudflare [Workers Cache](https://developers.cloudflare.com/workers/cache/) with default settings when a Cloudflare cache provider is used. You can [change the configuration](https://developers.cloudflare.com/workers/cache/configuration/) if needed, for example if you want to preserve the cache when you deploy a new version of the site.
 
 ## Interacting with the cache