From cf74f7c70d703b6c5074a8d25d35c727ce68452c Mon Sep 17 00:00:00 2001
From: kodster28 <kody@cloudflare.com>
Date: Tue, 15 Jul 2025 10:51:31 -0500
Subject: [PATCH 1/4] [Chore] Remove timestamps from changelogs

---
 ...-01-ssh-with-access-for-infrastructure.mdx |  3 +-
 .../2025-01-15-ssh-logs-and-logpush.mdx       |  2 +-
 ...-saml-oidc-fields-saml-transformations.mdx |  2 +-
 .../2025-04-09-SCIM-provisioning-logs.mdx     |  2 +-
 .../2025-04-21-Access-Bulk-Policy-Tester.mdx  |  3 +-
 ...2025-07-01-browser-based-rdp-open-beta.mdx |  4 +-
 .../agents/2025-02-14-example-ai-prompts.mdx  |  2 +-
 .../agents/2025-02-25-agents-sdk.mdx          |  4 +-
 .../agents/2025-03-18-npm-i-agents.mdx        |  2 +-
 ...5-04-07-mcp-servers-agents-sdk-updates.mdx |  2 +-
 .../2025-06-24-announcing-sandboxes.mdx       | 10 +--
 .../ai-audit/2024-09-23-ai-audit-launch.mdx   |  2 +-
 .../ai-audit/2025-07-01-pay-per-crawl.mdx     |  4 +-
 .../changelog/ai-audit/2025-07-01-refresh.mdx |  2 +-
 .../2025-01-07-aig-provider-deepseek.mdx      |  2 +-
 .../2025-01-26-worker-binding-methods.mdx     |  2 +-
 ...-aig-provider-cartesia-eleven-cerebras.mdx |  5 +-
 .../2025-02-05-aig-request-handling.mdx       |  2 +-
 .../ai-gateway/2025-02-26-guardrails.mdx      |  2 +-
 .../ai-gateway/2025-03-20-websockets.mdx      |  2 +-
 ...5-06-03-aig-openai-compatible-endpoint.mdx | 19 ++---
 .../2025-05-23-graphql-api-explorer.mdx       |  2 +-
 .../2025-03-18-api-posture-management.mdx     | 14 ++--
 ...3-27-automatic-audit-logs-beta-release.mdx |  4 +-
 .../autorag/2025-04-07-autorag-open-beta.mdx  |  2 +-
 .../2025-04-23-autorag-metadata-filtering.mdx |  2 +-
 ...19-autorag-custom-metadata-and-context.mdx | 26 +++----
 .../2025-06-19-autorag-filename-filter.mdx    | 20 +++---
 .../autorag/2025-07-08-autorag-jobs-view.mdx  |  8 +--
 .../2025-03-03-user-action-logging.mdx        |  2 +-
 ...01-30-browser-rendering-more-instances.mdx |  2 +-
 .../2025-02-27-br-rest-api-beta.mdx           |  2 +-
 .../2025-04-04-playwright-beta.mdx            | 59 +++++++--------
 .../2025-04-07-br-free-ga-playwright.mdx      |  2 +-
 .../2025-05-28-playwright-mcp.mdx             | 12 ++--
 ...sier-onboarding-for-csam-scanning-tool.mdx |  2 +-
 .../cache/2025-04-01-purge-for-all.mdx        | 12 ++--
 .../2024-11-22-cloud-data-extraction-aws.mdx  |  2 +-
 ...5-04-30-zero-trust-dashboard-dark-mode.mdx |  2 +-
 .../cloudflare-one/access-analytics-v2.mdx    |  4 +-
 .../cloudflare-one/dashboards-access-report   |  2 +-
 .../cloudflare-one/gateway-analytics-v2       |  4 +-
 .../2024-12-19-diagnostic-logs.mdx            |  2 +-
 .../d1/2025-01-07-d1-faster-query.mdx         |  4 +-
 .../2025-04-10-d1-read-replication-beta.mdx   |  2 +-
 .../d1/2025-05-30-d1-rest-api-latency.mdx     |  4 +-
 ...loudflare-one-device-health-monitoring.mdx |  3 +-
 ...025-01-03-source-code-confidence-level.mdx |  2 +-
 .../dlp/2025-04-14-icd11-support.mdx          |  2 +-
 .../dlp/2025-05-07-forensic-copy-update.mdx   |  3 +-
 .../dlp/2025-05-12-case-sensitive-cwl.mdx     |  2 +-
 .../dns/2025-02-02-removed-meta-fields.mdx    |  2 +-
 .../2025-06-03-shopify-o2o-improvements.mdx   |  2 +-
 .../dns/2025-06-11-nsec3-support.mdx          |  2 +-
 .../dns/2025-06-16-internal-dns-beta-ui.mdx   |  2 +-
 ...-06-23-account-level-dns-analytics-api.mdx |  8 +--
 .../2025-04-07-durable-objects-free-tier.mdx  |  2 +-
 ...025-04-07-sqlite-in-durable-objects-ga.mdx |  6 +-
 .../2025-06-25-actors-package-alpha.mdx       |  6 +-
 .../email-routing/2025-03-12-reply-limits.mdx | 71 +++++++++++--------
 .../2025-04-08-local-development.mdx          | 54 +++++++-------
 .../2025-06-30-mail-authentication.mdx        |  4 +-
 .../2024-12-19-reclassification-tab.mdx       |  2 +-
 ...pen-attachments-with-browser-isolation.mdx |  6 +-
 ...025-05-15-open-links-browser-isolation.mdx |  2 +-
 ...5-03-21-resource-force-replacement-bug.mdx |  4 +-
 .../2025-03-21-sensitive-values-redacted.mdx  |  2 +-
 ...5-02-13-improvements-unscannable-files.mdx |  2 +-
 .../2025-03-21-pdns-user-locations-role.mdx   |  2 +-
 ...tp-redirect-custom-block-page-redirect.mdx |  2 +-
 ...5-04-28-FDQN-Filtering-Egress-Policies.mdx |  5 +-
 .../2025-05-13-new-applications-added.mdx     | 14 ++--
 ...025-05-14-domain-category-improvements.mdx | 31 ++++----
 ...-05-27-Protocol-Detection-availability.mdx |  2 +-
 .../2025-06-17-new-order-of-enforcement.mdx   | 18 +++--
 .../2024-12-11-hyperdrive-caching-at-edge.mdx |  2 +-
 ...tomated-private-database-configuration.mdx |  2 +-
 ...ling-near-database-and-ip-range-egress.mdx |  2 +-
 .../2025-04-08-hyperdrive-free-plan.mdx       |  4 +-
 .../2025-04-08-hyperdrive-mysql-support.mdx   |  2 +-
 ...-hyperdrive-custom-certificate-support.mdx |  2 +-
 .../2025-05-14-hyperdrive-fedramp.mdx         |  2 +-
 ...perdrive-configurable-connection-count.mdx |  2 +-
 .../2025-02-21-images-bindings-in-workers.mdx |  2 +-
 ...5-01-27-kv-increased-namespaces-limits.mdx |  2 +-
 .../changelog/kv/2025-04-10-kv-bulk-reads.mdx |  2 +-
 .../2025-06-18-log-explorer-ga.mdx            |  8 +--
 .../logs/2025-03-06-oneclick-logpush.mdx      |  6 +-
 ...8-custom-fields-raw-transformed-values.mdx |  2 +-
 .../2024-12-05-cloud-onramp-terraform.mdx     |  2 +-
 .../2024-10-02-custom-rule-search.mdx         |  2 +-
 .../2024-09-24-magic-network-monitoring.mdx   |  2 +-
 .../2025-02-14-local-console-access.mdx       |  2 +-
 .../2024-12-17-bgp-support-cni.mdx            |  2 +-
 .../2025-04-10-launching-pipelines.mdx        |  2 +-
 ...-14-r2-super-slurper-faster-migrations.mdx |  2 +-
 ...r2-super-slurper-s3-compatible-support.mdx |  2 +-
 .../r2/2025-03-06-r2-bucket-locks.mdx         |  2 +-
 .../r2/2025-04-10-r2-data-catalog-beta.mdx    |  2 +-
 .../r2/2025-05-01-r2-dashboard-updates.mdx    |  5 +-
 .../radar/2025-02-04-radar-ai-insights.mdx    |  2 +-
 .../radar/2025-02-27-radar-dns-insights.mdx   |  3 +-
 ...3-18-radar-leaked-credentials-insights.mdx |  3 +-
 .../radar/2025-07-01-radar-bots-insights.mdx  | 18 ++---
 .../2024-06-17-okta-risk-exchange.mdx         |  2 +-
 .../rules/2024-09-05-rules-templates.mdx      |  3 +-
 .../2024-10-23-url-rewrites-wildcard.mdx      |  3 +-
 .../rules/2024-11-22-cloud-connector-r2.mdx   |  2 +-
 .../rules/2024-12-11-terraform-snippets.mdx   |  4 +-
 .../rules/2025-01-09-rules-overview.mdx       |  2 +-
 .../rules/2025-01-29-snippets-code-editor.mdx |  3 +-
 .../rules/2025-02-11-custom-errors-beta.mdx   |  2 +-
 .../2025-02-12-rules-upgraded-limits.mdx      | 24 +------
 .../rules/2025-04-09-snippets-ga.mdx          |  2 +-
 .../rules/2025-04-24-custom-errors-ga.mdx     |  5 +-
 ...s-cloud-connector-lists-waf-bot-scores.mdx |  5 +-
 .../2025-05-30-configuration-rules-webp.mdx   |  5 +-
 ...-09-custom-errors-fetch-4xx-5xx-assets.mdx |  5 +-
 ...-09-transform-rule-subrequest-matching.mdx |  2 +-
 .../2025-05-07-url-scanner-geoegress.mdx      |  7 +-
 ...-14-cert-bundling-for-custom-hostnames.mdx | 11 +--
 .../ssl/2025-04-09-secrets-store-beta.mdx     | 16 ++---
 .../ssl/2025-05-19-paygo-updates.mdx          | 10 +--
 ...tream-generated-captions-new-languages.mdx |  2 +-
 ...-02-14-introducing-dvr-for-stream-live.mdx |  4 +-
 .../2025-03-06-media-transformations.mdx      |  8 +--
 .../2025-04-14-webrtc-beta-signed-urls.mdx    |  2 +-
 ...ia-transformations-origin-restrictions.mdx |  2 +-
 ...-media-transformations-limits-increase.mdx |  2 +-
 .../2025-05-08-improved-payload-logging.mdx   |  2 +-
 .../2025-07-07-increased-ip-list-limits.mdx   |  3 +-
 .../2025-02-25-rum-exclude-eu.mdx             |  6 +-
 .../2025-02-20-updated-pricing-docs.mdx       | 10 +--
 .../workers-ai/2025-02-24-context-windows.mdx |  4 +-
 .../workers-ai/2025-02-25-json-mode.mdx       |  2 +-
 .../2025-03-17-new-workers-ai-models.mdx      |  9 +--
 .../2025-03-20-markdown-conversion.mdx        |  2 +-
 ...2025-04-11-new-models-faster-inference.mdx |  2 +-
 ...-01-31-workers-platforms-static-assets.mdx |  6 +-
 .../workers/2024-11-11-cache-no-store.mdx     |  4 +-
 .../workers/2024-12-29-faster-builds.mdx      |  2 +-
 .../2025-01-28-nodejs-compat-improvements.mdx |  2 +-
 .../2025-01-31-html-rewriter-streaming.mdx    |  2 +-
 .../2025-02-03-workers-metrics-revamp.mdx     |  2 +-
 .../2025-02-20-builds-name-conflict.mdx       |  2 +-
 .../workers/2025-02-28-wrangler-v4-rc.mdx     |  2 +-
 .../2025-03-11-process-env-support.mdx        |  2 +-
 .../workers/2025-03-13-wrangler-v4.mdx        |  2 +-
 ...03-14-breakpoint-debugging-with-vitest.mdx |  2 +-
 .../workers/2025-03-17-importable-env.mdx     |  2 +-
 .../workers/2025-03-17-rerun-build.mdx        |  2 +-
 .../2025-03-22-next-js-vulnerability-waf.mdx  | 21 +++---
 ...025-03-22-smart-placement-stablization.mdx |  2 +-
 .../workers/2025-03-25-gzip-source-maps.mdx   | 12 ++--
 .../workers/2025-03-25-higher-cpu-limits.mdx  |  4 +-
 ...2025-04-07-increase-trace-events-limit.mdx |  6 +-
 .../2025-04-08-fullstack-on-workers.mdx       |  5 +-
 .../2025-04-08-nodejs-crypto-and-tls.mdx      |  2 +-
 .../workers/2025-04-08-vite-plugin.mdx        |  2 +-
 .../workers/2025-04-09-qb-workers-logs-ga.mdx |  6 +-
 .../workers/2025-04-09-workers-timing.mdx     |  3 +-
 .../workers/2025-04-15-workers-api-fixes.mdx  |  2 +-
 ...2025-04-22-python-worker-cron-triggers.mdx |  2 +-
 .../2025-05-08-finalization-registry.mdx      |  4 +-
 ...025-05-14-python-worker-durable-object.mdx |  6 +-
 ...2025-05-21-vite-plugin-chrome-devtools.mdx |  3 +-
 ...2025-05-22-handle-request-cancellation.mdx |  3 +-
 ...-03-visualize-your-worker-architecture.mdx | 10 +--
 ...025-06-09-workers-integrations-changes.mdx | 29 ++++----
 .../workers/2025-06-10-default-env-vars.mdx   |  2 +-
 ...2025-06-16-workers-platform-admin-role.mdx |  2 +-
 .../workers/2025-06-17-advanced-routing.mdx   |  2 +-
 .../workers/2025-06-17-open-next-ssrf.mdx     |  2 +-
 ...-06-17-workers-terraform-sdk-api-fixes.mdx |  2 +-
 .../2025-06-18-remote-bindings-beta.mdx       |  2 +-
 ...-blob-size-limits-in-Workers-Analytics.mdx |  2 +-
 ...tPlatformProxy-support-remote-bindings.mdx |  2 +-
 ...-26-vite-plugin-cross-commands-binding.mdx |  6 +-
 ...01-vite-plugin-enhanced-assets-support.mdx |  2 +-
 .../2025-07-04-javascript-debug-terminals.mdx |  2 +-
 .../workflows/2024-10-24-workflows-beta.mdx   | 12 ++--
 ...-02-25-workflows-concurrency-increased.mdx |  6 +-
 .../workflows/2025-04-07-workflows-ga.mdx     |  2 +-
 .../zaraz/2025-02-24-zaraz-dash-placement.mdx |  9 ++-
 .../2024-06-16-cloudflare-one.mdx             |  2 +-
 .../2025-03-17-warp-ga-android.mdx            |  2 +-
 .../2025-03-17-warp-ga-ios.mdx                |  2 +-
 .../2025-06-30-warp-ga-android.mdx            |  8 +--
 .../2025-06-30-warp-ga-ios.mdx                |  6 +-
 189 files changed, 517 insertions(+), 514 deletions(-)

diff --git a/src/content/changelog/access/2024-10-01-ssh-with-access-for-infrastructure.mdx b/src/content/changelog/access/2024-10-01-ssh-with-access-for-infrastructure.mdx
index 16802b25ed8b9b..4f79426817197a 100644
--- a/src/content/changelog/access/2024-10-01-ssh-with-access-for-infrastructure.mdx
+++ b/src/content/changelog/access/2024-10-01-ssh-with-access-for-infrastructure.mdx
@@ -1,7 +1,7 @@
 ---
 title: Eliminate long-lived credentials and enhance SSH security with Cloudflare Access for Infrastructure
 description: Use short-lived SSH certificates and fine-grained policy to secure access to your SSH servers.
-date: 2024-10-01T6:00:00Z
+date: 2024-10-01
 ---
 
 Organizations can now eliminate long-lived credentials from their SSH setup and enable strong multi-factor authentication for SSH access, similar to other Access applications, all while generating access and command logs.
@@ -9,6 +9,7 @@ Organizations can now eliminate long-lived credentials from their SSH setup and
 SSH with [Access for Infrastructure](/cloudflare-one/applications/non-http/infrastructure-apps/) uses short-lived SSH certificates from Cloudflare, eliminating SSH key management and reducing the security risks associated with lost or stolen keys. It also leverages a common deployment model for Cloudflare One customers: [WARP-to-Tunnel](/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-warp-to-tunnel/).
 
 SSH with Access for Infrastructure enables you to:
+
 - **Author fine-grained policy** to control who may access your SSH servers, including specific ports, protocols, and SSH users.
 - **Monitor infrastructure access** with Access and SSH command logs, supporting regulatory compliance and providing visibility in case of security breach.
 - **Preserve your end users' workflows.** SSH with Access for Infrastructure supports native SSH clients and does not require any modifications to users’ SSH configs.
diff --git a/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx b/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx
index 2d8e8b4122c3db..05a1293716d308 100644
--- a/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx
+++ b/src/content/changelog/access/2025-01-15-ssh-logs-and-logpush.mdx
@@ -1,7 +1,7 @@
 ---
 title: Export SSH command logs with Access for Infrastructure using Logpush
 description: Easily configure automatic export of SSH command logs to third-party storage destinations or to security information and event management (SIEM) tools.
-date: 2025-01-15T6:00:00Z
+date: 2025-01-15
 ---
 
 :::note[Availability]
diff --git a/src/content/changelog/access/2025-03-03-saml-oidc-fields-saml-transformations.mdx b/src/content/changelog/access/2025-03-03-saml-oidc-fields-saml-transformations.mdx
index d83d3d8c19e089..1fadb777158e9a 100644
--- a/src/content/changelog/access/2025-03-03-saml-oidc-fields-saml-transformations.mdx
+++ b/src/content/changelog/access/2025-03-03-saml-oidc-fields-saml-transformations.mdx
@@ -1,7 +1,7 @@
 ---
 title: New SAML and OIDC Fields and SAML transforms for Access for SaaS
 description: Access for SaaS new SAML and OIDC Fields and SAML transforms
-date: 2025-03-03T6:00:00Z
+date: 2025-03-03
 ---
 
 [Access for SaaS applications](/cloudflare-one/applications/configure-apps/saas-apps/) now include more configuration options to support a wider array of SaaS applications.
diff --git a/src/content/changelog/access/2025-04-09-SCIM-provisioning-logs.mdx b/src/content/changelog/access/2025-04-09-SCIM-provisioning-logs.mdx
index f7518b245c6982..3381246069b2da 100644
--- a/src/content/changelog/access/2025-04-09-SCIM-provisioning-logs.mdx
+++ b/src/content/changelog/access/2025-04-09-SCIM-provisioning-logs.mdx
@@ -1,7 +1,7 @@
 ---
 title: Cloudflare Zero Trust SCIM User and Group Provisioning Logs
 description: View all user and group updates, creation and deletion events made via SCIM across all of your IdP instances in one place
-date: 2025-04-09T6:00:00Z
+date: 2025-04-09
 ---
 
 [Cloudflare Zero Trust SCIM provisioning](/cloudflare-one/identity/users/scim) now has a full audit log of all create, update and delete event from any SCIM Enabled IdP. The [SCIM logs](/cloudflare-one/insights/logs/scim-logs/) support filtering by IdP, Event type, Result and many more fields. This will help with debugging user and group update issues and questions.
diff --git a/src/content/changelog/access/2025-04-21-Access-Bulk-Policy-Tester.mdx b/src/content/changelog/access/2025-04-21-Access-Bulk-Policy-Tester.mdx
index ef667aa74a07b4..da2d70898c78a1 100644
--- a/src/content/changelog/access/2025-04-21-Access-Bulk-Policy-Tester.mdx
+++ b/src/content/changelog/access/2025-04-21-Access-Bulk-Policy-Tester.mdx
@@ -1,10 +1,9 @@
 ---
 title: Access bulk policy tester
 description: Test and simulate Access policies before deploying them to production. The Access bulk policy tester allows you to test your policies against your entire user population before and after deploying them.
-date: 2025-04-21T6:00:00Z
+date: 2025-04-21
 ---
 
 The [Access bulk policy tester](/cloudflare-one/policies/access/policy-management/#test-all-policies-in-an-application) is now available in the Cloudflare Zero Trust dashboard. The bulk policy tester allows you to simulate Access policies against your entire user base before and after deploying any changes. The policy tester will simulate the configured policy against each user's last seen identity and device posture (if applicable).
 
 ![Example policy tester](~/assets/images/changelog/access/example-policy-tester.png)
-
diff --git a/src/content/changelog/access/2025-07-01-browser-based-rdp-open-beta.mdx b/src/content/changelog/access/2025-07-01-browser-based-rdp-open-beta.mdx
index d793afd0591c42..4a1287b0744a04 100644
--- a/src/content/changelog/access/2025-07-01-browser-based-rdp-open-beta.mdx
+++ b/src/content/changelog/access/2025-07-01-browser-based-rdp-open-beta.mdx
@@ -1,12 +1,13 @@
 ---
 title: Access RDP securely from your browser — now in open beta
 description: Connect to internal Windows servers via a web browser — no VPN or RDP client required.
-date: 2025-07-01T13:00:00Z
+date: 2025-07-01
 ---
 
 [Browser-based RDP](/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser/) with [Cloudflare Access](/cloudflare-one/policies/access/) is now available in open beta for all Cloudflare customers. It enables secure, remote Windows server access without VPNs or RDP clients.
 
 With browser-based RDP, you can:
+
 - **Control how users authenticate to internal RDP resources** with single sign-on (SSO), multi-factor authentication (MFA), and granular access policies.
 - **Record who is accessing which servers and when** to support regulatory compliance requirements and to gain greater visibility in the event of a security event.
 - **Eliminate the need to install and manage software on user devices**. You will only need a web browser.
@@ -15,4 +16,3 @@ With browser-based RDP, you can:
 ![Example of a browsed-based RDP Access application](~/assets/images/changelog/access/browser-based-rdp-access-app.png)
 
 To get started, see [Connect to RDP in a browser](/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser/).
-
diff --git a/src/content/changelog/agents/2025-02-14-example-ai-prompts.mdx b/src/content/changelog/agents/2025-02-14-example-ai-prompts.mdx
index b979df67b5b02d..144dd441b3fa7e 100644
--- a/src/content/changelog/agents/2025-02-14-example-ai-prompts.mdx
+++ b/src/content/changelog/agents/2025-02-14-example-ai-prompts.mdx
@@ -5,7 +5,7 @@ products:
   - agents
   - workers
   - workflows
-date: 2025-02-14T19:00:00Z
+date: 2025-02-14
 ---
 
 We've added an [example prompt](/workers/get-started/prompting/) to help you get started with building AI agents and applications on Cloudflare [Workers](/workers/), including [Workflows](/workflows/), [Durable Objects](/durable-objects/), and [Workers KV](/kv/).
diff --git a/src/content/changelog/agents/2025-02-25-agents-sdk.mdx b/src/content/changelog/agents/2025-02-25-agents-sdk.mdx
index 26d5a5b4eca3c9..ff4c10d1f19d5f 100644
--- a/src/content/changelog/agents/2025-02-25-agents-sdk.mdx
+++ b/src/content/changelog/agents/2025-02-25-agents-sdk.mdx
@@ -4,7 +4,7 @@ description: Build and ship AI Agents on Cloudflare using the Agents SDK
 products:
   - agents
   - workers
-date: 2025-02-25T14:00:00Z
+date: 2025-02-25
 ---
 
 We've released the [Agents SDK](http://blog.cloudflare.com/build-ai-agents-on-cloudflare/), a package and set of tools that help you build and ship AI Agents.
@@ -25,7 +25,7 @@ npm i agents
 ... and then define your first Agent:
 
 ```ts
-import { Agent } from 'agents';
+import { Agent } from "agents";
 
 export class YourAgent extends Agent<Env> {
 	// Build it out
diff --git a/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx b/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx
index 69577dcca4d74f..fec5ce9351eca4 100644
--- a/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx
+++ b/src/content/changelog/agents/2025-03-18-npm-i-agents.mdx
@@ -4,7 +4,7 @@ description: Install the latest version of the `agents` SDK to build multi-agent
 products:
   - agents
   - workers
-date: 2025-03-18T14:00:00Z
+date: 2025-03-18
 ---
 
 import { Badge, MetaInfo, Render, TypeScriptExample } from "~/components"
diff --git a/src/content/changelog/agents/2025-04-07-mcp-servers-agents-sdk-updates.mdx b/src/content/changelog/agents/2025-04-07-mcp-servers-agents-sdk-updates.mdx
index 7a61e2c68e3722..4008b08537050a 100644
--- a/src/content/changelog/agents/2025-04-07-mcp-servers-agents-sdk-updates.mdx
+++ b/src/content/changelog/agents/2025-04-07-mcp-servers-agents-sdk-updates.mdx
@@ -4,7 +4,7 @@ description: The Agents SDK now includes built-in support for building remote MC
 products:
   - agents
   - workers
-date: 2025-04-07T13:00:00Z
+date: 2025-04-07
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/agents/2025-06-24-announcing-sandboxes.mdx b/src/content/changelog/agents/2025-06-24-announcing-sandboxes.mdx
index 0058c871e07831..8b454d0be156be 100644
--- a/src/content/changelog/agents/2025-06-24-announcing-sandboxes.mdx
+++ b/src/content/changelog/agents/2025-06-24-announcing-sandboxes.mdx
@@ -5,7 +5,7 @@ products:
   - agents
   - workers
   - workflows
-date: 2025-06-25T15:00:00Z
+date: 2025-06-25
 ---
 
 AI is supercharging app development for everyone, but we need a safe way to run untrusted, LLM-written code. We’re introducing [Sandboxes](https://www.npmjs.com/package/@cloudflare/sandbox), which let your Worker run actual processes in a secure, container-based environment.
@@ -15,10 +15,10 @@ import { getSandbox } from "@cloudflare/sandbox";
 export { Sandbox } from "@cloudflare/sandbox";
 
 export default {
-  async fetch(request: Request, env: Env) {
-    const sandbox = getSandbox(env.Sandbox, "my-sandbox");
-    return sandbox.exec("ls", ["-la"]);
-  },
+	async fetch(request: Request, env: Env) {
+		const sandbox = getSandbox(env.Sandbox, "my-sandbox");
+		return sandbox.exec("ls", ["-la"]);
+	},
 };
 ```
 
diff --git a/src/content/changelog/ai-audit/2024-09-23-ai-audit-launch.mdx b/src/content/changelog/ai-audit/2024-09-23-ai-audit-launch.mdx
index 317488e0f220cd..262320717928a5 100644
--- a/src/content/changelog/ai-audit/2024-09-23-ai-audit-launch.mdx
+++ b/src/content/changelog/ai-audit/2024-09-23-ai-audit-launch.mdx
@@ -1,7 +1,7 @@
 ---
 title: AI Audit
 description: AI Audit is available to all customers
-date: 2024-09-23T11:00:00Z
+date: 2024-09-23
 ---
 
 Every site on Cloudflare now has access to [**AI Audit**](/ai-audit/), which summarizes the crawling behavior of popular and known AI services.
diff --git a/src/content/changelog/ai-audit/2025-07-01-pay-per-crawl.mdx b/src/content/changelog/ai-audit/2025-07-01-pay-per-crawl.mdx
index 5003f3f80815bd..1e0c3c77eba921 100644
--- a/src/content/changelog/ai-audit/2025-07-01-pay-per-crawl.mdx
+++ b/src/content/changelog/ai-audit/2025-07-01-pay-per-crawl.mdx
@@ -1,7 +1,7 @@
 ---
 title: Introducing Pay Per Crawl (private beta)
 description: A new feature which allows site owners to charge crawlers for access to their content
-date: 2025-07-01T12:00:00Z
+date: 2025-07-01
 ---
 
 We are introducing a new feature of [AI Audit](/ai-audit/) — Pay Per Crawl. [Pay Per Crawl](/ai-audit/features/pay-per-crawl/what-is-pay-per-crawl/) enables site owners to require payment from AI crawlers every time the crawlers access their content, thereby fostering a fairer Internet by enabling site owners to control and monetize how their content gets used by AI.
@@ -9,11 +9,13 @@ We are introducing a new feature of [AI Audit](/ai-audit/) — Pay Per Crawl. [P
 ![Pay per crawl](~/assets/images/changelog/ai-audit/pay-per-crawl.png)
 
 **For Site Owners:**
+
 - Set pricing and select which crawlers to charge for content access
 - Manage payments via Stripe
 - Monitor analytics on successful content deliveries
 
 **For AI Crawler Owners:**
+
 - Use HTTP headers to request and accept pricing
 - Receive clear confirmations on charges for accessed content
 
diff --git a/src/content/changelog/ai-audit/2025-07-01-refresh.mdx b/src/content/changelog/ai-audit/2025-07-01-refresh.mdx
index 6411d73c1fe5c6..a36915e466ac55 100644
--- a/src/content/changelog/ai-audit/2025-07-01-refresh.mdx
+++ b/src/content/changelog/ai-audit/2025-07-01-refresh.mdx
@@ -1,7 +1,7 @@
 ---
 title: AI Audit refresh
 description: More intuitive AI crawler management
-date: 2025-07-01T11:00:00Z
+date: 2025-07-01
 ---
 
 We redesigned the AI Audit dashboard to provide more intuitive and granular control over AI crawlers.
diff --git a/src/content/changelog/ai-gateway/2025-01-07-aig-provider-deepseek.mdx b/src/content/changelog/ai-gateway/2025-01-07-aig-provider-deepseek.mdx
index 591275da715d90..5e178bc515f43c 100644
--- a/src/content/changelog/ai-gateway/2025-01-07-aig-provider-deepseek.mdx
+++ b/src/content/changelog/ai-gateway/2025-01-07-aig-provider-deepseek.mdx
@@ -3,7 +3,7 @@ title: AI Gateway adds DeepSeek as a Provider
 description: AI Gateway has added DeepSeek as a new provider.
 products:
   - ai-gateway
-date: 2025-01-02T11:00:00Z
+date: 2025-01-02
 ---
 
 [**AI Gateway**](/ai-gateway/) now supports [**DeepSeek**](/ai-gateway/providers/deepseek/), including their cutting-edge DeepSeek-V3 model. With this addition, you have even more flexibility to manage and optimize your AI workloads using AI Gateway. Whether you're leveraging DeepSeek or other providers, like OpenAI, Anthropic, or [Workers AI](/workers-ai/), AI Gateway empowers you to:
diff --git a/src/content/changelog/ai-gateway/2025-01-26-worker-binding-methods.mdx b/src/content/changelog/ai-gateway/2025-01-26-worker-binding-methods.mdx
index b38ca35f7a6d7c..171eb5e19c5af0 100644
--- a/src/content/changelog/ai-gateway/2025-01-26-worker-binding-methods.mdx
+++ b/src/content/changelog/ai-gateway/2025-01-26-worker-binding-methods.mdx
@@ -3,7 +3,7 @@ title: AI Gateway Introduces New Worker Binding Methods
 description: New Worker binding methods, enhancing integration capabilities for developers.
 products:
   - ai-gateway
-date: 2025-01-30T14:00:00Z
+date: 2025-01-30
 ---
 
 We have released new [Workers bindings API methods](/ai-gateway/integrations/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate.
diff --git a/src/content/changelog/ai-gateway/2025-02-04-aig-provider-cartesia-eleven-cerebras.mdx b/src/content/changelog/ai-gateway/2025-02-04-aig-provider-cartesia-eleven-cerebras.mdx
index 503eabd47135e8..ea72b5b02b418c 100644
--- a/src/content/changelog/ai-gateway/2025-02-04-aig-provider-cartesia-eleven-cerebras.mdx
+++ b/src/content/changelog/ai-gateway/2025-02-04-aig-provider-cartesia-eleven-cerebras.mdx
@@ -3,12 +3,12 @@ title: AI Gateway adds Cerebras, ElevenLabs, and Cartesia as new providers
 description: AI Gateway has added Cerebras, ElevenLabs, and Cartesia as new providers.
 products:
   - ai-gateway
-date: 2025-02-05T12:00:00Z
+date: 2025-02-05
 ---
 
 [AI Gateway](/ai-gateway/) has added three new providers: [Cartesia](/ai-gateway/providers/cartesia/), [Cerebras](/ai-gateway/providers/cerebras/), and [ElevenLabs](/ai-gateway/providers/elevenlabs/), giving you more even more options for providers you can use through AI Gateway. Here's a brief overview of each:
 
-- [Cartesia](/ai-gateway/providers/cartesia/) provides text-to-speech models that produce natural-sounding speech with low latency. 
+- [Cartesia](/ai-gateway/providers/cartesia/) provides text-to-speech models that produce natural-sounding speech with low latency.
 - [Cerebras](/ai-gateway/providers/cerebras/) delivers low-latency AI inference to Meta's Llama 3.1 8B and Llama 3.3 70B models.
 - [ElevenLabs](/ai-gateway/providers/elevenlabs/) offers text-to-speech models with human-like voices in 32 languages.
 
@@ -30,4 +30,3 @@ curl -X POST https://gateway.ai.cloudflare.com/v1/ACCOUNT_TAG/GATEWAY/cerebras/c
     ]
 }'
 ```
-
diff --git a/src/content/changelog/ai-gateway/2025-02-05-aig-request-handling.mdx b/src/content/changelog/ai-gateway/2025-02-05-aig-request-handling.mdx
index bde707fb403783..63cdcb0f02d0d4 100644
--- a/src/content/changelog/ai-gateway/2025-02-05-aig-request-handling.mdx
+++ b/src/content/changelog/ai-gateway/2025-02-05-aig-request-handling.mdx
@@ -3,7 +3,7 @@ title: Request timeouts and retries with AI Gateway
 description: AI Gateway has added additional request handling, with request timeouts and request retries
 products:
   - ai-gateway
-date: 2025-02-06T11:00:00Z
+date: 2025-02-06
 ---
 
 AI Gateway adds additional ways to handle requests - [Request Timeouts](/ai-gateway/configuration/request-handling/#request-timeouts) and [Request Retries](/ai-gateway/configuration/request-handling/#request-retries), making it easier to keep your applications responsive and reliable.
diff --git a/src/content/changelog/ai-gateway/2025-02-26-guardrails.mdx b/src/content/changelog/ai-gateway/2025-02-26-guardrails.mdx
index e82cf9ce2bf400..497865dcb9e486 100644
--- a/src/content/changelog/ai-gateway/2025-02-26-guardrails.mdx
+++ b/src/content/changelog/ai-gateway/2025-02-26-guardrails.mdx
@@ -1,7 +1,7 @@
 ---
 title: Introducing Guardrails in AI Gateway
 description: Keep AI interactions secure and risk-free with Guardrails in AI Gateway
-date: 2025-02-26T6:00:00Z
+date: 2025-02-26
 preview_image: ~/assets/images/changelog/ai-gateway/guardrails-social-preview.png
 ---
 
diff --git a/src/content/changelog/ai-gateway/2025-03-20-websockets.mdx b/src/content/changelog/ai-gateway/2025-03-20-websockets.mdx
index 09d079f5196baf..d52a0154884ec5 100644
--- a/src/content/changelog/ai-gateway/2025-03-20-websockets.mdx
+++ b/src/content/changelog/ai-gateway/2025-03-20-websockets.mdx
@@ -1,7 +1,7 @@
 ---
 title: AI Gateway launches Realtime WebSockets API
 description: AI Gateway now supports end-to-end, client-to-provider WebSockets
-date: 2025-03-21T09:00:00Z
+date: 2025-03-21
 ---
 
 We are excited to announce that [AI Gateway](/ai-gateway/) now supports real-time AI interactions with the new [Realtime WebSockets API](/ai-gateway/websockets-api/realtime-api/).
diff --git a/src/content/changelog/ai-gateway/2025-06-03-aig-openai-compatible-endpoint.mdx b/src/content/changelog/ai-gateway/2025-06-03-aig-openai-compatible-endpoint.mdx
index e61b6cecc7f491..3acc2212004141 100644
--- a/src/content/changelog/ai-gateway/2025-06-03-aig-openai-compatible-endpoint.mdx
+++ b/src/content/changelog/ai-gateway/2025-06-03-aig-openai-compatible-endpoint.mdx
@@ -3,28 +3,29 @@ title: AI Gateway adds OpenAI compatible endpoint
 description: AI Gateway has added OpenAI compatibility
 products:
   - ai-gateway
-date: 2025-06-03T12:00:00Z
+date: 2025-06-03
 ---
-Users can now use an [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) in AI Gateway to easily switch between providers, while keeping the exact same request and response formats. We're launching now with the chat completions endpoint, with the embeddings endpoint coming up next.  
+
+Users can now use an [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) in AI Gateway to easily switch between providers, while keeping the exact same request and response formats. We're launching now with the chat completions endpoint, with the embeddings endpoint coming up next.
 
 To get started, use the OpenAI compatible chat completions endpoint URL with your own account id and gateway id and switch between providers by changing the `model` and `apiKey` parameters.
 
 ```js title="OpenAI SDK Example"
 import OpenAI from "openai";
 const client = new OpenAI({
-  apiKey: "YOUR_PROVIDER_API_KEY", // Provider API key
-  baseURL:
-    "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat",
+	apiKey: "YOUR_PROVIDER_API_KEY", // Provider API key
+	baseURL:
+		"https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/compat",
 });
 
 const response = await client.chat.completions.create({
-  model: "google-ai-studio/gemini-2.0-flash",
-  messages: [{ role: "user", content: "What is Cloudflare?" }],
+	model: "google-ai-studio/gemini-2.0-flash",
+	messages: [{ role: "user", content: "What is Cloudflare?" }],
 });
 
 console.log(response.choices[0].message.content);
 ```
 
-Additionally, the [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) can be combined with our [Universal Endpoint](/ai-gateway/universal/) to add fallbacks across multiple providers. That means AI Gateway will return every response in the same standardized format, no extra parsing logic required!  
+Additionally, the [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) can be combined with our [Universal Endpoint](/ai-gateway/universal/) to add fallbacks across multiple providers. That means AI Gateway will return every response in the same standardized format, no extra parsing logic required!
 
-Learn more in the [OpenAI Compatibility](/ai-gateway/chat-completion/) documentation. 
+Learn more in the [OpenAI Compatibility](/ai-gateway/chat-completion/) documentation.
diff --git a/src/content/changelog/analytics/2025-05-23-graphql-api-explorer.mdx b/src/content/changelog/analytics/2025-05-23-graphql-api-explorer.mdx
index 9776692a049670..4157e41205f539 100644
--- a/src/content/changelog/analytics/2025-05-23-graphql-api-explorer.mdx
+++ b/src/content/changelog/analytics/2025-05-23-graphql-api-explorer.mdx
@@ -1,7 +1,7 @@
 ---
 title: New GraphQL Analytics API Explorer and MCP Server
 description: Easily explore, build, and run GraphQL queries with two new tools
-date: 2025-05-23T11:00:00Z
+date: 2025-05-23
 ---
 
 We’ve launched two powerful new tools to make the GraphQL Analytics API more accessible:
diff --git a/src/content/changelog/api-shield/2025-03-18-api-posture-management.mdx b/src/content/changelog/api-shield/2025-03-18-api-posture-management.mdx
index dcd5b0669d0d40..8797cc2fb41f96 100644
--- a/src/content/changelog/api-shield/2025-03-18-api-posture-management.mdx
+++ b/src/content/changelog/api-shield/2025-03-18-api-posture-management.mdx
@@ -1,7 +1,7 @@
 ---
 title: New API Posture Management for API Shield
 description: Monitor for API-specific threats and risks with Posture Management for API Shield
-date: 2025-03-18T11:00:00Z
+date: 2025-03-18
 ---
 
 Now, API Shield **automatically** labels your API inventory with API-specific risks so that you can track and manage risks to your APIs.
@@ -10,14 +10,14 @@ View these risks in [Endpoint Management](/api-shield/management-and-monitoring/
 
 ![A list of endpoint management labels](~/assets/images/changelog/api-shield/endpoint-management-label.png)
 
- ...or in [Security Center Insights](/security-center/security-insights/):
+...or in [Security Center Insights](/security-center/security-insights/):
 
 ![An example security center insight](~/assets/images/changelog/api-shield/posture-management-insight.png)
- 
+
 API Shield will scan for risks on your API inventory daily. Here are the new risks we're scanning for and automatically labelling:
 
 - **cf-risk-sensitive**: applied if the customer is subscribed to the [sensitive data detection ruleset](/waf/managed-rules/reference/sensitive-data-detection/) and the WAF detects sensitive data returned on an endpoint in the last seven days.
-- **cf-risk-missing-auth**: applied if the customer has configured a session ID and no successful requests to the endpoint contain the session ID. 
+- **cf-risk-missing-auth**: applied if the customer has configured a session ID and no successful requests to the endpoint contain the session ID.
 - **cf-risk-mixed-auth**: applied if the customer has configured a session ID and some successful requests to the endpoint contain the session ID while some lack the session ID.
 - **cf-risk-missing-schema**: added when a learned schema is available for an endpoint that has no active schema.
 - **cf-risk-error-anomaly**: added when an endpoint experiences a recent increase in response errors over the last 24 hours.
@@ -25,9 +25,9 @@ API Shield will scan for risks on your API inventory daily. Here are the new ris
 - **cf-risk-size-anomaly**: added when an endpoint experiences a spike in response body size over the last 24 hours.
 
 In addition, API Shield has two new 'beta' scans for **Broken Object Level Authorization (BOLA) attacks**. If you're in the beta, you will see the following two labels when API Shield suspects an endpoint is suffering from a BOLA vulnerability:
- 
- - **cf-risk-bola-enumeration**: added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
- - **cf-risk-bola-pollution**: added when an endpoint experiences successful responses where parameters are found in multiple places in the request.
+
+- **cf-risk-bola-enumeration**: added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
+- **cf-risk-bola-pollution**: added when an endpoint experiences successful responses where parameters are found in multiple places in the request.
 
 We are currently accepting more customers into our beta. Contact your account team if you are interested in BOLA attack detection for your API.
 
diff --git a/src/content/changelog/audit-logs/2025-03-27-automatic-audit-logs-beta-release.mdx b/src/content/changelog/audit-logs/2025-03-27-automatic-audit-logs-beta-release.mdx
index 0ce7ae86283dc7..be90d517dc75b2 100644
--- a/src/content/changelog/audit-logs/2025-03-27-automatic-audit-logs-beta-release.mdx
+++ b/src/content/changelog/audit-logs/2025-03-27-automatic-audit-logs-beta-release.mdx
@@ -1,7 +1,7 @@
 ---
 title: Audit logs (version 2) - Beta Release
 description: New version of audit logs
-date: 2025-03-27T11:00:00Z
+date: 2025-03-27
 ---
 The latest version of audit logs streamlines audit logging by automatically capturing all user and system actions performed through the Cloudflare Dashboard or public APIs. This update leverages Cloudflare’s existing API Shield to generate audit logs based on OpenAPI schemas, ensuring a more consistent and automated logging process.
 
@@ -12,7 +12,7 @@ Use the following API endpoint to retrieve audit logs:
 GET https://api.cloudflare.com/client/v4/accounts/<account_id>/logs/audit?since=<date>&before=<date>
 
 ```
-You can access detailed documentation for audit logs (version 2) Beta API release [here](https://developers.cloudflare.com/api/resources/accounts/subresources/logs/subresources/audit/methods/list/). 
+You can access detailed documentation for audit logs (version 2) Beta API release [here](https://developers.cloudflare.com/api/resources/accounts/subresources/logs/subresources/audit/methods/list/).
 
 **Key Improvements in the Beta Release:**
 
diff --git a/src/content/changelog/autorag/2025-04-07-autorag-open-beta.mdx b/src/content/changelog/autorag/2025-04-07-autorag-open-beta.mdx
index b0f2ba9ac1d122..6b51b1735f20fe 100644
--- a/src/content/changelog/autorag/2025-04-07-autorag-open-beta.mdx
+++ b/src/content/changelog/autorag/2025-04-07-autorag-open-beta.mdx
@@ -4,7 +4,7 @@ description: AutoRAG lets you create fully-managed, retrieval-augmented generati
 products:
   - autorag
   - vectorize
-date: 2025-04-07T6:00:00Z
+date: 2025-04-07
 ---
 
 [AutoRAG](/autorag) 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.
diff --git a/src/content/changelog/autorag/2025-04-23-autorag-metadata-filtering.mdx b/src/content/changelog/autorag/2025-04-23-autorag-metadata-filtering.mdx
index 115f977efc1ef9..deb788dda91baa 100644
--- a/src/content/changelog/autorag/2025-04-23-autorag-metadata-filtering.mdx
+++ b/src/content/changelog/autorag/2025-04-23-autorag-metadata-filtering.mdx
@@ -3,7 +3,7 @@ title: Metadata filtering and multitenancy support in AutoRAG
 description: Add metadata filters to AutoRAG queries to enable multitenancy and control the scope of retrieved results.
 products:
   - autorag
-date: 2025-04-23T6:00:00Z
+date: 2025-04-23
 ---
 
 You can now filter [AutoRAG](/autorag) search results by `folder` and `timestamp` using [metadata filtering](/autorag/configuration/metadata) to narrow down the scope of your query.
diff --git a/src/content/changelog/autorag/2025-06-19-autorag-custom-metadata-and-context.mdx b/src/content/changelog/autorag/2025-06-19-autorag-custom-metadata-and-context.mdx
index e2c27e2509f520..eec80f3aad3a41 100644
--- a/src/content/changelog/autorag/2025-06-19-autorag-custom-metadata-and-context.mdx
+++ b/src/content/changelog/autorag/2025-06-19-autorag-custom-metadata-and-context.mdx
@@ -3,12 +3,12 @@ title: View custom metadata in responses and guide AI-search with context in Aut
 description: You can now view custom metadata in AutoRAG search responses and use a context field to provide additional guidance to AI-generated answers.
 products:
   - autorag
-date: 2025-06-19T6:10:00Z
+date: 2025-06-19
 ---
 
 In [AutoRAG](/autorag/), you can now view your object's custom metadata in the response from [`/search`](/autorag/usage/workers-binding/) and [`/ai-search`](/autorag/usage/workers-binding/), and optionally add a `context` field in the custom metadata of an object to provide additional guidance for AI-generated answers.
 
-You can add [custom metadata](/r2/api/workers/workers-api-reference/#r2putoptions) to an object when uploading it to your R2 bucket. 
+You can add [custom metadata](/r2/api/workers/workers-api-reference/#r2putoptions) to an object when uploading it to your R2 bucket.
 
 # Object's custom metadata in search responses
 
@@ -18,15 +18,15 @@ For example, the `attributes` section of your search response may look like:
 
 ```json
 {
-  "attributes": {
-    "timestamp": 1750001460000,
-    "folder": "docs/",
-    "filename": "launch-checklist.md",
-    "file": {
-      "url": "https://wiki.company.com/docs/launch-checklist",
-      "context": "A checklist for internal launch readiness, including legal, engineering, and marketing steps."
-    }
-  }
+	"attributes": {
+		"timestamp": 1750001460000,
+		"folder": "docs/",
+		"filename": "launch-checklist.md",
+		"file": {
+			"url": "https://wiki.company.com/docs/launch-checklist",
+			"context": "A checklist for internal launch readiness, including legal, engineering, and marketing steps."
+		}
+	}
 }
 ```
 
@@ -40,10 +40,10 @@ For example:
 
 ```json
 {
-  "context": "summary: 'Checklist for internal product launch readiness, including legal, engineering, and marketing steps.'; url: 'https://wiki.company.com/docs/launch-checklist'"
+	"context": "summary: 'Checklist for internal product launch readiness, including legal, engineering, and marketing steps.'; url: 'https://wiki.company.com/docs/launch-checklist'"
 }
 ```
 
 This gives you more control over how your content is interpreted, without requiring you to modify the original contents of the file.
 
-Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata).
\ No newline at end of file
+Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata).
diff --git a/src/content/changelog/autorag/2025-06-19-autorag-filename-filter.mdx b/src/content/changelog/autorag/2025-06-19-autorag-filename-filter.mdx
index ce1b6dedd056c9..47b5db599c6ff7 100644
--- a/src/content/changelog/autorag/2025-06-19-autorag-filename-filter.mdx
+++ b/src/content/changelog/autorag/2025-06-19-autorag-filename-filter.mdx
@@ -1,9 +1,9 @@
 ---
-title: Filter your AutoRAG search by file name 
-description: You can now filter AutoRAG search queries by file name, allowing you to control which files can be retrieved for a given query. 
+title: Filter your AutoRAG search by file name
+description: You can now filter AutoRAG search queries by file name, allowing you to control which files can be retrieved for a given query.
 products:
   - autorag
-date: 2025-06-19T6:00:00Z
+date: 2025-06-19
 ---
 
 In [AutoRAG](/autorag/), you can now [filter](/autorag/configuration/metadata/) by an object's file name using the `filename` attribute, giving you more control over which files are searched for a given query.
@@ -14,15 +14,15 @@ For example, your search query may look like:
 
 ```js
 const response = await env.AI.autorag("my-autorag").search({
-  query: "what is the project deadline?",
-  filters: {
-    type: "eq",
-    key: "filename",
-    value: "project-alpha-roadmap.md",
-  },
+	query: "what is the project deadline?",
+	filters: {
+		type: "eq",
+		key: "filename",
+		value: "project-alpha-roadmap.md",
+	},
 });
 ```
 
 This allows you to connect your application logic with AutoRAG's retrieval process, making it easy to control what gets searched without needing to reindex or modify your data.
 
-Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata/).
\ No newline at end of file
+Learn more in AutoRAG's [metadata filtering documentation](/autorag/configuration/metadata/).
diff --git a/src/content/changelog/autorag/2025-07-08-autorag-jobs-view.mdx b/src/content/changelog/autorag/2025-07-08-autorag-jobs-view.mdx
index bf9e58a4149787..eac0c447f77cab 100644
--- a/src/content/changelog/autorag/2025-07-08-autorag-jobs-view.mdx
+++ b/src/content/changelog/autorag/2025-07-08-autorag-jobs-view.mdx
@@ -3,10 +3,10 @@ title: Faster indexing and new Jobs view in AutoRAG
 description: Track your indexing pipeline in real time with 3–5× faster indexing and a new Jobs dashboard.
 products:
   - autorag
-date: 2025-07-08T6:00:00Z
+date: 2025-07-08
 ---
 
-You can now expect **3-5× faster indexing** in AutoRAG, and with it, a brand new **Jobs view** to help you monitor indexing progress. 
+You can now expect **3-5× faster indexing** in AutoRAG, and with it, a brand new **Jobs view** to help you monitor indexing progress.
 
 With each AutoRAG, indexing jobs are automatically triggered to sync your data source (i.e. R2 bucket) with your Vectorize index, ensuring new or updated files are reflected in your query results. You can also trigger jobs manually via the [Sync API](/api/resources/autorag/subresources/rags/) or by clicking “Sync index” in the dashboard.
 
@@ -18,8 +18,8 @@ With the new jobs observability, you can now:
 
 ![AutoRAG jobs](~/assets/images/changelog/autorag/autorag-jobs-view.gif)
 
-This makes it easier to understand what’s happening behind the scenes. 
+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).
\ No newline at end of file
+Try it out today on the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/ai/autorag).
diff --git a/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx b/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx
index 690222a0b68400..e9970f541fec35 100644
--- a/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx
+++ b/src/content/changelog/browser-isolation/2025-03-03-user-action-logging.mdx
@@ -1,7 +1,7 @@
 ---
 title: Gain visibility into user actions in Zero Trust Browser Isolation sessions
 description: User action logs for Remote Browser Isolation
-date: 2025-03-04T11:00:00Z
+date: 2025-03-04
 ---
 
 We're excited to announce that new logging capabilities for [Remote Browser Isolation (RBI)](/cloudflare-one/policies/browser-isolation/) through [Logpush](/logs/reference/log-fields/account/) are available in Beta starting today!
diff --git a/src/content/changelog/browser-rendering/2025-01-30-browser-rendering-more-instances.mdx b/src/content/changelog/browser-rendering/2025-01-30-browser-rendering-more-instances.mdx
index 0b81d3d651431c..03d20cb073168f 100644
--- a/src/content/changelog/browser-rendering/2025-01-30-browser-rendering-more-instances.mdx
+++ b/src/content/changelog/browser-rendering/2025-01-30-browser-rendering-more-instances.mdx
@@ -4,7 +4,7 @@ description: Browser Rendering now supports more concurrent browser sessions.
 products:
   - workers
   - browser-rendering
-date: 2025-01-30T13:00:00Z
+date: 2025-01-30
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components"
diff --git a/src/content/changelog/browser-rendering/2025-02-27-br-rest-api-beta.mdx b/src/content/changelog/browser-rendering/2025-02-27-br-rest-api-beta.mdx
index 76f6070ec63564..64fb3980e479d3 100644
--- a/src/content/changelog/browser-rendering/2025-02-27-br-rest-api-beta.mdx
+++ b/src/content/changelog/browser-rendering/2025-02-27-br-rest-api-beta.mdx
@@ -3,7 +3,7 @@ title: New REST API is in open beta!
 description: We've released a new REST API in open beta.
 products:
   - browser-rendering
-date: 2025-02-27T12:00:00Z
+date: 2025-02-27
 ---
 
 We've released a new REST API for [Browser Rendering](/browser-rendering/) in open beta, making interacting with browsers easier than ever. This new API provides endpoints for common browser actions, with more to be added in the future.
diff --git a/src/content/changelog/browser-rendering/2025-04-04-playwright-beta.mdx b/src/content/changelog/browser-rendering/2025-04-04-playwright-beta.mdx
index 4b6c24f2be4f23..99505ca02b9ec0 100644
--- a/src/content/changelog/browser-rendering/2025-04-04-playwright-beta.mdx
+++ b/src/content/changelog/browser-rendering/2025-04-04-playwright-beta.mdx
@@ -3,7 +3,7 @@ title: Playwright for Browser Rendering now available
 description: Developers can now use the Playwright library for browser automation with Browser Rendering
 products:
   - browser-rendering
-date: 2025-04-04T14:00:00Z
+date: 2025-04-04
 ---
 
 We're excited to share that you can now use Playwright's browser automation [capabilities](https://playwright.dev/docs/api/class-playwright) from Cloudflare [Workers](/workers/).
@@ -13,39 +13,40 @@ We're excited to share that you can now use Playwright's browser automation [cap
 Below is an example of how to use Playwright with Browser Rendering to test a TODO application using assertions:
 
 ```ts title="Assertion example"
-import { launch, type BrowserWorker } from '@cloudflare/playwright';
-import { expect } from '@cloudflare/playwright/test';
+import { launch, type BrowserWorker } from "@cloudflare/playwright";
+import { expect } from "@cloudflare/playwright/test";
 
 interface Env {
-  MYBROWSER: BrowserWorker;
+	MYBROWSER: BrowserWorker;
 }
 
 export default {
-  async fetch(request: Request, env: Env) {
-
-    const browser = await launch(env.MYBROWSER);
-    const page = await browser.newPage();
-
-    await page.goto('https://demo.playwright.dev/todomvc');
-
-    const TODO_ITEMS = [
-        'buy some cheese',
-        'feed the cat',
-        'book a doctors appointment'
-    ];
-
-    const newTodo = page.getByPlaceholder('What needs to be done?');
-    for (const item of TODO_ITEMS) {
-        await newTodo.fill(item);
-        await newTodo.press('Enter');
-    }
-
-    await expect(page.getByTestId('todo-title')).toHaveCount(TODO_ITEMS.length);
-
-    await Promise.all(TODO_ITEMS.map(
-        (value, index) => expect(page.getByTestId('todo-title').nth(index)).toHaveText(value)
-    ));
-  },
+	async fetch(request: Request, env: Env) {
+		const browser = await launch(env.MYBROWSER);
+		const page = await browser.newPage();
+
+		await page.goto("https://demo.playwright.dev/todomvc");
+
+		const TODO_ITEMS = [
+			"buy some cheese",
+			"feed the cat",
+			"book a doctors appointment",
+		];
+
+		const newTodo = page.getByPlaceholder("What needs to be done?");
+		for (const item of TODO_ITEMS) {
+			await newTodo.fill(item);
+			await newTodo.press("Enter");
+		}
+
+		await expect(page.getByTestId("todo-title")).toHaveCount(TODO_ITEMS.length);
+
+		await Promise.all(
+			TODO_ITEMS.map((value, index) =>
+				expect(page.getByTestId("todo-title").nth(index)).toHaveText(value),
+			),
+		);
+	},
 };
 ```
 
diff --git a/src/content/changelog/browser-rendering/2025-04-07-br-free-ga-playwright.mdx b/src/content/changelog/browser-rendering/2025-04-07-br-free-ga-playwright.mdx
index 004bf778267695..4cf9b781057eee 100644
--- a/src/content/changelog/browser-rendering/2025-04-07-br-free-ga-playwright.mdx
+++ b/src/content/changelog/browser-rendering/2025-04-07-br-free-ga-playwright.mdx
@@ -3,7 +3,7 @@ title: Browser Rendering REST API is Generally Available, with new endpoints and
 description: Browser Rendering updates - free tier and REST API GA with new endpoints
 products:
   - browser-rendering
-date: 2025-04-07T6:00:00Z
+date: 2025-04-07
 ---
 
 We’re excited to announce Browser Rendering is now available on the [Workers Free plan](https://www.cloudflare.com/plans/developer-platform/), making it even easier to prototype and experiment with web search and headless browser use-cases when building applications on Workers.
diff --git a/src/content/changelog/browser-rendering/2025-05-28-playwright-mcp.mdx b/src/content/changelog/browser-rendering/2025-05-28-playwright-mcp.mdx
index 77050359dc22ba..49282f6bf1866a 100644
--- a/src/content/changelog/browser-rendering/2025-05-28-playwright-mcp.mdx
+++ b/src/content/changelog/browser-rendering/2025-05-28-playwright-mcp.mdx
@@ -3,12 +3,10 @@ title: Playwright MCP server is now compatible with Browser Rendering
 description: You can now deploy Playwright MCP and use any MCP client to get AI models to interact with Browser Rendering
 products:
   - browser-rendering
-date: 2025-05-28T08:00:00Z
+date: 2025-05-28
 ---
 
-import {
-	PackageManagers,
-} from "~/components";
+import { PackageManagers } from "~/components";
 
 We're excited to share that you can now use the [Playwright MCP](https://github.com/cloudflare/playwright-mcp) server with Browser Rendering.
 
@@ -23,11 +21,11 @@ Playwright MCP is available as an npm package at [`@cloudflare/playwright-mcp`](
 Deploying the server is then as easy as:
 
 ```ts
-import { env } from 'cloudflare:workers';
-import { createMcpAgent } from '@cloudflare/playwright-mcp';
+import { env } from "cloudflare:workers";
+import { createMcpAgent } from "@cloudflare/playwright-mcp";
 
 export const PlaywrightMCP = createMcpAgent(env.BROWSER);
-export default PlaywrightMCP.mount('/sse');
+export default PlaywrightMCP.mount("/sse");
 ```
 
 Check out the full code at [GitHub](https://github.com/cloudflare/playwright-mcp).
diff --git a/src/content/changelog/cache/2025-02-04-easier-onboarding-for-csam-scanning-tool.mdx b/src/content/changelog/cache/2025-02-04-easier-onboarding-for-csam-scanning-tool.mdx
index 65540043038d76..70039e28d57eab 100644
--- a/src/content/changelog/cache/2025-02-04-easier-onboarding-for-csam-scanning-tool.mdx
+++ b/src/content/changelog/cache/2025-02-04-easier-onboarding-for-csam-scanning-tool.mdx
@@ -3,7 +3,7 @@ title: Fight CSAM More Easily Than Ever
 description: Simplified setup for Cloudflare's CSAM Scanning Tool, improving child safety protections for websites.
 products:
   - cache
-date: 2025-02-04T12:00:00Z
+date: 2025-02-04
 ---
 
 You can now implement our **child safety tooling**, the **[CSAM Scanning Tool](/cache/reference/csam-scanning/)**, more easily. Instead of requiring external reporting credentials, you only need a verified email address for notifications to onboard. This change makes the tool more accessible to a wider range of customers.
diff --git a/src/content/changelog/cache/2025-04-01-purge-for-all.mdx b/src/content/changelog/cache/2025-04-01-purge-for-all.mdx
index a5e5323d404af7..d59030ecdb21e4 100644
--- a/src/content/changelog/cache/2025-04-01-purge-for-all.mdx
+++ b/src/content/changelog/cache/2025-04-01-purge-for-all.mdx
@@ -1,19 +1,19 @@
 ---
 title: All cache purge methods now available for all plans
 description: All Cloudflare plans can purge by tag, prefix, url, host, or everything to invalidate cached content on the fly.
-products: 
-    - cache
-date: 2025-04-03T18:00:00Z 
+products:
+  - cache
+date: 2025-04-03
 ---
- 
+
 You can now access all Cloudflare cache purge methods — no matter which plan you’re on. Whether you need to update a single asset or instantly invalidate large portions of your site’s content, you now have the same powerful tools previously reserved for Enterprise customers.
 
 **Anyone on Cloudflare can now:**
+
 1. [Purge Everything](/cache/how-to/purge-cache/purge-everything/): Clears all cached content associated with a website.
 2. [Purge by Prefix](/cache/how-to/purge-cache/purge_by_prefix/): Targets URLs sharing a common prefix.
 3. [Purge by Hostname](/cache/how-to/purge-cache/purge-by-hostname/): Invalidates content by specific hostnames.
 4. [Purge by URL (single-file purge)](/cache/how-to/purge-cache/purge-by-single-file/): Precisely targets individual URLs.
 5. [Purge by Tag](/cache/how-to/purge-cache/purge-by-tags/): Uses Cache-Tag response headers to invalidate grouped assets, offering flexibility for complex cache management scenarios.
- 
-Want to learn how each purge method works, when to use them, or what limits apply to your plan? Dive into our [purge cache documentation](/cache/how-to/purge-cache/) and [API reference](https://developers.cloudflare.com/api/resources/cache/methods/purge/) for all the details.
 
+Want to learn how each purge method works, when to use them, or what limits apply to your plan? Dive into our [purge cache documentation](/cache/how-to/purge-cache/) and [API reference](https://developers.cloudflare.com/api/resources/cache/methods/purge/) for all the details.
diff --git a/src/content/changelog/casb/2024-11-22-cloud-data-extraction-aws.mdx b/src/content/changelog/casb/2024-11-22-cloud-data-extraction-aws.mdx
index 343310e6e4ebb7..d52d6f05c9a2c8 100644
--- a/src/content/changelog/casb/2024-11-22-cloud-data-extraction-aws.mdx
+++ b/src/content/changelog/casb/2024-11-22-cloud-data-extraction-aws.mdx
@@ -1,7 +1,7 @@
 ---
 title: Find security misconfigurations in your AWS cloud environment
 description: CASB and DLP with Cloud Data Extraction for AWS cloud environments
-date: 2024-11-22T11:00:00Z
+date: 2024-11-22
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx b/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx
index 4c635371af3499..33c6c6c4965e3f 100644
--- a/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx
+++ b/src/content/changelog/cloudflare-one/2025-04-30-zero-trust-dashboard-dark-mode.mdx
@@ -1,7 +1,7 @@
 ---
 title: Dark Mode for Zero Trust Dashboard
 description: Use Dark Mode in the Zero Trust Dashboard
-date: 2025-04-30T11:00:00Z
+date: 2025-04-30
 ---
 
 import { Tabs, TabItem } from "~/components";
diff --git a/src/content/changelog/cloudflare-one/access-analytics-v2.mdx b/src/content/changelog/cloudflare-one/access-analytics-v2.mdx
index e6e4900e1f4075..636d58bb197c87 100644
--- a/src/content/changelog/cloudflare-one/access-analytics-v2.mdx
+++ b/src/content/changelog/cloudflare-one/access-analytics-v2.mdx
@@ -1,7 +1,7 @@
 ---
 title: New Access Analytics in the Cloudflare One Dashboard
 description: An upgraded analytics experience for Access usage and metrics.
-date: 2025-05-16T11:00:00Z
+date: 2025-05-16
 products:
   - access
 ---
@@ -19,4 +19,4 @@ A new Access Analytics dashboard is now available to all Cloudflare One customer
 
 ![Access Analytics](~/assets/images/changelog/cloudflare-one/accessanalytics.png)
 
-To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar.
\ No newline at end of file
+To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar.
diff --git a/src/content/changelog/cloudflare-one/dashboards-access-report b/src/content/changelog/cloudflare-one/dashboards-access-report
index f15f9da84fe6d5..bedfae29995ace 100644
--- a/src/content/changelog/cloudflare-one/dashboards-access-report
+++ b/src/content/changelog/cloudflare-one/dashboards-access-report
@@ -1,7 +1,7 @@
 ---
 title: Cloudflare One Analytics Dashboards and Exportable Access Report
 description: An upgraded analytics experience for navigating analytics and new report
-date: 2025-06-05T11:00:00Z
+date: 2025-06-05
 products:
   - access
 ---
diff --git a/src/content/changelog/cloudflare-one/gateway-analytics-v2 b/src/content/changelog/cloudflare-one/gateway-analytics-v2
index fdb4df50d38eef..5f1981bccc2701 100644
--- a/src/content/changelog/cloudflare-one/gateway-analytics-v2
+++ b/src/content/changelog/cloudflare-one/gateway-analytics-v2
@@ -1,7 +1,7 @@
 ---
 title: New Gateway Analytics in the Cloudflare One Dashboard
 description: An upgraded analytics experience for Gateway usage and metrics.
-date: 2025-05-29T09:00:00Z
+date: 2025-05-29
 products:
   - gateway
 ---
@@ -15,6 +15,6 @@ You can now visualize and explore:
 - Actions Taken: See a clear breakdown of security actions applied by Gateway policies, such as blocks and allows, offering a comprehensive view of your security posture.
 - Geographic Regions: Gain insight into the global distribution of your traffic.
 
-![Gateway Analytics](~/assets/images/changelog/cloudflare-one/gateway-analytics.png) 
+![Gateway Analytics](~/assets/images/changelog/cloudflare-one/gateway-analytics.png)
 
 To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and go to Analytics in the side navigation bar.
diff --git a/src/content/changelog/cloudflare-tunnel/2024-12-19-diagnostic-logs.mdx b/src/content/changelog/cloudflare-tunnel/2024-12-19-diagnostic-logs.mdx
index 4f36422934902e..ec4c32f5081fe9 100644
--- a/src/content/changelog/cloudflare-tunnel/2024-12-19-diagnostic-logs.mdx
+++ b/src/content/changelog/cloudflare-tunnel/2024-12-19-diagnostic-logs.mdx
@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot tunnels with diagnostic logs
 description: View tunnel diagnostic logs
-date: 2024-12-19T11:00:00Z
+date: 2024-12-19
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/changelog/d1/2025-01-07-d1-faster-query.mdx b/src/content/changelog/d1/2025-01-07-d1-faster-query.mdx
index 2988327d16602b..11405b3d62b86d 100644
--- a/src/content/changelog/d1/2025-01-07-d1-faster-query.mdx
+++ b/src/content/changelog/d1/2025-01-07-d1-faster-query.mdx
@@ -3,14 +3,14 @@ title: 40-60% Faster D1 Worker API Requests
 description: D1's Worker API request latency decreases by 40-60%.
 products:
   - d1
-date: 2025-01-07T18:00:00Z
+date: 2025-01-07
 ---
 
 Users making [D1](/d1/) requests via the [Workers API](/d1/worker-api/) can see up to a 60% end-to-end latency improvement due to the removal of redundant network round trips needed for each request to a D1 database.
 
 ![D1 Worker API latency](public/images/d1/faster-d1-worker-api.png)
 
-*p50, p90, and p95 request latency aggregated across entire D1 service. These latencies are a reference point and should not be viewed as your exact workload improvement.*
+_p50, p90, and p95 request latency aggregated across entire D1 service. These latencies are a reference point and should not be viewed as your exact workload improvement._
 
 This performance improvement benefits all D1 Worker API traffic, especially cross-region requests where network latency is an outsized latency factor. For example, a user in Europe talking to a database in North America. D1 [location hints](/d1/configuration/data-location/#provide-a-location-hint) can be used to influence the geographic location of a database.
 
diff --git a/src/content/changelog/d1/2025-04-10-d1-read-replication-beta.mdx b/src/content/changelog/d1/2025-04-10-d1-read-replication-beta.mdx
index 985d46c2507b0c..cdc315b8001122 100644
--- a/src/content/changelog/d1/2025-04-10-d1-read-replication-beta.mdx
+++ b/src/content/changelog/d1/2025-04-10-d1-read-replication-beta.mdx
@@ -4,7 +4,7 @@ description: Use D1 Sessions API to leverage read replication.
 products:
   - d1
   - workers
-date: 2025-04-10T06:00:00Z
+date: 2025-04-10
 ---
 
 D1 read replication is available in public beta to help lower average latency and increase overall throughput for read-heavy applications like e-commerce websites or content management tools.
diff --git a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx
index bb54cd0f3e7f08..8c1ca46fcf6893 100644
--- a/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx
+++ b/src/content/changelog/d1/2025-05-30-d1-rest-api-latency.mdx
@@ -4,10 +4,10 @@ description: D1 REST API request latency improvements.
 products:
   - d1
   - workers
-date: 2025-05-29T00:00:00Z
+date: 2025-05-29
 ---
 
-Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency. 
+Users using Cloudflare's [REST API](/api/resources/d1/) to query their D1 database can see lower end-to-end request latency now that D1 authentication is performed at the closest Cloudflare network data center that received the request. Previously, authentication required D1 REST API requests to proxy to Cloudflare's core, centralized data centers, which added network round trips and latency.
 
 Latency improvements range from 50-500 ms depending on request location and [database location](/d1/configuration/data-location/) and only apply to the REST API. REST API requests and databases outside the United States see a bigger benefit since Cloudflare's primary core data centers reside in the United States.
 
diff --git a/src/content/changelog/dex/2025-03-07-cloudflare-one-device-health-monitoring.mdx b/src/content/changelog/dex/2025-03-07-cloudflare-one-device-health-monitoring.mdx
index e25e61e222a047..339fdf006bba3e 100644
--- a/src/content/changelog/dex/2025-03-07-cloudflare-one-device-health-monitoring.mdx
+++ b/src/content/changelog/dex/2025-03-07-cloudflare-one-device-health-monitoring.mdx
@@ -1,13 +1,14 @@
 ---
 title: Cloudflare One Agent now supports Endpoint Monitoring
 description: Monitor device health metrics directly from the Cloudflare One agent
-date: 2025-03-07T6:00:00Z
+date: 2025-03-07
 ---
 
 [Digital Experience Monitoring (DEX)](/cloudflare-one/insights/dex/) provides visibility into device, network, and application performance across your Cloudflare SASE deployment. The latest release of the Cloudflare One agent (v2025.1.861) now includes device endpoint monitoring capabilities
 to provide deeper visibility into end-user device performance which can be analyzed directly from the dashboard.
 
 Device health metrics are now automatically collected, allowing administrators to:
+
 - View the last network a user was connected to
 - Monitor CPU and RAM utilization on devices
 - Identify resource-intensive processes running on endpoints
diff --git a/src/content/changelog/dlp/2025-01-03-source-code-confidence-level.mdx b/src/content/changelog/dlp/2025-01-03-source-code-confidence-level.mdx
index 73a42cae2d01e2..2325dc880eb02e 100644
--- a/src/content/changelog/dlp/2025-01-03-source-code-confidence-level.mdx
+++ b/src/content/changelog/dlp/2025-01-03-source-code-confidence-level.mdx
@@ -1,7 +1,7 @@
 ---
 title: Detect source code leaks with Data Loss Prevention
 description: Added source code confidence levels to Data Loss Prevention
-date: 2025-01-20T11:00:00Z
+date: 2025-01-20
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/changelog/dlp/2025-04-14-icd11-support.mdx b/src/content/changelog/dlp/2025-04-14-icd11-support.mdx
index 63b334f346c5a0..958c6066561126 100644
--- a/src/content/changelog/dlp/2025-04-14-icd11-support.mdx
+++ b/src/content/changelog/dlp/2025-04-14-icd11-support.mdx
@@ -1,7 +1,7 @@
 ---
 title: New predefined detection entry for ICD-11
 description: ICD-11 is now available for DLP detections.
-date: 2025-04-14T11:00:00Z
+date: 2025-04-14
 ---
 
 You now have access to the World Health Organization (WHO) 2025 edition of the [International Classification of Diseases 11th Revision (ICD-11)](https://www.who.int/news/item/14-02-2025-who-releases-2025-update-to-the-international-classification-of-diseases-%28icd-11%29) as a predefined detection entry. The new dataset can be found in the [Health Information](/cloudflare-one/policies/data-loss-prevention/dlp-profiles/predefined-profiles/#health-information) predefined profile.
diff --git a/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx b/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx
index 4c6dac8ca5092d..841ddddd4c8745 100644
--- a/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx
+++ b/src/content/changelog/dlp/2025-05-07-forensic-copy-update.mdx
@@ -1,10 +1,9 @@
 ---
 title: Send forensic copies to storage without DLP profiles
 description: HTTP policies can now be configured to send forensic copies for all allow and block policies.
-date: 2025-05-07T11:00:00Z
+date: 2025-05-07
 ---
 
-
 You can now [send DLP forensic copies](/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options/#send-http-requests-to-logpush-destination/) to third-party storage for any HTTP policy with an `Allow` or `Block` action, without needing to include a DLP profile. This change increases flexibility for data handling and forensic investigation use cases.
 
 By default, Gateway will send all matched HTTP requests to your configured DLP Forensic Copy jobs.
diff --git a/src/content/changelog/dlp/2025-05-12-case-sensitive-cwl.mdx b/src/content/changelog/dlp/2025-05-12-case-sensitive-cwl.mdx
index 96c56ed78ca37b..966c521a36ebd3 100644
--- a/src/content/changelog/dlp/2025-05-12-case-sensitive-cwl.mdx
+++ b/src/content/changelog/dlp/2025-05-12-case-sensitive-cwl.mdx
@@ -1,7 +1,7 @@
 ---
 title: Case Sensitive Custom Word Lists
 description: Custom Word Lists can now be configured to enforce case sensitivity.
-date: 2025-05-12T11:00:00Z
+date: 2025-05-12
 ---
 
 You can now configure [custom word lists](/cloudflare-one/policies/data-loss-prevention/datasets/#custom-wordlist) to enforce case sensitivity. This setting supports flexibility where needed and aims to reduce false positives where letter casing is critical.
diff --git a/src/content/changelog/dns/2025-02-02-removed-meta-fields.mdx b/src/content/changelog/dns/2025-02-02-removed-meta-fields.mdx
index 1fd730e0a47c30..f7c89393bb9c75 100644
--- a/src/content/changelog/dns/2025-02-02-removed-meta-fields.mdx
+++ b/src/content/changelog/dns/2025-02-02-removed-meta-fields.mdx
@@ -1,7 +1,7 @@
 ---
 title: Removed unused meta fields from DNS records
 description: Cloudflare is removing five fields from the meta object of DNS records.
-date: 2025-02-02T18:00:00Z
+date: 2025-02-02
 ---
 
 Cloudflare is removing five fields from the `meta` object of DNS records. These fields have been unused for more than a year and are no longer set on new records. This change may take up to four weeks to fully roll out.
diff --git a/src/content/changelog/dns/2025-06-03-shopify-o2o-improvements.mdx b/src/content/changelog/dns/2025-06-03-shopify-o2o-improvements.mdx
index 9ed7394ff811c8..011f3a7bfc3743 100644
--- a/src/content/changelog/dns/2025-06-03-shopify-o2o-improvements.mdx
+++ b/src/content/changelog/dns/2025-06-03-shopify-o2o-improvements.mdx
@@ -1,7 +1,7 @@
 ---
 title: Improved onboarding for Shopify merchants
 description: Shopify merchants can easily set up Orange-to-Orange (O2O).
-date: 2025-06-03T11:00:00Z
+date: 2025-06-03
 ---
 
 Shopify merchants can now onboard to **Orange-to-Orange (O2O)** automatically, without needing to contact support or community members.
diff --git a/src/content/changelog/dns/2025-06-11-nsec3-support.mdx b/src/content/changelog/dns/2025-06-11-nsec3-support.mdx
index d5ee5ac66336a5..4b28acd7349522 100644
--- a/src/content/changelog/dns/2025-06-11-nsec3-support.mdx
+++ b/src/content/changelog/dns/2025-06-11-nsec3-support.mdx
@@ -1,7 +1,7 @@
 ---
 title: NSEC3 support for DNSSEC
 description: Cloudflare DNSSEC supports NSEC3 for proof of non-existence.
-date: 2025-06-11T12:00:00Z
+date: 2025-06-11
 ---
 
 Enterprise customers can now select NSEC3 as method for proof of non-existence on their zones.
diff --git a/src/content/changelog/dns/2025-06-16-internal-dns-beta-ui.mdx b/src/content/changelog/dns/2025-06-16-internal-dns-beta-ui.mdx
index 8d0b2cba9ef5e6..a00f46a9907171 100644
--- a/src/content/changelog/dns/2025-06-16-internal-dns-beta-ui.mdx
+++ b/src/content/changelog/dns/2025-06-16-internal-dns-beta-ui.mdx
@@ -1,7 +1,7 @@
 ---
 title: Internal DNS (beta) now manageable in the Cloudflare dashboard
 description: The Internal DNS (beta) is now fully available in the Cloudflare dashboard.
-date: 2025-06-16T16:00:00Z
+date: 2025-06-16
 ---
 
 Participating beta testers can now fully configure [Internal DNS](/dns/internal-dns/) directly in the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/internal-dns).
diff --git a/src/content/changelog/dns/2025-06-23-account-level-dns-analytics-api.mdx b/src/content/changelog/dns/2025-06-23-account-level-dns-analytics-api.mdx
index 1d1ca735aec954..8c4e8d6cabd9b9 100644
--- a/src/content/changelog/dns/2025-06-23-account-level-dns-analytics-api.mdx
+++ b/src/content/changelog/dns/2025-06-23-account-level-dns-analytics-api.mdx
@@ -1,7 +1,7 @@
 ---
 title: Account-level DNS analytics now available via GraphQL Analytics API
 description: Authoritative DNS analytics can now be accessed on the account level via the GraphQL Analytics API.
-date: 2025-06-19T12:00:00Z
+date: 2025-06-19
 ---
 
 Authoritative DNS analytics are now available on the **account level** via the [Cloudflare GraphQL Analytics API](/analytics/graphql-api/).
@@ -15,9 +15,9 @@ query GetLatestNXDOMAINResponses {
 	viewer {
 		accounts(filter: { accountTag: "a30f822fcd7c401984bf85d8f2a5111c" }) {
 			dnsAnalyticsAdaptive(
-				filter: { 
-					date_geq: "2025-06-16", 
-					date_leq: "2025-06-18",
+				filter: {
+					date_geq: "2025-06-16"
+					date_leq: "2025-06-18"
 					responseCode: "NXDOMAIN"
 				}
 				limit: 10000
diff --git a/src/content/changelog/durable-objects/2025-04-07-durable-objects-free-tier.mdx b/src/content/changelog/durable-objects/2025-04-07-durable-objects-free-tier.mdx
index 54561cb0b76674..1de05ce1907cad 100644
--- a/src/content/changelog/durable-objects/2025-04-07-durable-objects-free-tier.mdx
+++ b/src/content/changelog/durable-objects/2025-04-07-durable-objects-free-tier.mdx
@@ -4,7 +4,7 @@ description: Durable Objects now available on Workers Free plan.
 products:
   - durable-objects
   - workers
-date: 2025-04-07T06:00:00Z
+date: 2025-04-07
 ---
 
 Durable Objects can now be used with zero commitment on the [Workers Free plan](/workers/platform/pricing/) allowing you to build AI agents with [Agents SDK](/agents/), collaboration tools, and real-time applications like chat or multiplayer games.
diff --git a/src/content/changelog/durable-objects/2025-04-07-sqlite-in-durable-objects-ga.mdx b/src/content/changelog/durable-objects/2025-04-07-sqlite-in-durable-objects-ga.mdx
index ee521539a5b837..89022b7bf7a61b 100644
--- a/src/content/changelog/durable-objects/2025-04-07-sqlite-in-durable-objects-ga.mdx
+++ b/src/content/changelog/durable-objects/2025-04-07-sqlite-in-durable-objects-ga.mdx
@@ -3,11 +3,11 @@ title: SQLite in Durable Objects GA with 10GB storage per object
 description: SQLite-backed Durable Objects are generally available.
 products:
   - durable-objects
-  - workers 
-date: 2025-04-07T06:00:00Z
+  - workers
+date: 2025-04-07
 ---
 
-SQLite in Durable Objects is now generally available (GA) with 10GB SQLite database per Durable Object. Since the [public beta](https://blog.cloudflare.com/sqlite-in-durable-objects/) in September 2024, we've added feature parity and robustness for the SQLite storage backend compared to the preexisting key-value (KV) storage backend for Durable Objects. 
+SQLite in Durable Objects is now generally available (GA) with 10GB SQLite database per Durable Object. Since the [public beta](https://blog.cloudflare.com/sqlite-in-durable-objects/) in September 2024, we've added feature parity and robustness for the SQLite storage backend compared to the preexisting key-value (KV) storage backend for Durable Objects.
 
 SQLite-backed Durable Objects are recommended for all new Durable Object classes, using `new_sqlite_classes` [Wrangler configuration](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class). Only SQLite-backed Durable Objects have access to Storage API's [SQL](/durable-objects/api/storage-api/#sql-api) and [point-in-time recovery](/durable-objects/api/storage-api/#pitr-point-in-time-recovery-api) methods, which provide relational data modeling, SQL querying, and better data management.
 
diff --git a/src/content/changelog/durable-objects/2025-06-25-actors-package-alpha.mdx b/src/content/changelog/durable-objects/2025-06-25-actors-package-alpha.mdx
index 55fd6d468528de..0ac7413a2c900b 100644
--- a/src/content/changelog/durable-objects/2025-06-25-actors-package-alpha.mdx
+++ b/src/content/changelog/durable-objects/2025-06-25-actors-package-alpha.mdx
@@ -4,7 +4,7 @@ description: "@cloudflare/actors library with Durable Objects helpers and patter
 products:
   - durable-objects
   - workers
-date: 2025-06-25T06:00:00Z
+date: 2025-06-25
 ---
 
 The new [@cloudflare/actors](https://www.npmjs.com/package/@cloudflare/actors) library is now in beta!
@@ -28,7 +28,7 @@ import { Storage } from "@cloudflare/actors/storage";
 
 export class ChatRoom extends DurableObject<Env> {
     storage: Storage;
-    
+
     constructor(ctx: DurableObjectState, env: Env) {
         super(ctx, env)
         this.storage = new Storage(ctx.storage);
@@ -50,7 +50,7 @@ export class ChatRoom extends DurableObject<Env> {
 }
 ```
 
-`@cloudflare/actors` library introduces the `Actor` class pattern. `Actor` lets you access Durable Objects without writing the Worker that communicates with your Durable Object (the Worker is created for you). By default, requests are routed to a Durable Object named "default". 
+`@cloudflare/actors` library introduces the `Actor` class pattern. `Actor` lets you access Durable Objects without writing the Worker that communicates with your Durable Object (the Worker is created for you). By default, requests are routed to a Durable Object named "default".
 
 ```js
 export class MyActor extends Actor<Env> {
diff --git a/src/content/changelog/email-routing/2025-03-12-reply-limits.mdx b/src/content/changelog/email-routing/2025-03-12-reply-limits.mdx
index d7fa895eff4ef8..eb6af07f96b743 100644
--- a/src/content/changelog/email-routing/2025-03-12-reply-limits.mdx
+++ b/src/content/changelog/email-routing/2025-03-12-reply-limits.mdx
@@ -1,51 +1,60 @@
 ---
 title: Threaded replies now possible in Email Workers
 description: You can now use Email Workers to send multiple replies to the same email thread.
-date: 2025-03-12T18:00:00Z
+date: 2025-03-12
 ---
 
 We’re removing some of the restrictions in Email Routing so that AI Agents and task automation can better handle email workflows, including how Workers can [reply](/email-routing/email-workers/reply-email-workers/) to incoming emails.
 
 It's now possible to keep a threaded email conversation with an [Email Worker](/email-routing/email-workers/) script as long as:
 
-* The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
-* The email can only be replied to once in the same `EmailMessage` event.
-* The recipient in the reply must match the incoming sender.
-* The outgoing sender domain must match the same domain that received the email.
-* Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
+- The incoming email has to have valid [DMARC](https://www.cloudflare.com/learning/dns/dns-records/dns-dmarc-record/).
+- The email can only be replied to once in the same `EmailMessage` event.
+- The recipient in the reply must match the incoming sender.
+- The outgoing sender domain must match the same domain that received the email.
+- Every time an email passes through Email Routing or another MTA, an entry is added to the `References` list. We stop accepting replies to emails with more than 100 `References` entries to prevent abuse or accidental loops.
 
 Here's an example of a Worker responding to Emails using a Workers AI model:
 
 ```ts title="AI model responding to emails"
 import PostalMime from "postal-mime";
-import {createMimeMessage} from "mimetext"
+import { createMimeMessage } from "mimetext";
 import { EmailMessage } from "cloudflare:email";
 
 export default {
-  async email(message, env, ctx) {
-    const email = await PostalMime.parse(message.raw)
-    const res = await env.AI.run('@cf/meta/llama-2-7b-chat-fp16', {
-      messages: [{
-        role: "user",
-        content: email.text ?? ''
-      }]
-    })
-
-    // message-id is generated by mimetext
-    const response = createMimeMessage()
-    response.setHeader("In-Reply-To", message.headers.get("Message-ID")!);
-    response.setSender("agent@example.com");
-    response.setRecipient(message.from);
-    response.setSubject("Llama response");
-    response.addMessage({
-      contentType: 'text/plain',
-      data: res instanceof ReadableStream ? await new Response(res).text() : res.response!
-    })
-
-    const replyMessage = new EmailMessage("<email>", message.from, response.asRaw());
-    await message.reply(replyMessage)
-  }
+	async email(message, env, ctx) {
+		const email = await PostalMime.parse(message.raw);
+		const res = await env.AI.run("@cf/meta/llama-2-7b-chat-fp16", {
+			messages: [
+				{
+					role: "user",
+					content: email.text ?? "",
+				},
+			],
+		});
+
+		// message-id is generated by mimetext
+		const response = createMimeMessage();
+		response.setHeader("In-Reply-To", message.headers.get("Message-ID")!);
+		response.setSender("agent@example.com");
+		response.setRecipient(message.from);
+		response.setSubject("Llama response");
+		response.addMessage({
+			contentType: "text/plain",
+			data:
+				res instanceof ReadableStream
+					? await new Response(res).text()
+					: res.response!,
+		});
+
+		const replyMessage = new EmailMessage(
+			"<email>",
+			message.from,
+			response.asRaw(),
+		);
+		await message.reply(replyMessage);
+	},
 } satisfies ExportedHandler<Env>;
 ```
 
-See [Reply to emails from Workers](/email-routing/email-workers/reply-email-workers/) for more information.
\ No newline at end of file
+See [Reply to emails from Workers](/email-routing/email-workers/reply-email-workers/) for more information.
diff --git a/src/content/changelog/email-routing/2025-04-08-local-development.mdx b/src/content/changelog/email-routing/2025-04-08-local-development.mdx
index a41e2374eff3fc..91c399481f6106 100644
--- a/src/content/changelog/email-routing/2025-04-08-local-development.mdx
+++ b/src/content/changelog/email-routing/2025-04-08-local-development.mdx
@@ -1,7 +1,7 @@
 ---
 title: Local development support for Email Workers
 description: Developers can now use wrangler to do local development for Email Workers.
-date: 2025-04-08T15:00:00Z
+date: 2025-04-08
 ---
 
 Email Workers enables developers to programmatically take action on anything that hits their email inbox. If you're building with Email Workers, you can now test the behavior of an Email Worker script, receiving, replying and sending emails in your local environment using `wrangler dev`.
@@ -9,7 +9,7 @@ Email Workers enables developers to programmatically take action on anything tha
 Below is an example that shows you how you can receive messages using the `email()` handler and parse them using [postal-mime](https://www.npmjs.com/package/postal-mime):
 
 ```ts
-import * as PostalMime from 'postal-mime';
+import * as PostalMime from "postal-mime";
 
 export default {
 	async email(message, env, ctx) {
@@ -47,31 +47,31 @@ This is what you get in the console:
 
 ```json
 {
-  headers: [
-    {
-      key: 'received',
-      value: 'from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000'
-    },
-    { key: 'from', value: '"John" <sender@example.com>' },
-    { key: 'reply-to', value: 'sender@example.com' },
-    { key: 'to', value: 'recipient@example.com' },
-    { key: 'subject', value: 'Testing Email Workers Local Dev' },
-    { key: 'content-type', value: 'text/html; charset="windows-1252"' },
-    { key: 'x-mailer', value: 'Curl' },
-    { key: 'date', value: 'Tue, 27 Aug 2024 08:49:44 -0700' },
-    {
-      key: 'message-id',
-      value: '<6114391943504294873000@ZSH-GHOSTTY>'
-    }
-  ],
-  from: { address: 'sender@example.com', name: 'John' },
-  to: [ { address: 'recipient@example.com', name: '' } ],
-  replyTo: [ { address: 'sender@example.com', name: '' } ],
-  subject: 'Testing Email Workers Local Dev',
-  messageId: '<6114391943504294873000@ZSH-GHOSTTY>',
-  date: '2024-08-27T15:49:44.000Z',
-  html: 'Hi there\n',
-  attachments: []
+	"headers": [
+		{
+			"key": "received",
+			"value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"
+		},
+		{ "key": "from", "value": "\"John\" <sender@example.com>" },
+		{ "key": "reply-to", "value": "sender@example.com" },
+		{ "key": "to", "value": "recipient@example.com" },
+		{ "key": "subject", "value": "Testing Email Workers Local Dev" },
+		{ "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },
+		{ "key": "x-mailer", "value": "Curl" },
+		{ "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },
+		{
+			"key": "message-id",
+			"value": "<6114391943504294873000@ZSH-GHOSTTY>"
+		}
+	],
+	"from": { "address": "sender@example.com", "name": "John" },
+	"to": [{ "address": "recipient@example.com", "name": "" }],
+	"replyTo": [{ "address": "sender@example.com", "name": "" }],
+	"subject": "Testing Email Workers Local Dev",
+	"messageId": "<6114391943504294873000@ZSH-GHOSTTY>",
+	"date": "2024-08-27T15:49:44.000Z",
+	"html": "Hi there\n",
+	"attachments": []
 }
 ```
 
diff --git a/src/content/changelog/email-routing/2025-06-30-mail-authentication.mdx b/src/content/changelog/email-routing/2025-06-30-mail-authentication.mdx
index 905c673e0ac13d..ffff627feab38b 100644
--- a/src/content/changelog/email-routing/2025-06-30-mail-authentication.mdx
+++ b/src/content/changelog/email-routing/2025-06-30-mail-authentication.mdx
@@ -1,7 +1,7 @@
 ---
 title: Mail authentication requirements for Email Routing
 description: Emails will need to be authenticated either via SPF or DKIM in order to be forwarded.
-date: 2025-06-30T10:00:00Z
+date: 2025-06-30
 ---
 
 The Email Routing platform supports [SPF](https://datatracker.ietf.org/doc/html/rfc7208) records and [DKIM (DomainKeys Identified Mail)](https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail) signatures and
@@ -17,4 +17,4 @@ the forward action may fail due to missing authentication on the incoming email.
 SPAM has been a long-standing issue with email. By enforcing mail authentication, we will increase the efficiency of identifying abusive senders and blocking
 bad emails.
 If you're an email server delivering emails to large mailbox providers, it's likely you already use these protocols; otherwise, please ensure
-you have them properly configured.
\ No newline at end of file
+you have them properly configured.
diff --git a/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx b/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx
index 4a28d27b1922e7..9a8a977617f440 100644
--- a/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx
+++ b/src/content/changelog/email-security-cf1/2024-12-19-reclassification-tab.mdx
@@ -1,7 +1,7 @@
 ---
 title: Increased transparency for phishing email submissions
 description: New Email reclassifications tab
-date: 2024-12-19T11:00:00Z
+date: 2024-12-19
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/changelog/email-security-cf1/2025-05-08-open-attachments-with-browser-isolation.mdx b/src/content/changelog/email-security-cf1/2025-05-08-open-attachments-with-browser-isolation.mdx
index c224d45a743626..22c24304681b04 100644
--- a/src/content/changelog/email-security-cf1/2025-05-08-open-attachments-with-browser-isolation.mdx
+++ b/src/content/changelog/email-security-cf1/2025-05-08-open-attachments-with-browser-isolation.mdx
@@ -1,14 +1,13 @@
 ---
 title: Open email attachments with Browser Isolation
 description: A new attachment section in Email Security allows you to safely open attachments to view and investigate.
-date: 2025-05-08T19:20:11Z
+date: 2025-05-08
 ---
 
 You can now safely open email attachments to view and investigate them.
 
 What this means is that messages now have a **Attachments** section. Here, you can view processed attachments and their classifications (for example, _Malicious_, _Suspicious_, _Encrypted_). Next to each attachment, a **Browser Isolation** icon allows your team to safely open the file in a **clientless, isolated browser** with no risk to the analyst or your environment.
 
-
 To use this feature, you must:
 
 - Enable **Clientless Web Isolation** in your Zero Trust settings.
@@ -16,8 +15,7 @@ To use this feature, you must:
 
 For more details, refer to our [setup guide](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/).
 
-Some attachment types may not render in Browser Isolation. If there is a file type that you would like to be opened with Browser Isolation, reach out to your Cloudflare contact. 
-
+Some attachment types may not render in Browser Isolation. If there is a file type that you would like to be opened with Browser Isolation, reach out to your Cloudflare contact.
 
 This feature is available across all CES packages:
 
diff --git a/src/content/changelog/email-security-cf1/2025-05-15-open-links-browser-isolation.mdx b/src/content/changelog/email-security-cf1/2025-05-15-open-links-browser-isolation.mdx
index 144cc3232787ca..d7267a1ebd3d89 100644
--- a/src/content/changelog/email-security-cf1/2025-05-15-open-links-browser-isolation.mdx
+++ b/src/content/changelog/email-security-cf1/2025-05-15-open-links-browser-isolation.mdx
@@ -1,7 +1,7 @@
 ---
 title: Open email links with Browser Isolation
 description: New investigation feature for links
-date: 2025-05-15T11:00:00Z
+date: 2025-05-15
 ---
 
 You can now safely open links in emails to view and investigate them.
diff --git a/src/content/changelog/fundamentals/2025-03-21-resource-force-replacement-bug.mdx b/src/content/changelog/fundamentals/2025-03-21-resource-force-replacement-bug.mdx
index 8f8a4cd6fc380c..120ee9a8e666d8 100644
--- a/src/content/changelog/fundamentals/2025-03-21-resource-force-replacement-bug.mdx
+++ b/src/content/changelog/fundamentals/2025-03-21-resource-force-replacement-bug.mdx
@@ -3,10 +3,10 @@ title: Dozens of Cloudflare Terraform Provider resources now have proper drift d
 description: Improper drift detection in the Cloudflare Terraform Provider resulted in dozens of resources always indicating they needed to be updated or replaced.
 products:
   - fundamentals
-date: 2025-03-21T00:00:00Z
+date: 2025-03-21
 ---
 
-In [Cloudflare Terraform Provider](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, dozens of resources now have proper drift detection. Before this fix, these resources would indicate they needed to be updated or replaced — even if there was no real change. Now, you can rely on your `terraform plan` to only show what resources are expected to change. 
+In [Cloudflare Terraform Provider](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, dozens of resources now have proper drift detection. Before this fix, these resources would indicate they needed to be updated or replaced — even if there was no real change. Now, you can rely on your `terraform plan` to only show what resources are expected to change.
 
 This issue affected [resources](https://registry.terraform.io/providers/cloudflare/cloudflare/latest/docs) related to these products and features:
 
diff --git a/src/content/changelog/fundamentals/2025-03-21-sensitive-values-redacted.mdx b/src/content/changelog/fundamentals/2025-03-21-sensitive-values-redacted.mdx
index 3b05a126441b11..e972424f723c9c 100644
--- a/src/content/changelog/fundamentals/2025-03-21-sensitive-values-redacted.mdx
+++ b/src/content/changelog/fundamentals/2025-03-21-sensitive-values-redacted.mdx
@@ -3,7 +3,7 @@ title: Cloudflare Terraform Provider now properly redacts sensitive values
 description: Resources in the Cloudflare Terraform Provider that have sensitive properties will not show those values in logs.
 products:
   - fundamentals
-date: 2025-03-21T00:00:00Z
+date: 2025-03-21
 ---
 
 In the [Cloudflare Terraform Provider](https://github.com/cloudflare/terraform-provider-cloudflare) versions 5.2.0 and above, sensitive properties of resources are redacted in logs. Sensitive properties in [Cloudflare's OpenAPI Schema](https://raw.githubusercontent.com/cloudflare/api-schemas/refs/heads/main/openapi.yaml) are now annotated with `x-sensitive: true`. This results in proper auto-generation of the corresponding Terraform resources, and prevents sensitive values from being shown when you run Terraform commands.
diff --git a/src/content/changelog/gateway/2025-02-13-improvements-unscannable-files.mdx b/src/content/changelog/gateway/2025-02-13-improvements-unscannable-files.mdx
index 7cce7f047cebe9..616514a4d0276c 100644
--- a/src/content/changelog/gateway/2025-02-13-improvements-unscannable-files.mdx
+++ b/src/content/changelog/gateway/2025-02-13-improvements-unscannable-files.mdx
@@ -1,7 +1,7 @@
 ---
 title: Block files that are password-protected, compressed, or otherwise unscannable.
 description: Unscannable files for Download and Upload File Types selectors
-date: 2025-02-03T11:00:00Z
+date: 2025-02-03
 products:
   - dlp
 ---
diff --git a/src/content/changelog/gateway/2025-03-21-pdns-user-locations-role.mdx b/src/content/changelog/gateway/2025-03-21-pdns-user-locations-role.mdx
index 0f88592c7049ad..80e031d4c3fd07 100644
--- a/src/content/changelog/gateway/2025-03-21-pdns-user-locations-role.mdx
+++ b/src/content/changelog/gateway/2025-03-21-pdns-user-locations-role.mdx
@@ -1,7 +1,7 @@
 ---
 title: Secure DNS Locations Management User Role
 description: Create secure DNS locations using the new Cloudflare Zero Trust Locations Write role.
-date: 2025-03-21T13:50:40Z
+date: 2025-03-21
 products:
   - gateway
 hidden: false
diff --git a/src/content/changelog/gateway/2025-04-11-http-redirect-custom-block-page-redirect.mdx b/src/content/changelog/gateway/2025-04-11-http-redirect-custom-block-page-redirect.mdx
index be391583db64f2..bb703f9abab194 100644
--- a/src/content/changelog/gateway/2025-04-11-http-redirect-custom-block-page-redirect.mdx
+++ b/src/content/changelog/gateway/2025-04-11-http-redirect-custom-block-page-redirect.mdx
@@ -1,7 +1,7 @@
 ---
 title: HTTP redirect and custom block page redirect
 description: Redirect traffic with a Gateway HTTP Redirect policy, or with the block page in an HTTP or DNS Block policy.
-date: 2025-04-11T16:30:00Z
+date: 2025-04-11
 products:
   - gateway
 hidden: false
diff --git a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
index 6e69a238131c4c..ef98a6b4d09b38 100644
--- a/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
+++ b/src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx
@@ -4,10 +4,11 @@ description: Select your egress IP depending on your upstream fully qualified do
 products:
   - gateway
 hidden: false
-date: 2025-04-28T11:00:00Z
+date: 2025-04-28
 ---
 
-Cloudflare One administrators can now control which egress IP is used based on a destination's fully qualified domain name (FDQN) within Gateway Egress policies. 
+Cloudflare One administrators can now control which egress IP is used based on a destination's fully qualified domain name (FDQN) within Gateway Egress policies.
+
 - Host, Domain, Content Categories, and Application selectors are now available in the Gateway Egress policy builder in beta.
 - During the beta period, you can use these selectors with traffic on-ramped to Gateway with the WARP client, proxy endpoints (commonly deployed with PAC files), or Cloudflare Browser Isolation.
   - For WARP client support, additional configuration is required. For more information, refer to the [WARP client configuration documentation](/cloudflare-one/policies/gateway/egress-policies/#limitations).
diff --git a/src/content/changelog/gateway/2025-05-13-new-applications-added.mdx b/src/content/changelog/gateway/2025-05-13-new-applications-added.mdx
index a1d259c5738f30..0ce7e661831191 100644
--- a/src/content/changelog/gateway/2025-05-13-new-applications-added.mdx
+++ b/src/content/changelog/gateway/2025-05-13-new-applications-added.mdx
@@ -1,16 +1,16 @@
 ---
 title: New Applications Added for DNS Filtering
-description: Manage outbound traffic for 273 new applications with DNS policy options 
-date: 2025-05-13T11:00:00Z
+description: Manage outbound traffic for 273 new applications with DNS policy options
+date: 2025-05-13
 ---
- 
-You can now create DNS policies to manage outbound traffic for an expanded list of applications. 
+
+You can now create DNS policies to manage outbound traffic for an expanded list of applications.
 This update adds support for 273 new applications, giving you more control over your organization's outbound traffic.
 
 With this update, you can:
-+ Create DNS policies for a wider range of applications
-+ Manage outbound traffic more effectively
-+ Improve your organization's security and compliance posture
 
+- Create DNS policies for a wider range of applications
+- Manage outbound traffic more effectively
+- Improve your organization's security and compliance posture
 
 For more information on creating DNS policies, see our [DNS policy documentation](/cloudflare-one/policies/gateway/dns-policies/).
diff --git a/src/content/changelog/gateway/2025-05-14-domain-category-improvements.mdx b/src/content/changelog/gateway/2025-05-14-domain-category-improvements.mdx
index 440b25b96a7bea..36f9d5aaddcfa7 100644
--- a/src/content/changelog/gateway/2025-05-14-domain-category-improvements.mdx
+++ b/src/content/changelog/gateway/2025-05-14-domain-category-improvements.mdx
@@ -1,26 +1,27 @@
 ---
 title: Domain Categories improvements
 description: We have added 7 new Domain Categories and renamed 3 Domain Categories, to better reflect online content and enable DNS filtering
-date: 2025-05-14T11:00:00Z
+date: 2025-05-14
 ---
+
 **New categories added**
 
-| Parent ID | Parent Name | Category ID | Category Name |
-| --- | --- | --- | --- |
-| 1 | Ads | 66 | Advertisements |
-| 3 | Business & Economy | 185 | Personal Finance |
-| 3 | Business & Economy | 186 | Brokerage & Investing |
-| 21 | Security Threats | 187 | Compromised Domain |
-| 21 | Security Threats | 188 | Potentially Unwanted Software |
-| 6 | Education | 189 | Reference |
-| 9 | Government & Politics | 190 | Charity and Non-profit |
+| Parent ID | Parent Name           | Category ID | Category Name                 |
+| --------- | --------------------- | ----------- | ----------------------------- |
+| 1         | Ads                   | 66          | Advertisements                |
+| 3         | Business & Economy    | 185         | Personal Finance              |
+| 3         | Business & Economy    | 186         | Brokerage & Investing         |
+| 21        | Security Threats      | 187         | Compromised Domain            |
+| 21        | Security Threats      | 188         | Potentially Unwanted Software |
+| 6         | Education             | 189         | Reference                     |
+| 9         | Government & Politics | 190         | Charity and Non-profit        |
 
 **Changes to existing categories**
 
-| Original Name | New Name |
-| --- | --- |
-| Religion | Religion & Spirituality |
-| Government | Government/Legal |
-| Redirect | URL Alias/Redirect |
+| Original Name | New Name                |
+| ------------- | ----------------------- |
+| Religion      | Religion & Spirituality |
+| Government    | Government/Legal        |
+| Redirect      | URL Alias/Redirect      |
 
 Refer to [Gateway domain categories](/cloudflare-one/policies/gateway/domain-categories/) to learn more.
diff --git a/src/content/changelog/gateway/2025-05-27-Protocol-Detection-availability.mdx b/src/content/changelog/gateway/2025-05-27-Protocol-Detection-availability.mdx
index a2b600542d5e86..7b21c1b689d1f2 100644
--- a/src/content/changelog/gateway/2025-05-27-Protocol-Detection-availability.mdx
+++ b/src/content/changelog/gateway/2025-05-27-Protocol-Detection-availability.mdx
@@ -4,7 +4,7 @@ description: Gateway protocol detection is now available on customer plan types!
 products:
   - gateway
 hidden: false
-date: 2025-05-27T11:00:00Z
+date: 2025-05-27
 ---
 
 All Cloudflare One Gateway users can now use Protocol detection logging and filtering, including those on Pay-as-you-go and Free plans.
diff --git a/src/content/changelog/gateway/2025-06-17-new-order-of-enforcement.mdx b/src/content/changelog/gateway/2025-06-17-new-order-of-enforcement.mdx
index 061c9c98d7cf4f..f33f9c25381db6 100644
--- a/src/content/changelog/gateway/2025-06-17-new-order-of-enforcement.mdx
+++ b/src/content/changelog/gateway/2025-06-17-new-order-of-enforcement.mdx
@@ -4,8 +4,9 @@ description: Gateway Network policies (Layer 4) will be evaluated before HTTP (L
 products:
   - gateway
 hidden: false
-date: 2025-06-18T11:00:00Z
+date: 2025-06-18
 ---
+
 [Gateway](/cloudflare-one/policies/gateway/) will now evaluate [Network (Layer 4) policies](/cloudflare-one/policies/gateway/network-policies/) **before** [HTTP (Layer 7) policies](/cloudflare-one/policies/gateway/http-policies/). This change preserves your existing security posture and does not affect which traffic is filtered — but it may impact how notifications are displayed to end users.
 
 This change will roll out progressively between **July 14–18, 2025**. If you use HTTP policies, we recommend reviewing your configuration ahead of rollout to ensure the user experience remains consistent.
@@ -13,14 +14,16 @@ This change will roll out progressively between **July 14–18, 2025**. If you u
 ### Updated order of enforcement
 
 **Previous order:**
-1. DNS policies  
-2. HTTP policies  
-3. Network policies  
+
+1. DNS policies
+2. HTTP policies
+3. Network policies
 
 **New order:**
-1. DNS policies  
-2. **Network policies**  
-3. **HTTP policies**  
+
+1. DNS policies
+2. **Network policies**
+3. **HTTP policies**
 
 ### Action required: Review your Gateway HTTP policies
 
@@ -32,6 +35,7 @@ This change may affect block notifications. For example:
 With the new order, the Network policy will trigger first — and the user will no longer see the HTTP block page.
 
 To ensure users still receive a block notification, you can:
+
 - Add a client notification to your Network policy, or
 - Use only the HTTP policy for that domain.
 
diff --git a/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx b/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx
index 6cc85e45a894e8..6e09f5b120b77e 100644
--- a/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx
+++ b/src/content/changelog/hyperdrive/2024-12-11-hyperdrive-caching-at-edge.mdx
@@ -3,7 +3,7 @@ title: Up to 10x faster cached queries for Hyperdrive
 description: Hyperdrive now caches queries in all Cloudflare locations decreasing cache hit latency by up to 90%
 products:
   - hyperdrive
-date: 2024-12-11T18:00:00Z
+date: 2024-12-11
 ---
 
 Hyperdrive now caches queries in all Cloudflare locations, decreasing cache hit latency by up to 90%.
diff --git a/src/content/changelog/hyperdrive/2025-01-28-hyperdrive-automated-private-database-configuration.mdx b/src/content/changelog/hyperdrive/2025-01-28-hyperdrive-automated-private-database-configuration.mdx
index 0c54cf613b7820..546b34508d42c4 100644
--- a/src/content/changelog/hyperdrive/2025-01-28-hyperdrive-automated-private-database-configuration.mdx
+++ b/src/content/changelog/hyperdrive/2025-01-28-hyperdrive-automated-private-database-configuration.mdx
@@ -3,7 +3,7 @@ title: Automatic configuration for private databases on Hyperdrive
 description: Hyperdrive now automatically configures your Cloudflare Tunnel to connect to your private database.
 products:
   - hyperdrive
-date: 2025-01-28T18:00:00Z
+date: 2025-01-28
 ---
 
 Hyperdrive now automatically configures your Cloudflare Tunnel to connect to your private database.
diff --git a/src/content/changelog/hyperdrive/2025-03-04-hyperdrive-pooling-near-database-and-ip-range-egress.mdx b/src/content/changelog/hyperdrive/2025-03-04-hyperdrive-pooling-near-database-and-ip-range-egress.mdx
index 1399c9b6ba2fe4..35205f590b1cfb 100644
--- a/src/content/changelog/hyperdrive/2025-03-04-hyperdrive-pooling-near-database-and-ip-range-egress.mdx
+++ b/src/content/changelog/hyperdrive/2025-03-04-hyperdrive-pooling-near-database-and-ip-range-egress.mdx
@@ -3,7 +3,7 @@ title: Hyperdrive reduces query latency by up to 90% and now supports IP access
 description: Hyperdrive now pools database connections closer to your database to reduce query latency, and now also provides a documented IP address range for IP ACLs.
 products:
   - hyperdrive
-date: 2025-03-07T18:00:00Z
+date: 2025-03-07
 ---
 
 Hyperdrive now pools database connections in one or more regions close to your database. This means that your uncached queries and new database connections have up to 90% less latency as measured from connection pools.
diff --git a/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-free-plan.mdx b/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-free-plan.mdx
index dc2f94b40513c5..3381502cb1ae20 100644
--- a/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-free-plan.mdx
+++ b/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-free-plan.mdx
@@ -3,7 +3,7 @@ title: Hyperdrive Free plan makes fast, global database access available to all
 description: Hyperdrive is now available on the Free plan of Cloudflare Workers, enabling you to build Workers that connect to PostgreSQL or MySQL databases without compromise.
 products:
   - hyperdrive
-date: 2025-04-08T18:00:00Z
+date: 2025-04-08
 ---
 
 Hyperdrive is now available on the Free plan of Cloudflare Workers, enabling you to build Workers that connect to PostgreSQL or MySQL databases without compromise.
@@ -15,4 +15,4 @@ If you want to learn more about how Hyperdrive works, read the [deep dive](https
 
 ![Hyperdrive provides edge connection setup and global connection pooling for optimal latencies.](~/assets/images/hyperdrive/configuration/hyperdrive-global-placement.png)
 
-Visit the docs to [get started](/hyperdrive/get-started/) with Hyperdrive for PostgreSQL or MySQL.
\ No newline at end of file
+Visit the docs to [get started](/hyperdrive/get-started/) with Hyperdrive for PostgreSQL or MySQL.
diff --git a/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-mysql-support.mdx b/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-mysql-support.mdx
index 5f5d07c31138a0..ed940d62842f79 100644
--- a/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-mysql-support.mdx
+++ b/src/content/changelog/hyperdrive/2025-04-08-hyperdrive-mysql-support.mdx
@@ -3,7 +3,7 @@ title: Hyperdrive introduces support for MySQL and MySQL-compatible databases
 description: You can now connect to MySQL databases from your Workers using Hyperdrive for optimal performance
 products:
   - hyperdrive
-date: 2025-04-08T14:00:00Z
+date: 2025-04-08
 ---
 
 import { Code } from "~/components";
diff --git a/src/content/changelog/hyperdrive/2025-04-09-hyperdrive-custom-certificate-support.mdx b/src/content/changelog/hyperdrive/2025-04-09-hyperdrive-custom-certificate-support.mdx
index c56a44ba3997ae..03b51c49c062b1 100644
--- a/src/content/changelog/hyperdrive/2025-04-09-hyperdrive-custom-certificate-support.mdx
+++ b/src/content/changelog/hyperdrive/2025-04-09-hyperdrive-custom-certificate-support.mdx
@@ -3,7 +3,7 @@ title: Hyperdrive now supports custom TLS/SSL certificates
 description: You can now configure custom certificates for secure database connections with Hyperdrive, including both server certificate verification and client certificates
 products:
   - hyperdrive
-date: 2025-04-09T17:00:00Z
+date: 2025-04-09
 ---
 
 import { Code } from "~/components";
diff --git a/src/content/changelog/hyperdrive/2025-05-14-hyperdrive-fedramp.mdx b/src/content/changelog/hyperdrive/2025-05-14-hyperdrive-fedramp.mdx
index d249df939dd00a..178fd274fe62d6 100644
--- a/src/content/changelog/hyperdrive/2025-05-14-hyperdrive-fedramp.mdx
+++ b/src/content/changelog/hyperdrive/2025-05-14-hyperdrive-fedramp.mdx
@@ -3,7 +3,7 @@ title: Hyperdrive achieves FedRAMP Moderate-Impact Authorization
 description: Hyperdrive has been approved for FedRAMP Authorization and is now available in the FedRAMP Marketplace
 products:
   - hyperdrive
-date: 2025-05-14T17:00:00Z
+date: 2025-05-14
 ---
 
 import { Code } from "~/components";
diff --git a/src/content/changelog/hyperdrive/2025-07-02-hyperdrive-configurable-connection-count.mdx b/src/content/changelog/hyperdrive/2025-07-02-hyperdrive-configurable-connection-count.mdx
index 4bd381b0d6d875..43c3adb4c362d9 100644
--- a/src/content/changelog/hyperdrive/2025-07-02-hyperdrive-configurable-connection-count.mdx
+++ b/src/content/changelog/hyperdrive/2025-07-02-hyperdrive-configurable-connection-count.mdx
@@ -3,7 +3,7 @@ title: Hyperdrive now supports configuring the amount of database connections
 description: Hyperdrive configurations can now be set to use a specific number of connections to your origin database.
 products:
   - hyperdrive
-date: 2025-07-03T18:00:00Z
+date: 2025-07-03
 ---
 
 You can now specify the number of connections your Hyperdrive configuration uses to connect to your origin database.
diff --git a/src/content/changelog/images/2025-02-21-images-bindings-in-workers.mdx b/src/content/changelog/images/2025-02-21-images-bindings-in-workers.mdx
index c7c18b8ac656e2..a2ae817076c030 100644
--- a/src/content/changelog/images/2025-02-21-images-bindings-in-workers.mdx
+++ b/src/content/changelog/images/2025-02-21-images-bindings-in-workers.mdx
@@ -2,7 +2,7 @@
 title: "Bind the Images API to your Worker"
 description: >
   You can now interact with the Images API directly in your Worker with Image Bindings.
-date: 2025-02-24T12:00:00Z
+date: 2025-02-24
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/changelog/kv/2025-01-27-kv-increased-namespaces-limits.mdx b/src/content/changelog/kv/2025-01-27-kv-increased-namespaces-limits.mdx
index c18885b2c68b2b..0fc2bc34ef0840 100644
--- a/src/content/changelog/kv/2025-01-27-kv-increased-namespaces-limits.mdx
+++ b/src/content/changelog/kv/2025-01-27-kv-increased-namespaces-limits.mdx
@@ -3,7 +3,7 @@ title: Workers KV namespace limits increased to 1000
 description: You can now have up to 1000 Workers KV namespaces per account.
 products:
   - kv
-date: 2025-01-28T14:00:00Z
+date: 2025-01-28
 ---
 
 You can now have up to 1000 Workers KV namespaces per account.
diff --git a/src/content/changelog/kv/2025-04-10-kv-bulk-reads.mdx b/src/content/changelog/kv/2025-04-10-kv-bulk-reads.mdx
index 3a6c8958ebbdac..8d1219322aa239 100644
--- a/src/content/changelog/kv/2025-04-10-kv-bulk-reads.mdx
+++ b/src/content/changelog/kv/2025-04-10-kv-bulk-reads.mdx
@@ -3,7 +3,7 @@ title: Read multiple keys from Workers KV with bulk reads
 description: You can now retrieve up to 100 keys in a single bulk read request to Workers KV.
 products:
   - kv
-date: 2025-04-17T14:00:00Z
+date: 2025-04-17
 ---
 
 You can now retrieve up to 100 keys in a single bulk read request made to Workers KV using the binding.
diff --git a/src/content/changelog/log-explorer/2025-06-18-log-explorer-ga.mdx b/src/content/changelog/log-explorer/2025-06-18-log-explorer-ga.mdx
index c89b082380cd83..dcc68b3e976959 100644
--- a/src/content/changelog/log-explorer/2025-06-18-log-explorer-ga.mdx
+++ b/src/content/changelog/log-explorer/2025-06-18-log-explorer-ga.mdx
@@ -1,10 +1,10 @@
 ---
 title: Log Explorer is GA
 description: Log Explorer is now GA - providing native observability and forensics
-date: 2025-06-18T11:00:00Z
+date: 2025-06-18
 ---
- 
-[Log Explorer](/log-explorer/) is now GA, providing native observability and forensics for traffic flowing through Cloudflare. 
+
+[Log Explorer](/log-explorer/) is now GA, providing native observability and forensics for traffic flowing through Cloudflare.
 
 Search and analyze your logs, natively in the Cloudflare dashboard. These logs are also stored in Cloudflare's network, eliminating many of the costs associated with other log providers.
 
@@ -14,7 +14,7 @@ With Log Explorer, you can now:
 
 - **Monitor security and performance issues with custom dashboards** – use natural language to define charts for measuring response time, error rates, top statistics and more.
 - **Investigate and troubleshoot issues with Log Search** – use data type-aware search filters or custom sql to investigate detailed logs.
-- **Save time and collaborate with saved queries** – save Log Search queries for repeated use or sharing with other users in your account. 
+- **Save time and collaborate with saved queries** – save Log Search queries for repeated use or sharing with other users in your account.
 - **Access Log Explorer at the account and zone level** – easily find Log Explorer at the account and zone level for querying any dataset.
 
 For help getting started, refer to [our documentation](/log-explorer/).
diff --git a/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx b/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx
index 683361d40ee9f8..2a8d203bb7d9c3 100644
--- a/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx
+++ b/src/content/changelog/logs/2025-03-06-oneclick-logpush.mdx
@@ -1,14 +1,14 @@
 ---
 title: One-click Logpush Setup with R2 Object Storage
 description: Seamlessly configure Logpush to R2 in just one click.
-date: 2025-03-06T11:00:00Z
+date: 2025-03-06
 ---
 
-We’ve streamlined the [Logpush](/logs/get-started/) setup process by integrating R2 bucket creation directly into the Logpush workflow! 
+We’ve streamlined the [Logpush](/logs/get-started/) setup process by integrating R2 bucket creation directly into the Logpush workflow!
 
 Now, you no longer need to navigate multiple pages to manually create an R2 bucket or copy credentials. With this update, you can seamlessly **configure a Logpush job to R2 in just one click**, reducing friction and making setup faster and easier.
 
-This enhancement makes it easier for customers to adopt Logpush and R2. 
+This enhancement makes it easier for customers to adopt Logpush and R2.
 
 For more details refer to our [Logs](/logs/get-started/enable-destinations/r2/) documentation.
 
diff --git a/src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx b/src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx
index 50a083dd460a05..7b2738b31793f6 100644
--- a/src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx
+++ b/src/content/changelog/logs/2025-04-18-custom-fields-raw-transformed-values.mdx
@@ -1,7 +1,7 @@
 ---
 title: Custom fields raw and transformed values support
 description: Configure request header and response headers values can log eiterh raw or transformed value
-date: 2025-04-18T11:00:00Z
+date: 2025-04-18
 ---
 
 Custom Fields now support logging both **raw and transformed values** for request and response headers in the HTTP requests dataset.
diff --git a/src/content/changelog/magic-cloud-networking/2024-12-05-cloud-onramp-terraform.mdx b/src/content/changelog/magic-cloud-networking/2024-12-05-cloud-onramp-terraform.mdx
index 867ad9d7bd1c6a..9201d66004ce89 100644
--- a/src/content/changelog/magic-cloud-networking/2024-12-05-cloud-onramp-terraform.mdx
+++ b/src/content/changelog/magic-cloud-networking/2024-12-05-cloud-onramp-terraform.mdx
@@ -1,7 +1,7 @@
 ---
 title: Generate customized terraform files for building cloud network on-ramps
 description: Download cloud onramp terraform
-date: 2024-12-05T11:00:00Z
+date: 2024-12-05
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/changelog/magic-firewall/2024-10-02-custom-rule-search.mdx b/src/content/changelog/magic-firewall/2024-10-02-custom-rule-search.mdx
index 3f35841971b303..a749a5dd7b5d6d 100644
--- a/src/content/changelog/magic-firewall/2024-10-02-custom-rule-search.mdx
+++ b/src/content/changelog/magic-firewall/2024-10-02-custom-rule-search.mdx
@@ -1,7 +1,7 @@
 ---
 title: Search for custom rules using rule name and/or ID
 description: New UI improvements for Magic Firewall
-date: 2024-10-02T11:00:00Z
+date: 2024-10-02
 ---
 
 The Magic Firewall dashboard now allows you to search custom rules using the rule name and/or ID.
diff --git a/src/content/changelog/magic-network-monitoring/2024-09-24-magic-network-monitoring.mdx b/src/content/changelog/magic-network-monitoring/2024-09-24-magic-network-monitoring.mdx
index ad2d0f4dc92e95..47fd21ccaa6001 100644
--- a/src/content/changelog/magic-network-monitoring/2024-09-24-magic-network-monitoring.mdx
+++ b/src/content/changelog/magic-network-monitoring/2024-09-24-magic-network-monitoring.mdx
@@ -1,7 +1,7 @@
 ---
 title: Try out Magic Network Monitoring
 description: The free version of Magic Network Monitoring is available to all customers
-date: 2024-09-24T11:00:00Z
+date: 2024-09-24
 ---
 
 The free version of Magic Network Monitoring (MNM) is now available to everyone with a Cloudflare account by default.
diff --git a/src/content/changelog/magic-wan/2025-02-14-local-console-access.mdx b/src/content/changelog/magic-wan/2025-02-14-local-console-access.mdx
index 741ae819498f71..02bc05b2f601ad 100644
--- a/src/content/changelog/magic-wan/2025-02-14-local-console-access.mdx
+++ b/src/content/changelog/magic-wan/2025-02-14-local-console-access.mdx
@@ -1,7 +1,7 @@
 ---
 title: Configure your Magic WAN Connector to connect via static IP assigment
 description: Local console access for bootstrapping Magic WAN Connector
-date: 2025-02-14T11:00:00Z
+date: 2025-02-14
 ---
 
 You can now locally configure your [Magic WAN Connector](/magic-wan/configuration/connector/) to work in a static IP configuration.
diff --git a/src/content/changelog/network-interconnect/2024-12-17-bgp-support-cni.mdx b/src/content/changelog/network-interconnect/2024-12-17-bgp-support-cni.mdx
index 382a1988c6c70c..d7539219b3c27a 100644
--- a/src/content/changelog/network-interconnect/2024-12-17-bgp-support-cni.mdx
+++ b/src/content/changelog/network-interconnect/2024-12-17-bgp-support-cni.mdx
@@ -1,7 +1,7 @@
 ---
 title: Establish BGP peering over Direct CNI circuits
 description: BGP support for Cloudflare Network Interconnect (CNI)
-date: 2024-12-17T11:00:00Z
+date: 2024-12-17
 products:
   - magic-transit
   - magic-wan
diff --git a/src/content/changelog/pipelines/2025-04-10-launching-pipelines.mdx b/src/content/changelog/pipelines/2025-04-10-launching-pipelines.mdx
index 289689c51f6bec..b97f8ffdf62270 100644
--- a/src/content/changelog/pipelines/2025-04-10-launching-pipelines.mdx
+++ b/src/content/changelog/pipelines/2025-04-10-launching-pipelines.mdx
@@ -5,7 +5,7 @@ products:
   - pipelines
   - r2
   - workers
-date: 2025-04-10T12:00:00Z
+date: 2025-04-10
 ---
 
 [Cloudflare Pipelines](/pipelines) is now available in beta, to all users with a [Workers Paid](/workers/platform/pricing) plan.
diff --git a/src/content/changelog/r2/2025-02-14-r2-super-slurper-faster-migrations.mdx b/src/content/changelog/r2/2025-02-14-r2-super-slurper-faster-migrations.mdx
index c9b893fec24a06..5fe8784da3dd49 100644
--- a/src/content/changelog/r2/2025-02-14-r2-super-slurper-faster-migrations.mdx
+++ b/src/content/changelog/r2/2025-02-14-r2-super-slurper-faster-migrations.mdx
@@ -3,7 +3,7 @@ title: Super Slurper now transfers data to R2 up to 5x faster
 description: Super Slurper now transfers data from cloud object storage providers like AWS S3 and Google Cloud Storage to Cloudflare R2 up to 5x faster
 products:
   - r2
-date: 2025-02-14T19:00:00Z
+date: 2025-02-14
 ---
 
 [Super Slurper](/r2/data-migration/super-slurper/) now transfers data from cloud object storage providers like AWS S3 and Google Cloud Storage to [Cloudflare R2](/r2/) up to 5x faster than it did before.
diff --git a/src/content/changelog/r2/2025-02-24-r2-super-slurper-s3-compatible-support.mdx b/src/content/changelog/r2/2025-02-24-r2-super-slurper-s3-compatible-support.mdx
index 46bc49013ae889..616f6cc8472325 100644
--- a/src/content/changelog/r2/2025-02-24-r2-super-slurper-s3-compatible-support.mdx
+++ b/src/content/changelog/r2/2025-02-24-r2-super-slurper-s3-compatible-support.mdx
@@ -3,7 +3,7 @@ title: Super Slurper now supports migrations from all S3-compatible storage prov
 description: Super Slurper now supports migrations from all S3-compatible storage providers
 products:
   - r2
-date: 2025-02-24T19:00:00Z
+date: 2025-02-24
 ---
 
 [Super Slurper](/r2/data-migration/super-slurper/) can now migrate data from any S3-compatible object storage provider to [Cloudflare R2](/r2/). This includes transfers from services like MinIO, Wasabi, Backblaze B2, and DigitalOcean Spaces.
diff --git a/src/content/changelog/r2/2025-03-06-r2-bucket-locks.mdx b/src/content/changelog/r2/2025-03-06-r2-bucket-locks.mdx
index 6de77053611bd7..7dc72deff29156 100644
--- a/src/content/changelog/r2/2025-03-06-r2-bucket-locks.mdx
+++ b/src/content/changelog/r2/2025-03-06-r2-bucket-locks.mdx
@@ -3,7 +3,7 @@ title: Set retention polices for your R2 bucket with bucket locks
 description: Set retention polices for your R2 bucket with bucket locks
 products:
   - r2
-date: 2025-03-06T10:00:00Z
+date: 2025-03-06
 ---
 
 You can now use [bucket locks](/r2/buckets/bucket-locks/) to set retention policies on your [R2 buckets](/r2/buckets/) (or specific prefixes within your buckets) for a specified period — or indefinitely. This can help ensure compliance by protecting important data from accidental or malicious deletion.
diff --git a/src/content/changelog/r2/2025-04-10-r2-data-catalog-beta.mdx b/src/content/changelog/r2/2025-04-10-r2-data-catalog-beta.mdx
index 12ae0a7911f974..94a9d753f6862e 100644
--- a/src/content/changelog/r2/2025-04-10-r2-data-catalog-beta.mdx
+++ b/src/content/changelog/r2/2025-04-10-r2-data-catalog-beta.mdx
@@ -3,7 +3,7 @@ title: R2 Data Catalog is a managed Apache Iceberg data catalog built directly i
 description: A managed Apache Iceberg data catalog built directly into R2 buckets
 products:
   - r2
-date: 2025-04-10T13:00:00Z
+date: 2025-04-10
 ---
 
 Today, we're launching [R2 Data Catalog](/r2/data-catalog/) in open beta, a managed Apache Iceberg catalog built directly into your [Cloudflare R2](/r2/) bucket.
diff --git a/src/content/changelog/r2/2025-05-01-r2-dashboard-updates.mdx b/src/content/changelog/r2/2025-05-01-r2-dashboard-updates.mdx
index 3e021c29c07fd7..63673317863590 100644
--- a/src/content/changelog/r2/2025-05-01-r2-dashboard-updates.mdx
+++ b/src/content/changelog/r2/2025-05-01-r2-dashboard-updates.mdx
@@ -3,14 +3,13 @@ title: R2 Dashboard experience gets new updates
 description: R2 Dashboard experience gets new updates
 products:
   - r2
-date: 2025-05-01T13:00:00Z
+date: 2025-05-01
 ---
 
 We're excited to announce several improvements to the [Cloudflare R2](/r2/) dashboard experience that make managing your object storage easier and more intuitive:
 
 ![Cloudflare R2 Dashboard](~/assets/images/r2/r2-dashboard-updates.png)
 
-
 #### All-new settings page
 
 We've redesigned the bucket settings page, giving you a centralized location to manage all your bucket configurations in one place.
@@ -25,4 +24,4 @@ We've redesigned the bucket settings page, giving you a centralized location to
 - Renamed "r2.dev domain" to "Public Development URL" for better clarity when exposing bucket contents for non-production workloads.
 - Public Access status now clearly displays "Enabled" when your bucket is exposed to the internet (via Public Development URL or Custom Domains).
 
-We've also made numerous other usability improvements across the board to make your R2 experience smoother and more productive.
\ No newline at end of file
+We've also made numerous other usability improvements across the board to make your R2 experience smoother and more productive.
diff --git a/src/content/changelog/radar/2025-02-04-radar-ai-insights.mdx b/src/content/changelog/radar/2025-02-04-radar-ai-insights.mdx
index 9b83c516598e03..4e8f88cdc6d927 100644
--- a/src/content/changelog/radar/2025-02-04-radar-ai-insights.mdx
+++ b/src/content/changelog/radar/2025-02-04-radar-ai-insights.mdx
@@ -3,7 +3,7 @@ title: Expanded AI insights in Cloudflare Radar
 description: Expanded AI insights with new API endpoints for Internet services rankings, robots.txt, and inference data
 products:
   - radar
-date: 2025-02-04T11:00:00Z
+date: 2025-02-04
 ---
 
 [**Radar**](/radar/) has expanded its AI insights with new API endpoints for Internet services rankings, robots.txt analysis, and AI inference data.
diff --git a/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx b/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx
index 28cc89fbb154f8..b8618431a83c30 100644
--- a/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx
+++ b/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx
@@ -3,7 +3,7 @@ title: DNS Insights in Cloudflare Radar
 description: Expanded DNS insights with new API endpoints for 1.1.1.1 resolver aggregated traffic data
 products:
   - radar
-date: 2025-02-27T15:00:00Z
+date: 2025-02-27
 ---
 
 [**Radar**](/radar/) has expanded its DNS insights, providing visibility into aggregated traffic and usage trends observed by our [1.1.1.1](/1.1.1.1/) DNS resolver.
@@ -28,5 +28,4 @@ For the `summary` and `timeseries_groups` endpoints, the following dimensions ar
 - `response_code`: Response code (`NOERROR`, `NXDOMAIN`, `REFUSED`, etc.).
 - `response_ttl`: Response TTL.
 
-
 Learn more about the new Radar DNS insights in our [blog post](https://blog.cloudflare.com/new-dns-section-on-cloudflare-radar/), and check out the [new Radar page](https://radar.cloudflare.com/dns).
diff --git a/src/content/changelog/radar/2025-03-18-radar-leaked-credentials-insights.mdx b/src/content/changelog/radar/2025-03-18-radar-leaked-credentials-insights.mdx
index 6a049555afbee8..0555e4d6c710d9 100644
--- a/src/content/changelog/radar/2025-03-18-radar-leaked-credentials-insights.mdx
+++ b/src/content/changelog/radar/2025-03-18-radar-leaked-credentials-insights.mdx
@@ -3,7 +3,7 @@ title: Leaked Credentials Insights in Cloudflare Radar
 description: Expanded security insights with new API endpoints for aggregated authentication request data
 products:
   - radar
-date: 2025-03-18T14:00:00Z
+date: 2025-03-18
 ---
 
 [**Radar**](/radar/) has expanded its security insights, providing visibility into aggregate trends in authentication requests,
@@ -19,5 +19,4 @@ The following dimensions are available, displaying the distribution of HTTP auth
 - `compromised`: Credential status (clean vs. compromised).
 - `bot_class`: [Bot class](/radar/concepts/bot-classes) (human vs. bot).
 
-
 Dive deeper into leaked credential detection in this [blog post](https://blog.cloudflare.com/password-reuse-rampant-half-user-logins-compromised/) and learn more about the expanded Radar security insights in our [blog post](https://blog.cloudflare.com/cloudflare-radar-ddos-leaked-credentials-bots).
diff --git a/src/content/changelog/radar/2025-07-01-radar-bots-insights.mdx b/src/content/changelog/radar/2025-07-01-radar-bots-insights.mdx
index 885d274c2fcc83..63185d7cb997b2 100644
--- a/src/content/changelog/radar/2025-07-01-radar-bots-insights.mdx
+++ b/src/content/changelog/radar/2025-07-01-radar-bots-insights.mdx
@@ -3,7 +3,7 @@ title: Bot & Crawler Insights in Cloudflare Radar
 description: Expanded visibility into crawler, referral, and bot activity with new Radar API endpoints.
 products:
   - radar
-date: 2025-07-01T12:00:00Z
+date: 2025-07-01
 ---
 
 ### Web crawlers insights
@@ -25,17 +25,17 @@ These endpoints allow analysis across the following dimensions:
 
 In addition to crawler-specific insights, Radar now provides a broader set of bot endpoints:
 
-* [`/bots/`](/api/resources/radar/subresources/bots/): Lists all bots.
-* [`/bots/:bot_slug`](/api/resources/radar/subresources/bots/methods/get/): Returns detailed metadata for a specific bot.
-* [`/bots/timeseries`](/api/resources/radar/subresources/bots/methods/timeseries/): Time-series data for bot activity.
-* [`/bots/summary`](/api/resources/radar/subresources/bots/methods/summary/): Returns an overview of bot HTTP request distributions across key dimensions.
-* [`/bots/timeseries_groups`](/api/resources/radar/subresources/bots/methods/timeseries_groups/): Provides time-series data on bot request distributions across the same dimensions.
+- [`/bots/`](/api/resources/radar/subresources/bots/): Lists all bots.
+- [`/bots/:bot_slug`](/api/resources/radar/subresources/bots/methods/get/): Returns detailed metadata for a specific bot.
+- [`/bots/timeseries`](/api/resources/radar/subresources/bots/methods/timeseries/): Time-series data for bot activity.
+- [`/bots/summary`](/api/resources/radar/subresources/bots/methods/summary/): Returns an overview of bot HTTP request distributions across key dimensions.
+- [`/bots/timeseries_groups`](/api/resources/radar/subresources/bots/methods/timeseries_groups/): Provides time-series data on bot request distributions across the same dimensions.
 
 These endpoints support filtering and breakdowns by:
 
-* `bot`: Bot name.
-* `bot_operator`: The organization or entity operating the bot.
-* `bot_category`: Classification of bot type.
+- `bot`: Bot name.
+- `bot_operator`: The organization or entity operating the bot.
+- `bot_category`: Classification of bot type.
 
 The previously available `verified_bots` endpoints have now been deprecated in favor of this set of bot insights APIs.
 While current data still focuses on verified bots, we plan to expand support for unverified bot traffic in the future.
diff --git a/src/content/changelog/risk-score/2024-06-17-okta-risk-exchange.mdx b/src/content/changelog/risk-score/2024-06-17-okta-risk-exchange.mdx
index f509ee8db3e1c3..38c8e2c55a7031 100644
--- a/src/content/changelog/risk-score/2024-06-17-okta-risk-exchange.mdx
+++ b/src/content/changelog/risk-score/2024-06-17-okta-risk-exchange.mdx
@@ -1,7 +1,7 @@
 ---
 title: Exchange user risk scores with Okta
 description: Okta risk exchange
-date: 2024-06-17T11:00:00Z
+date: 2024-06-17
 ---
 
 import { Render } from "~/components";
diff --git a/src/content/changelog/rules/2024-09-05-rules-templates.mdx b/src/content/changelog/rules/2024-09-05-rules-templates.mdx
index 127c3006c8980d..96f02d3c3d6d39 100644
--- a/src/content/changelog/rules/2024-09-05-rules-templates.mdx
+++ b/src/content/changelog/rules/2024-09-05-rules-templates.mdx
@@ -3,7 +3,7 @@ title: New Rules Templates for One-Click Rule Creation
 description: Quickly set up common rules with pre-built templates.
 products:
   - rules
-date: 2024-09-05T11:00:00Z
+date: 2024-09-05
 ---
 
 Now, you can create **common rule configurations** in just **one click** using Rules Templates.
@@ -11,6 +11,7 @@ Now, you can create **common rule configurations** in just **one click** using R
 ![Rules Templates](~/assets/images/changelog/rules/rules-templates.gif)
 
 What you can do:
+
 - **Pick a pre-built rule** – Choose from a library of templates.
 - **One-click setup** – Deploy best practices instantly.
 - **Customize as needed** – Adjust templates to fit your setup.
diff --git a/src/content/changelog/rules/2024-10-23-url-rewrites-wildcard.mdx b/src/content/changelog/rules/2024-10-23-url-rewrites-wildcard.mdx
index 4db7988be369e4..fbc0f750f2eb26 100644
--- a/src/content/changelog/rules/2024-10-23-url-rewrites-wildcard.mdx
+++ b/src/content/changelog/rules/2024-10-23-url-rewrites-wildcard.mdx
@@ -3,7 +3,7 @@ title: Simplified UI for URL Rewrites
 description: Set up wildcard-based URL rewrites faster with a new streamlined UI.
 products:
   - rules
-date: 2024-10-23T11:00:00Z
+date: 2024-10-23
 ---
 
 It’s now easy to create **wildcard-based [URL Rewrites](/rules/transform/url-rewrite/)**. No need for complex functions—just define your patterns and go.
@@ -11,6 +11,7 @@ It’s now easy to create **wildcard-based [URL Rewrites](/rules/transform/url-r
 ![Rules Overview Interface](~/assets/images/rules/transform/create-url-rewrite-rule.png)
 
 What’s improved:
+
 - **Full wildcard support** – Create rewrite patterns using intuitive interface.
 - **Simplified rule creation** – No need for complex functions.
 
diff --git a/src/content/changelog/rules/2024-11-22-cloud-connector-r2.mdx b/src/content/changelog/rules/2024-11-22-cloud-connector-r2.mdx
index dba1beb0911bd9..8d546d46006e4d 100644
--- a/src/content/changelog/rules/2024-11-22-cloud-connector-r2.mdx
+++ b/src/content/changelog/rules/2024-11-22-cloud-connector-r2.mdx
@@ -3,7 +3,7 @@ title: Cloud Connector Now Supports R2
 description: Cloud Connector now integrates with Cloudflare R2 for object storage.
 products:
   - rules
-date: 2024-11-22T11:00:00Z
+date: 2024-11-22
 ---
 
 Now, you can use [Cloud Connector](/rules/cloud-connector/) to route traffic to your [R2 buckets](/r2/) based on URLs, headers, geolocation, and more.
diff --git a/src/content/changelog/rules/2024-12-11-terraform-snippets.mdx b/src/content/changelog/rules/2024-12-11-terraform-snippets.mdx
index 73ab109cf257c8..b06f20363d6979 100644
--- a/src/content/changelog/rules/2024-12-11-terraform-snippets.mdx
+++ b/src/content/changelog/rules/2024-12-11-terraform-snippets.mdx
@@ -3,7 +3,7 @@ title: Terraform Support for Snippets
 description: Automate Snippet deployments with Terraform.
 products:
   - rules
-date: 2024-12-11T11:00:00Z
+date: 2024-12-11
 ---
 
 Now, you can manage [Cloudflare Snippets](/rules/snippets/) with [Terraform](/terraform/). Use infrastructure-as-code to deploy and update Snippet code and rules without manual changes in the dashboard.
@@ -33,4 +33,4 @@ resource "cloudflare_snippet_rules" "cookie_snippet_rule" {
 }
 ```
 
-Learn more in the [Configure Snippets using Terraform](/rules/snippets/create-terraform/) documentation.
\ No newline at end of file
+Learn more in the [Configure Snippets using Terraform](/rules/snippets/create-terraform/) documentation.
diff --git a/src/content/changelog/rules/2025-01-09-rules-overview.mdx b/src/content/changelog/rules/2025-01-09-rules-overview.mdx
index 09376743249ca7..f9566b538e6a11 100644
--- a/src/content/changelog/rules/2025-01-09-rules-overview.mdx
+++ b/src/content/changelog/rules/2025-01-09-rules-overview.mdx
@@ -3,7 +3,7 @@ title: New Rules Overview Interface
 description: Manage all your rules in one place with the new Rules Overview.
 products:
   - rules
-date: 2025-01-09T11:00:00Z
+date: 2025-01-09
 ---
 
 **Rules Overview** gives you a single page to manage all your [Cloudflare Rules](/rules/).
diff --git a/src/content/changelog/rules/2025-01-29-snippets-code-editor.mdx b/src/content/changelog/rules/2025-01-29-snippets-code-editor.mdx
index 1c44cc7e207fa1..c61b94efa699bd 100644
--- a/src/content/changelog/rules/2025-01-29-snippets-code-editor.mdx
+++ b/src/content/changelog/rules/2025-01-29-snippets-code-editor.mdx
@@ -3,7 +3,7 @@ title: New Snippets Code Editor
 description: Edit Snippets and rules in one place with the new built-in code editor.
 products:
   - rules
-date: 2025-01-29T11:00:00Z
+date: 2025-01-29
 ---
 
 The new [Snippets](/rules/snippets/) code editor lets you edit Snippet code and rule in one place, making it easier to test and deploy changes without switching between pages.
@@ -11,6 +11,7 @@ The new [Snippets](/rules/snippets/) code editor lets you edit Snippet code and
 ![New Snippets code editor](~/assets/images/changelog/rules/snippets-new-editor.png)
 
 What’s new:
+
 - **Single-page editing for code and rule** – No need to jump between screens.
 - **Auto-complete & syntax highlighting** – Get suggestions and avoid mistakes.
 - **Code formatting & refactoring** – Write cleaner, more readable code.
diff --git a/src/content/changelog/rules/2025-02-11-custom-errors-beta.mdx b/src/content/changelog/rules/2025-02-11-custom-errors-beta.mdx
index d59d255f1e9c20..ccb5e514defb1d 100644
--- a/src/content/changelog/rules/2025-02-11-custom-errors-beta.mdx
+++ b/src/content/changelog/rules/2025-02-11-custom-errors-beta.mdx
@@ -3,7 +3,7 @@ title: "Custom Errors (beta): Stored Assets & Account-level Rules"
 description: Cloudflare introduces Custom Errors (beta), building on Custom Error Responses with new asset storage capabilities
 products:
   - rules
-date: 2025-02-11T11:00:00Z
+date: 2025-02-11
 ---
 
 We're introducing [Custom Errors](/rules/custom-errors/) (beta), which builds on our existing Custom Error Responses feature with new asset storage capabilities.
diff --git a/src/content/changelog/rules/2025-02-12-rules-upgraded-limits.mdx b/src/content/changelog/rules/2025-02-12-rules-upgraded-limits.mdx
index c8db89019cf1bd..066d4d47aa195c 100644
--- a/src/content/changelog/rules/2025-02-12-rules-upgraded-limits.mdx
+++ b/src/content/changelog/rules/2025-02-12-rules-upgraded-limits.mdx
@@ -3,31 +3,13 @@ title: Increased Cloudflare Rules limits
 description: We have upgraded and streamlined limits for Cloudflare Rules products for everyone.
 products:
   - rules
-date: 2025-02-12T19:00:00Z
+date: 2025-02-12
 ---
 
 We have upgraded and streamlined [Cloudflare Rules](/rules/) limits across all plans, simplifying rule management and improving scalability for everyone.
 
-**New limits by product:**
-      - [Bulk Redirects](/rules/url-forwarding/bulk-redirects/)
-        - Free: **20** → **10,000** URL redirects across lists
-        - Pro: **500** → **25,000** URL redirects across lists
-        - Business: **500** → **50,000** URL redirects across lists
-        - Enterprise: **10,000** → **1,000,000** URL redirects across lists
-      - [Cloud Connector](/rules/cloud-connector/)
-        - Free: **5** → **10** connectors
-        - Enterprise: **125** → **300** connectors
-      - [Custom Errors](/rules/custom-errors/)
-        - Pro: **5** → **25** error assets and rules
-        - Business: **20** → **50** error assets and rules
-        - Enterprise: **50** → **300** error assets and rules
-      - [Snippets](/rules/snippets/)
-        - Pro: **10** → **25** code snippets and rules
-        - Business: **25** → **50** code snippets and rules
-        - Enterprise: **50** → **300** code snippets and rules
-      - [Cache Rules](/cache/how-to/cache-rules/), [Configuration Rules](/rules/configuration-rules/), [Compression Rules](/rules/compression-rules/), [Origin Rules](/rules/origin-rules/), [Single Redirects](/rules/url-forwarding/single-redirects/), and [Transform Rules](/rules/transform/)
-        - Enterprise: **125** → **300** rules
+**New limits by product:** - [Bulk Redirects](/rules/url-forwarding/bulk-redirects/) - Free: **20** → **10,000** URL redirects across lists - Pro: **500** → **25,000** URL redirects across lists - Business: **500** → **50,000** URL redirects across lists - Enterprise: **10,000** → **1,000,000** URL redirects across lists - [Cloud Connector](/rules/cloud-connector/) - Free: **5** → **10** connectors - Enterprise: **125** → **300** connectors - [Custom Errors](/rules/custom-errors/) - Pro: **5** → **25** error assets and rules - Business: **20** → **50** error assets and rules - Enterprise: **50** → **300** error assets and rules - [Snippets](/rules/snippets/) - Pro: **10** → **25** code snippets and rules - Business: **25** → **50** code snippets and rules - Enterprise: **50** → **300** code snippets and rules - [Cache Rules](/cache/how-to/cache-rules/), [Configuration Rules](/rules/configuration-rules/), [Compression Rules](/rules/compression-rules/), [Origin Rules](/rules/origin-rules/), [Single Redirects](/rules/url-forwarding/single-redirects/), and [Transform Rules](/rules/transform/) - Enterprise: **125** → **300** rules
 
 :::note[Gradual rollout]
 Limits are updated gradually. Some customers may still see previous limits until the rollout is fully completed in the first half of 2025.
-:::
\ No newline at end of file
+:::
diff --git a/src/content/changelog/rules/2025-04-09-snippets-ga.mdx b/src/content/changelog/rules/2025-04-09-snippets-ga.mdx
index 740b6b327b94d1..ba84497da2e09b 100644
--- a/src/content/changelog/rules/2025-04-09-snippets-ga.mdx
+++ b/src/content/changelog/rules/2025-04-09-snippets-ga.mdx
@@ -3,7 +3,7 @@ title: Cloudflare Snippets are now Generally Available
 description: Snippets let you program HTTP traffic with lightweight JavaScript — now GA and ready for production.
 products:
   - rules
-date: 2025-04-09T14:00:00Z
+date: 2025-04-09
 ---
 
 ![Cloudflare Snippets are now GA](~/assets/images/changelog/rules/snippets-ga.png)
diff --git a/src/content/changelog/rules/2025-04-24-custom-errors-ga.mdx b/src/content/changelog/rules/2025-04-24-custom-errors-ga.mdx
index 9de114197c8795..edd6bde9acc757 100644
--- a/src/content/changelog/rules/2025-04-24-custom-errors-ga.mdx
+++ b/src/content/changelog/rules/2025-04-24-custom-errors-ga.mdx
@@ -3,7 +3,7 @@ title: Custom Errors are now Generally Available
 description: A new UI for error handling is now available — letting you manage Error Pages, Custom Error Rules, and Assets from the dashboard.
 products:
   - rules
-date: 2025-04-24T17:00:00Z
+date: 2025-04-24
 ---
 
 [Custom Errors](/rules/custom-errors/) are now generally available for all paid plans — bringing a unified and powerful experience for customizing error responses at both the zone and account levels.
@@ -11,6 +11,7 @@ date: 2025-04-24T17:00:00Z
 You can now manage **Custom Error Rules**, **Custom Error Assets**, and redesigned **Error Pages** directly from the Cloudflare dashboard. These features let you deliver tailored messaging when errors occur, helping you maintain brand consistency and improve user experience — whether it’s a 404 from your origin or a security challenge from Cloudflare.
 
 What's new:
+
 - **Custom Errors are now GA** – Available on all paid plans and ready for production traffic.
 - **UI for Custom Error Rules and Assets** – Manage your zone-level rules from the Rules > Overview and your zone-level assets from the Rules > Settings tabs.
 - **Define inline content or upload assets** – Create custom responses directly in the rule builder, upload new or reuse previously stored assets.
@@ -19,4 +20,4 @@ What's new:
 
 ![Custom Errors GA](~/assets/images/changelog/rules/custom-errors.gif)
 
-Learn more in the [Custom Errors documentation](/rules/custom-errors/).
\ No newline at end of file
+Learn more in the [Custom Errors documentation](/rules/custom-errors/).
diff --git a/src/content/changelog/rules/2025-05-09-snippets-cloud-connector-lists-waf-bot-scores.mdx b/src/content/changelog/rules/2025-05-09-snippets-cloud-connector-lists-waf-bot-scores.mdx
index 02b33757f78cfa..b5e6c11e038da8 100644
--- a/src/content/changelog/rules/2025-05-09-snippets-cloud-connector-lists-waf-bot-scores.mdx
+++ b/src/content/changelog/rules/2025-05-09-snippets-cloud-connector-lists-waf-bot-scores.mdx
@@ -3,7 +3,7 @@ title: More ways to match — Snippets now support Custom Lists, Bot Score, and
 description: Snippets and Cloud Connector now support user-defined IP, AS, and Hostname Custom Lists — plus Bot Score and WAF Attack Score in Snippets.
 products:
   - rules
-date: 2025-05-09T10:00:00Z
+date: 2025-05-09
 ---
 
 You can now use IP, Autonomous System (AS), and Hostname [custom lists](/waf/tools/lists/custom-lists/) to route traffic to [Snippets](/rules/snippets/) and [Cloud Connector](/rules/cloud-connector/), giving you greater precision and control over how you match and process requests at the edge.
@@ -11,6 +11,7 @@ You can now use IP, Autonomous System (AS), and Hostname [custom lists](/waf/too
 In Snippets, you can now also match on [Bot Score](/bots/concepts/bot-score/) and [WAF Attack Score](/waf/detections/attack-score/), unlocking smarter edge logic for everything from request filtering and mitigation to [tarpitting](/rules/snippets/examples/slow-suspicious-requests/) and logging.
 
 **What’s new:**
+
 - [Custom lists](/waf/tools/lists/custom-lists/) matching – Snippets and Cloud Connector now support user-created IP, AS, and Hostname lists via dashboard or [Lists API](/api/resources/rules/subresources/lists/methods/list/). Great for shared logic across zones.
 - [Bot Score](/bots/concepts/bot-score/) and [WAF Attack Score](/waf/detections/attack-score/) – Use Cloudflare’s intelligent traffic signals to detect bots or attacks and take advanced, tailored actions with just a few lines of code.
 
@@ -18,4 +19,4 @@ In Snippets, you can now also match on [Bot Score](/bots/concepts/bot-score/) an
 
 These enhancements unlock new possibilities for building smarter traffic workflows with minimal code and maximum efficiency.
 
-Learn more in the [Snippets](/rules/snippets/) and [Cloud Connector](/rules/cloud-connector/) documentation.
\ No newline at end of file
+Learn more in the [Snippets](/rules/snippets/) and [Cloud Connector](/rules/cloud-connector/) documentation.
diff --git a/src/content/changelog/rules/2025-05-30-configuration-rules-webp.mdx b/src/content/changelog/rules/2025-05-30-configuration-rules-webp.mdx
index d12dfb860b1da0..7f2ab602079bc8 100644
--- a/src/content/changelog/rules/2025-05-30-configuration-rules-webp.mdx
+++ b/src/content/changelog/rules/2025-05-30-configuration-rules-webp.mdx
@@ -3,16 +3,17 @@ title: Fine-tune image optimization — WebP now supported in Configuration Rule
 description: Configuration Rules now let you selectively enable or disable Polish with WebP format for precise control over image optimization.
 products:
   - rules
-date: 2025-05-30T17:00:00Z
+date: 2025-05-30
 ---
 
 You can now enable [Polish](/images/polish/activate-polish/) with the `webp` format directly in [Configuration Rules](/rules/configuration-rules/), allowing you to optimize image delivery for specific routes, user agents, or A/B tests — without applying changes zone-wide.
 
 **What’s new:**
+
 - [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.
\ No newline at end of file
+Learn more in the [Polish](/images/polish/) and [Configuration Rules](/rules/configuration-rules/) documentation.
diff --git a/src/content/changelog/rules/2025-06-09-custom-errors-fetch-4xx-5xx-assets.mdx b/src/content/changelog/rules/2025-06-09-custom-errors-fetch-4xx-5xx-assets.mdx
index a07342434d447d..6c4267699115d4 100644
--- a/src/content/changelog/rules/2025-06-09-custom-errors-fetch-4xx-5xx-assets.mdx
+++ b/src/content/changelog/rules/2025-06-09-custom-errors-fetch-4xx-5xx-assets.mdx
@@ -3,15 +3,16 @@ title: More flexible fallback handling — Custom Errors now support fetching as
 description: Custom Errors can now fetch and store fallback assets even if the origin returns a 4xx or 5xx status code.
 products:
   - rules
-date: 2025-06-09T18:00:00Z
+date: 2025-06-09
 ---
 
 [Custom Errors](/rules/custom-errors/) can now fetch and store [assets](/rules/custom-errors/create-rules/#create-a-custom-error-asset-dashboard) and [error pages](/rules/custom-errors/#error-pages) from your origin even if they are served with a 4xx or 5xx HTTP status code — previously, only 200 OK responses were allowed.
 
 **What’s new:**
+
 - You can now upload error pages and error assets that return error status codes (for example, 403, 500, 502, 503, 504) when fetched.
 - These assets are stored and minified at the edge, so they can be reused across multiple Custom Error rules without triggering requests to the origin.
 
 This is especially useful for retrieving error content or downtime banners from your backend when you can’t override the origin status code.
 
-Learn more in the [Custom Errors](/rules/custom-errors/) documentation.
\ No newline at end of file
+Learn more in the [Custom Errors](/rules/custom-errors/) documentation.
diff --git a/src/content/changelog/rules/2025-06-09-transform-rule-subrequest-matching.mdx b/src/content/changelog/rules/2025-06-09-transform-rule-subrequest-matching.mdx
index 9bb4667cf9b852..dc5f87aa8ed561 100644
--- a/src/content/changelog/rules/2025-06-09-transform-rule-subrequest-matching.mdx
+++ b/src/content/changelog/rules/2025-06-09-transform-rule-subrequest-matching.mdx
@@ -3,7 +3,7 @@ title: Match Workers subrequests by upstream zone — cf.worker.upstream_zone no
 description: Transform Rules now support the cf.worker.upstream_zone field, letting you conditionally apply rules based on which zone sent Workers subrequest.
 products:
   - rules
-date: 2025-06-09T17:00:00Z
+date: 2025-06-09
 ---
 
 import { Example } from "~/components";
diff --git a/src/content/changelog/security-center/2025-05-07-url-scanner-geoegress.mdx b/src/content/changelog/security-center/2025-05-07-url-scanner-geoegress.mdx
index 5d68449675e80e..9c244128bc1816 100644
--- a/src/content/changelog/security-center/2025-05-07-url-scanner-geoegress.mdx
+++ b/src/content/changelog/security-center/2025-05-07-url-scanner-geoegress.mdx
@@ -2,8 +2,8 @@
 title: URL Scanner now supports geo-specific scanning
 description: Enterprise users can now choose the location from which URL scans are performed.
 products:
-    - security-center
-date: 2025-05-08T14:00:00Z
+  - security-center
+date: 2025-05-08
 ---
 
 Enterprise customers can now choose the geographic location from which a URL scan is performed — either via [Security Center](/security-center/investigate/) in the Cloudflare dashboard or via the [URL Scanner API](/api/resources/url_scanner/subresources/scans/methods/create/).
@@ -11,8 +11,9 @@ Enterprise customers can now choose the geographic location from which a URL sca
 This feature gives security teams greater insight into how a website behaves across different regions, helping uncover targeted, location-specific threats.
 
 **What’s new:**
+
 - Location Picker: Select a location for the scan via **Security Center → Investigate** in the dashboard or through the API.
 - Region-aware scanning: Understand how content changes by location — useful for detecting regionally tailored attacks.
 - Default behavior: If no location is set, scans default to the user’s current geographic region.
 
-Learn more in the [Security Center documentation](/security-center/).
\ No newline at end of file
+Learn more in the [Security Center documentation](/security-center/).
diff --git a/src/content/changelog/ssl/2025-02-14-cert-bundling-for-custom-hostnames.mdx b/src/content/changelog/ssl/2025-02-14-cert-bundling-for-custom-hostnames.mdx
index 63831623f04e17..d4c8ab56701046 100644
--- a/src/content/changelog/ssl/2025-02-14-cert-bundling-for-custom-hostnames.mdx
+++ b/src/content/changelog/ssl/2025-02-14-cert-bundling-for-custom-hostnames.mdx
@@ -1,9 +1,10 @@
 ---
 title: Upload a certificate bundle with an RSA and ECDSA certificate per custom hostname
 description: Upload a certificate bundle with an RSA and ECDSA certificate per custom hostname
-date: 2025-02-14T11:00:00Z
+date: 2025-02-14
 ---
-import { Card, Render, Details } from "~/components"
+
+import { Card, Render, Details } from "~/components";
 
 Cloudflare has supported both RSA and ECDSA certificates across our platform for a number of years. Both certificates offer the same security, but ECDSA is more performant due to a smaller key size. However, RSA is more widely adopted and ensures compatibility with legacy clients. Instead of choosing between them, you may want both – that way, ECDSA is used when clients support it, but RSA is available if not.
 
@@ -38,10 +39,10 @@ curl -X POST https://api.cloudflare.com/client/v4/zones/$ZONE_ID/custom_hostname
 
 You can also:
 
-* [Upload](/api/resources/custom_hostnames/methods/create/) an RSA or ECDSA certificate to a custom hostname with an existing ECDSA or RSA certificate, respectively.
+- [Upload](/api/resources/custom_hostnames/methods/create/) an RSA or ECDSA certificate to a custom hostname with an existing ECDSA or RSA certificate, respectively.
 
-* [Replace](/api/resources/custom_hostnames/subresources/certificate_pack/subresources/certificates/methods/update/) the RSA or ECDSA certificate with a certificate of its same type.
+- [Replace](/api/resources/custom_hostnames/subresources/certificate_pack/subresources/certificates/methods/update/) the RSA or ECDSA certificate with a certificate of its same type.
 
-* [Delete](/api/resources/custom_hostnames/subresources/certificate_pack/subresources/certificates/methods/delete/) the RSA or ECDSA certificate (if the custom hostname has both an RSA and ECDSA uploaded).
+- [Delete](/api/resources/custom_hostnames/subresources/certificate_pack/subresources/certificates/methods/delete/) the RSA or ECDSA certificate (if the custom hostname has both an RSA and ECDSA uploaded).
 
 This feature is available for Business and Enterprise customers who have purchased custom certificates.
diff --git a/src/content/changelog/ssl/2025-04-09-secrets-store-beta.mdx b/src/content/changelog/ssl/2025-04-09-secrets-store-beta.mdx
index 13b44bfbc044c9..7ae30967dde715 100644
--- a/src/content/changelog/ssl/2025-04-09-secrets-store-beta.mdx
+++ b/src/content/changelog/ssl/2025-04-09-secrets-store-beta.mdx
@@ -1,12 +1,12 @@
 ---
-title:  Cloudflare Secrets Store now available in Beta
+title: Cloudflare Secrets Store now available in Beta
 description: Manage account level Workers secrets via Cloudflare Secrets Store (beta)
-date: 2025-04-09T11:00:00Z
+date: 2025-04-09
 products:
   - secrets-store
 ---
 
-Cloudflare Secrets Store is available today in Beta. You can now store, manage, and deploy account level secrets from a secure, centralized platform to your Workers. 
+Cloudflare Secrets Store is available today in Beta. You can now store, manage, and deploy account level secrets from a secure, centralized platform to your Workers.
 
 ![Import repo or choose template](~/assets/images/ssl/secrets-store-landing-page.png)
 
@@ -18,9 +18,9 @@ wrangler secrets-store store create <name> --remote
 
 The following are supported in the Secrets Store beta:
 
-* Secrets Store UI & API: create your store & create, duplicate, update, scope, and delete a secret
-* Workers UI: bind a new or existing account level secret to a Worker and deploy in code
-* Wrangler: create your store & create, duplicate, update, scope, and delete a secret
-* Account Management UI & API: assign Secrets Store permissions roles & view audit logs for actions taken in Secrets Store core platform
+- Secrets Store UI & API: create your store & create, duplicate, update, scope, and delete a secret
+- Workers UI: bind a new or existing account level secret to a Worker and deploy in code
+- Wrangler: create your store & create, duplicate, update, scope, and delete a secret
+- Account Management UI & API: assign Secrets Store permissions roles & view audit logs for actions taken in Secrets Store core platform
 
-For instructions on how to get started, visit our [developer documentation](/secrets-store/). 
+For instructions on how to get started, visit our [developer documentation](/secrets-store/).
diff --git a/src/content/changelog/ssl/2025-05-19-paygo-updates.mdx b/src/content/changelog/ssl/2025-05-19-paygo-updates.mdx
index 9f721847938e70..7724f04c2933d7 100644
--- a/src/content/changelog/ssl/2025-05-19-paygo-updates.mdx
+++ b/src/content/changelog/ssl/2025-05-19-paygo-updates.mdx
@@ -1,18 +1,18 @@
 ---
 title: Increased limits for Cloudflare for SaaS and Secrets Store free and pay-as-you-go plans
-description: With upgraded limits to [all free and paid plans](https://www.cloudflare.com/plans/), you can now extend the benefits of Cloudflare to more end customers via [Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) and deploy more account level variables through [Cloudflare Secrets Store](https://developers.cloudflare.com/secrets-store/). 
-date: 2025-05-27T11:00:00Z
+description: With upgraded limits to [all free and paid plans](https://www.cloudflare.com/plans/), you can now extend the benefits of Cloudflare to more end customers via [Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) and deploy more account level variables through [Cloudflare Secrets Store](https://developers.cloudflare.com/secrets-store/).
+date: 2025-05-27
 products:
   - ssl
   - cloudflare-for-saas
   - secrets-store
 ---
 
-import { Card, Render, Details } from "~/components"
+import { Card, Render, Details } from "~/components";
 
-With upgraded limits to [all free and paid plans](https://www.cloudflare.com/plans/), you can now scale more easily with [Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) and [Secrets Store](https://developers.cloudflare.com/secrets-store/). 
+With upgraded limits to [all free and paid plans](https://www.cloudflare.com/plans/), you can now scale more easily with [Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) and [Secrets Store](https://developers.cloudflare.com/secrets-store/).
 
-[Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) allows you to extend the benefits of Cloudflare to your customers via their own custom or vanity domains.  Now, the [limit for custom hostnames](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/plans/) on a Cloudflare for SaaS pay-as-you-go plan has been **raised from 5,000 custom hostnames to 50,000 custom hostnames.**
+[Cloudflare for SaaS](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/) allows you to extend the benefits of Cloudflare to your customers via their own custom or vanity domains. Now, the [limit for custom hostnames](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/plans/) on a Cloudflare for SaaS pay-as-you-go plan has been **raised from 5,000 custom hostnames to 50,000 custom hostnames.**
 
 With custom origin server -- previously an enterprise-only feature -- you can route traffic from one or more custom hostnames somewhere other than your default proxy fallback. [Custom origin server](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/) is now available to Cloudflare for SaaS customers on Free, Pro, and Business plans.
 
diff --git a/src/content/changelog/stream/2025-01-30-stream-generated-captions-new-languages.mdx b/src/content/changelog/stream/2025-01-30-stream-generated-captions-new-languages.mdx
index e5f495042079eb..3a75175487dc02 100644
--- a/src/content/changelog/stream/2025-01-30-stream-generated-captions-new-languages.mdx
+++ b/src/content/changelog/stream/2025-01-30-stream-generated-captions-new-languages.mdx
@@ -3,7 +3,7 @@ title: Expanded language support for Stream AI Generated Captions
 description: Captions can now be generated for 11 additional spoken languages at no cost!
 products:
   - stream
-date: 2025-01-30T12:00:00Z
+date: 2025-01-30
 ---
 
 Stream's [generated captions](/stream/edit-videos/adding-captions/#generate-a-caption)
diff --git a/src/content/changelog/stream/2025-02-14-introducing-dvr-for-stream-live.mdx b/src/content/changelog/stream/2025-02-14-introducing-dvr-for-stream-live.mdx
index 521772fdd1b151..8b5b7f848c1737 100644
--- a/src/content/changelog/stream/2025-02-14-introducing-dvr-for-stream-live.mdx
+++ b/src/content/changelog/stream/2025-02-14-introducing-dvr-for-stream-live.mdx
@@ -4,14 +4,14 @@ description: >
   Stream has added support for DVR for Live broadcasts. In other words, for those
   who didn’t witness the magic of TiVo, you can now allow your viewers to rewind
   and replay Live content during broadcasts.
-date: 2025-02-14T12:00:00Z
+date: 2025-02-14
 ---
 
 Previously, all viewers watched "the live edge," or the latest content of the
 broadcast, synchronously. If a viewer paused for more than a few seconds,
 the player would automatically "catch up" when playback started again. Seeking
 through the broadcast was only available once the recording was available after
-  it concluded.
+it concluded.
 
 Starting today, customers can make a small adjustment to the player
 embed or manifest URL to enable the DVR experience for their viewers. By
diff --git a/src/content/changelog/stream/2025-03-06-media-transformations.mdx b/src/content/changelog/stream/2025-03-06-media-transformations.mdx
index 8eb85b5f4a38d5..22392a98fd8f17 100644
--- a/src/content/changelog/stream/2025-03-06-media-transformations.mdx
+++ b/src/content/changelog/stream/2025-03-06-media-transformations.mdx
@@ -3,7 +3,7 @@ title: Introducing Media Transformations from Cloudflare Stream
 description: >
   Dynamically optimize, clip, and resize video from any origin, no storage
   migration needed.
-date: 2025-03-06T12:00:00Z
+date: 2025-03-06
 ---
 
 Today, we are thrilled to announce Media Transformations, a new service that
@@ -25,7 +25,7 @@ an MP4 that can be used in an HTML video element without a player library.
 If your zone already has Image Transformations enabled, then it is ready to
 optimize videos with Media Transformations, too.
 
-``` text title="URL format"
+```text title="URL format"
 https://example.com/cdn-cgi/media/<OPTIONS>/<SOURCE-VIDEO>
 ```
 
@@ -34,10 +34,10 @@ original is nearly 30 megabytes and wider than necessary for this layout.
 Consider a simple width adjustment:
 
 <video controls>
-  <source src="https://developers.cloudflare.com/cdn-cgi/media/width=640/https://pub-d9fcbc1abcd244c1821f38b99017347f.r2.dev/aus-mobile.mp4" />
+	<source src="https://developers.cloudflare.com/cdn-cgi/media/width=640/https://pub-d9fcbc1abcd244c1821f38b99017347f.r2.dev/aus-mobile.mp4" />
 </video>
 
-``` text title="Example URL"
+```text title="Example URL"
 https://example.com/cdn-cgi/media/width=640/<SOURCE-VIDEO>
 https://developers.cloudflare.com/cdn-cgi/media/width=640/https://pub-d9fcbc1abcd244c1821f38b99017347f.r2.dev/aus-mobile.mp4
 ```
diff --git a/src/content/changelog/stream/2025-04-14-webrtc-beta-signed-urls.mdx b/src/content/changelog/stream/2025-04-14-webrtc-beta-signed-urls.mdx
index 4d30e9de7d8f7a..02cd18965776c0 100644
--- a/src/content/changelog/stream/2025-04-14-webrtc-beta-signed-urls.mdx
+++ b/src/content/changelog/stream/2025-04-14-webrtc-beta-signed-urls.mdx
@@ -3,7 +3,7 @@ title: Signed URLs and Infrastructure Improvements on Stream Live WebRTC Beta
 description: >
   Dynamically optimize, clip, and resize video from any origin, no storage
   migration needed.
-date: 2025-04-11T12:00:00Z
+date: 2025-04-11
 ---
 
 Cloudflare [Stream](/stream/) has completed an infrastructure upgrade for our [Live WebRTC beta](/stream/webrtc-beta/) support which brings increased scalability and improved playback performance to all customers. WebRTC allows broadcasting directly from a browser (or supported WHIP client) with ultra-low latency to tens of thousands of concurrent viewers across the globe.
diff --git a/src/content/changelog/stream/2025-05-14-media-transformations-origin-restrictions.mdx b/src/content/changelog/stream/2025-05-14-media-transformations-origin-restrictions.mdx
index 03f539598b7d13..8e87b0fc188be1 100644
--- a/src/content/changelog/stream/2025-05-14-media-transformations-origin-restrictions.mdx
+++ b/src/content/changelog/stream/2025-05-14-media-transformations-origin-restrictions.mdx
@@ -2,7 +2,7 @@
 title: Introducing Origin Restrictions for Media Transformations
 description: >
   Control which sources can be used for original media when requesting transformations.
-date: 2025-05-14T12:00:00Z
+date: 2025-05-14
 ---
 
 We are adding [source origin restrictions](/stream/transform-videos/sources/) to
diff --git a/src/content/changelog/stream/2025-06-10-media-transformations-limits-increase.mdx b/src/content/changelog/stream/2025-06-10-media-transformations-limits-increase.mdx
index 3f94991c1a9bea..9a07eec51e3702 100644
--- a/src/content/changelog/stream/2025-06-10-media-transformations-limits-increase.mdx
+++ b/src/content/changelog/stream/2025-06-10-media-transformations-limits-increase.mdx
@@ -2,7 +2,7 @@
 title: Increased limits for Media Transformations
 description: >
   Media Transformations now supports inputs up to 100MB and output videos as long as 1 minute.
-date: 2025-06-10T12:00:00Z
+date: 2025-06-10
 ---
 
 We have increased the limits for [Media Transformations](/stream/transform-videos/):
diff --git a/src/content/changelog/waf/2025-05-08-improved-payload-logging.mdx b/src/content/changelog/waf/2025-05-08-improved-payload-logging.mdx
index db67709aadba72..bea9d9afc90f33 100644
--- a/src/content/changelog/waf/2025-05-08-improved-payload-logging.mdx
+++ b/src/content/changelog/waf/2025-05-08-improved-payload-logging.mdx
@@ -3,7 +3,7 @@ title: Improved Payload Logging for WAF Managed Rules
 description: We have upgraded WAF Payload Logging to enhance rule diagnostics and usability.
 products:
   - waf
-date: 2025-05-08T11:00:00Z
+date: 2025-05-08
 ---
 
 We have upgraded WAF Payload Logging to enhance rule diagnostics and usability:
diff --git a/src/content/changelog/waf/2025-07-07-increased-ip-list-limits.mdx b/src/content/changelog/waf/2025-07-07-increased-ip-list-limits.mdx
index 2bb56ecb560904..acb4f1f050d99c 100644
--- a/src/content/changelog/waf/2025-07-07-increased-ip-list-limits.mdx
+++ b/src/content/changelog/waf/2025-07-07-increased-ip-list-limits.mdx
@@ -3,7 +3,7 @@ title: Increased IP List Limits for Enterprise Accounts
 description: We have significantly increased the limits for IP Lists on Enterprise plans to provide greater flexibility and control.
 products:
   - waf
-date: 2025-07-07T11:00:00Z
+date: 2025-07-07
 ---
 
 We have significantly increased the limits for [IP Lists](/waf/tools/lists/) on Enterprise plans to provide greater flexibility and control:
@@ -12,4 +12,3 @@ We have significantly increased the limits for [IP Lists](/waf/tools/lists/) on
 - **Total number of list items**: Increased from 10,000 to 500,000.
 
 Limits for other list types and plans remain unchanged. For more details, refer to the [lists availability](/waf/tools/lists/#availability).
-
diff --git a/src/content/changelog/web-analytics/2025-02-25-rum-exclude-eu.mdx b/src/content/changelog/web-analytics/2025-02-25-rum-exclude-eu.mdx
index f4ceee60ddfb7c..9feb5d5e02a562 100644
--- a/src/content/changelog/web-analytics/2025-02-25-rum-exclude-eu.mdx
+++ b/src/content/changelog/web-analytics/2025-02-25-rum-exclude-eu.mdx
@@ -1,9 +1,9 @@
-
 ---
 title: Easily Exclude EU Visitors from RUM
 description: Enable RUM monitoring for your website and respect privacy laws with ease.
-date: 2024-02-26T11:00:00Z
+date: 2024-02-26
 ---
+
 You can now easily enable Real User Monitoring (RUM) monitoring for your hostnames, while safely dropping requests from visitors in the European Union to comply with GDPR and CCPA.
 
 ![RUM Enablement UI](~/assets/images/changelog/web-analytics/2025-02-26-rum-eu.png)
@@ -12,4 +12,4 @@ Our Web Analytics product has always been centered on giving you insights into y
 
 To help with that aim, you can now selectively enable RUM monitoring for your hostname and exclude EU visitor data in a single click. If you opt for this option, we will drop all metrics collected by our EU data centeres automatically.
 
-You can learn more about what metrics are reported by Web Analytics and how it is collected [in the Web Analytics documentation](/web-analytics/data-metrics/). You can enable Web Analytics on any hostname by going to the [Web Analytics](https://dash.cloudflare.com/?to=/:account/web-analytics/sites) section of the dashboard, selecting "Manage Site" for the hostname you want to monitor, and choosing the appropriate enablement option.
\ No newline at end of file
+You can learn more about what metrics are reported by Web Analytics and how it is collected [in the Web Analytics documentation](/web-analytics/data-metrics/). You can enable Web Analytics on any hostname by going to the [Web Analytics](https://dash.cloudflare.com/?to=/:account/web-analytics/sites) section of the dashboard, selecting "Manage Site" for the hostname you want to monitor, and choosing the appropriate enablement option.
diff --git a/src/content/changelog/workers-ai/2025-02-20-updated-pricing-docs.mdx b/src/content/changelog/workers-ai/2025-02-20-updated-pricing-docs.mdx
index 22df837d440f9a..3f91dd95f297bc 100644
--- a/src/content/changelog/workers-ai/2025-02-20-updated-pricing-docs.mdx
+++ b/src/content/changelog/workers-ai/2025-02-20-updated-pricing-docs.mdx
@@ -1,13 +1,13 @@
 ---
 title: Workers AI updated pricing
 description: Granular pricing in units and neurons
-date: 2025-02-20T11:00:00Z
+date: 2025-02-20
 ---
- 
+
 We've updated the Workers AI [pricing](/workers-ai/platform/pricing/) to include the latest models and how model usage maps to Neurons.
 
-* Each model's core input format(s) (tokens, audio seconds, images, etc) now include mappings to Neurons, making it easier to understand how your included Neuron volume is consumed and how you are charged at scale
-* Per-model pricing, instead of the previous bucket approach, allows us to be more flexible on how models are charged based on their size, performance and capabilities. As we optimize each model, we can then pass on savings for that model.
-* You will still only pay for what you consume: Workers AI inference is serverless, and not billed by the hour.
+- Each model's core input format(s) (tokens, audio seconds, images, etc) now include mappings to Neurons, making it easier to understand how your included Neuron volume is consumed and how you are charged at scale
+- Per-model pricing, instead of the previous bucket approach, allows us to be more flexible on how models are charged based on their size, performance and capabilities. As we optimize each model, we can then pass on savings for that model.
+- You will still only pay for what you consume: Workers AI inference is serverless, and not billed by the hour.
 
 Going forward, models will be launched with their associated Neuron costs, and we'll be updating the Workers AI dashboard and API to reflect consumption in both raw units and Neurons. Visit the [Workers AI pricing](/workers-ai/platform/pricing/) page to learn more about Workers AI pricing.
diff --git a/src/content/changelog/workers-ai/2025-02-24-context-windows.mdx b/src/content/changelog/workers-ai/2025-02-24-context-windows.mdx
index e5e775ca81009f..3bccc01ae15a03 100644
--- a/src/content/changelog/workers-ai/2025-02-24-context-windows.mdx
+++ b/src/content/changelog/workers-ai/2025-02-24-context-windows.mdx
@@ -1,11 +1,11 @@
 ---
 title: Workers AI larger context windows
 description: Updated Workers AI models with larger context windows
-date: 2025-02-24T11:00:00Z
+date: 2025-02-24
 ---
 
 We've updated the Workers AI text generation models to include context windows and limits definitions and changed our APIs to estimate and validate the number of tokens in the input prompt, not the number of characters.
 
 This update allows developers to use larger context windows when interacting with Workers AI models, which can lead to better and more accurate results.
 
-Our [catalog page](/workers-ai/models/) provides more information about each model's supported context window.
\ No newline at end of file
+Our [catalog page](/workers-ai/models/) provides more information about each model's supported context window.
diff --git a/src/content/changelog/workers-ai/2025-02-25-json-mode.mdx b/src/content/changelog/workers-ai/2025-02-25-json-mode.mdx
index cfddc344e570a6..49c93864c765da 100644
--- a/src/content/changelog/workers-ai/2025-02-25-json-mode.mdx
+++ b/src/content/changelog/workers-ai/2025-02-25-json-mode.mdx
@@ -1,7 +1,7 @@
 ---
 title: Workers AI now supports structured JSON outputs.
 description: Workers AI JSON Mode adds structured outputs support
-date: 2025-02-25T15:00:00Z
+date: 2025-02-25
 ---
 
 import { TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/workers-ai/2025-03-17-new-workers-ai-models.mdx b/src/content/changelog/workers-ai/2025-03-17-new-workers-ai-models.mdx
index 26524d1da7df31..920a3ab9f8d91d 100644
--- a/src/content/changelog/workers-ai/2025-03-17-new-workers-ai-models.mdx
+++ b/src/content/changelog/workers-ai/2025-03-17-new-workers-ai-models.mdx
@@ -1,12 +1,13 @@
 ---
 title: New models in Workers AI
 description: New text-to-speech, reranker, whisper, embeddings models now available!
-date: 2025-03-17T17:00:00Z
+date: 2025-03-17
 ---
 
 Workers AI is excited to add 4 new models to the catalog, including 2 brand new classes of models with a text-to-speech and reranker model. Introducing:
-- [@cf/baai/bge-m3](/workers-ai/models/bge-m3/) - a multi-lingual embeddings model that supports over 100 languages. It can also simultaneously perform dense retrieval, multi-vector retrieval, and sparse retrieval, with the ability to process inputs of different granularities. 
-- [@cf/baai/bge-reranker-base](/workers-ai/models/bge-reranker-base/) - our first reranker model! Rerankers are a type of text classification model that takes a query and context, and outputs a similarity score between the two. When used in RAG systems, you can use a reranker after the initial vector search to find the most relevant documents to return to a user by reranking the outputs. 
+
+- [@cf/baai/bge-m3](/workers-ai/models/bge-m3/) - a multi-lingual embeddings model that supports over 100 languages. It can also simultaneously perform dense retrieval, multi-vector retrieval, and sparse retrieval, with the ability to process inputs of different granularities.
+- [@cf/baai/bge-reranker-base](/workers-ai/models/bge-reranker-base/) - our first reranker model! Rerankers are a type of text classification model that takes a query and context, and outputs a similarity score between the two. When used in RAG systems, you can use a reranker after the initial vector search to find the most relevant documents to return to a user by reranking the outputs.
 - [@cf/openai/whisper-large-v3-turbo](/workers-ai/models/whisper-large-v3-turbo/) - a faster, more accurate speech-to-text model. This model was added earlier but is graduating out of beta with pricing included today.
 - [@cf/myshell-ai/melotts](/workers-ai/models/melotts/) - our first text-to-speech model that allows users to generate an MP3 with voice audio from inputted text.
 
@@ -14,4 +15,4 @@ Pricing is available for each of these models on the [Workers AI pricing page](/
 
 This docs update includes a few minor bug fixes to the model schema for llama-guard, llama-3.2-1b, which you can review on the [product changelog](/workers-ai/changelog/).
 
-Try it out and let us know what you think! Stay tuned for more models in the coming days.
\ No newline at end of file
+Try it out and let us know what you think! Stay tuned for more models in the coming days.
diff --git a/src/content/changelog/workers-ai/2025-03-20-markdown-conversion.mdx b/src/content/changelog/workers-ai/2025-03-20-markdown-conversion.mdx
index 301b4380497664..06a1dc139891fb 100644
--- a/src/content/changelog/workers-ai/2025-03-20-markdown-conversion.mdx
+++ b/src/content/changelog/workers-ai/2025-03-20-markdown-conversion.mdx
@@ -1,7 +1,7 @@
 ---
 title: Markdown conversion in Workers AI
 description: You can now convert documents in multiple formats to Markdown using the toMarkdown utility method in Workers AI.
-date: 2025-03-20T18:00:00Z
+date: 2025-03-20
 ---
 
 Document conversion plays an important role when designing and developing AI applications and agents. Workers AI now provides the `toMarkdown` utility method that developers can use to for quick, easy, and convenient conversion and summary of documents in multiple formats to Markdown language.
diff --git a/src/content/changelog/workers-ai/2025-04-11-new-models-faster-inference.mdx b/src/content/changelog/workers-ai/2025-04-11-new-models-faster-inference.mdx
index c60fa7ecec3ea1..6c23a881d9eefc 100644
--- a/src/content/changelog/workers-ai/2025-04-11-new-models-faster-inference.mdx
+++ b/src/content/changelog/workers-ai/2025-04-11-new-models-faster-inference.mdx
@@ -1,7 +1,7 @@
 ---
 title: Workers AI for Developer Week - faster inference, new models, async batch API, expanded LoRA support
 description: Workers AI now has more models, faster inference, async batch API, and expanded LoRA
-date: 2025-04-11T18:00:00Z
+date: 2025-04-11
 ---
 
 Happy Developer Week 2025! Workers AI is excited to announce a couple of new features and improvements available today. Check out our [blog](https://blog.cloudflare.com/workers-ai-improvements) for all the announcement details.
diff --git a/src/content/changelog/workers-for-platforms/2025-01-31-workers-platforms-static-assets.mdx b/src/content/changelog/workers-for-platforms/2025-01-31-workers-platforms-static-assets.mdx
index d3cb715673a7af..048f0fb2180d91 100644
--- a/src/content/changelog/workers-for-platforms/2025-01-31-workers-platforms-static-assets.mdx
+++ b/src/content/changelog/workers-for-platforms/2025-01-31-workers-platforms-static-assets.mdx
@@ -3,7 +3,7 @@ title: Workers for Platforms now supports Static Assets
 description: Workers for Platforms customers can now serve static assets for User Workers directly from Cloudflare's global edge
 products:
   - workers-for-platforms
-date: 2025-01-31T17:00:00Z
+date: 2025-01-31
 ---
 
 import { Render, TypeScriptExample } from "~/components";
@@ -23,14 +23,14 @@ This allows your platform to serve entire front-end applications from Cloudflare
 export default {
   async fetch(request, env) {
     const url = new URL(request.url);
-    
+
     // Check real-time inventory
     if (url.pathname === '/api/inventory/check') {
       const product = url.searchParams.get('product');
       const inventory = await env.INVENTORY_KV.get(product);
       return new Response(inventory);
     }
-    
+
     // Serve static assets (HTML, CSS, images)
     return env.ASSETS.fetch(request);
   }
diff --git a/src/content/changelog/workers/2024-11-11-cache-no-store.mdx b/src/content/changelog/workers/2024-11-11-cache-no-store.mdx
index 429956d554278a..2731060ea77a6b 100644
--- a/src/content/changelog/workers/2024-11-11-cache-no-store.mdx
+++ b/src/content/changelog/workers/2024-11-11-cache-no-store.mdx
@@ -1,9 +1,9 @@
 ---
 title: Bypass caching for subrequests made from Cloudflare Workers, with Request.cache
 description: New runtime APIs allow you to control when subrequests are cached, increasing compatibility with popular NPM packages
-products: 
+products:
   - workers
-date: 2024-11-11T14:00:00Z
+date: 2024-11-11
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components"
diff --git a/src/content/changelog/workers/2024-12-29-faster-builds.mdx b/src/content/changelog/workers/2024-12-29-faster-builds.mdx
index b9ce17937839da..f1411d3a6827f3 100644
--- a/src/content/changelog/workers/2024-12-29-faster-builds.mdx
+++ b/src/content/changelog/workers/2024-12-29-faster-builds.mdx
@@ -3,7 +3,7 @@ title: Faster Workers Builds with Build Caching and Watch Paths
 description: Speed up your builds with build caching and build watch paths in Workers Builds (beta).
 products:
   - workers
-date: 2024-12-29T11:00:00Z
+date: 2024-12-29
 ---
 
 ![Build caching settings](~/assets/images/workers/platform/ci-cd/workers-build-caching.png)
diff --git a/src/content/changelog/workers/2025-01-28-nodejs-compat-improvements.mdx b/src/content/changelog/workers/2025-01-28-nodejs-compat-improvements.mdx
index 5a6a8bd862a171..0f365e5392e116 100644
--- a/src/content/changelog/workers/2025-01-28-nodejs-compat-improvements.mdx
+++ b/src/content/changelog/workers/2025-01-28-nodejs-compat-improvements.mdx
@@ -3,7 +3,7 @@ title: Support for Node.js DNS, Net, and Timer APIs in Workers
 description: Node.js APIs from the node:dns, node:net, and node:timers modules are now available when using nodejs_compat.
 products:
   - workers
-date: 2025-01-28T13:00:00Z
+date: 2025-01-28
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/workers/2025-01-31-html-rewriter-streaming.mdx b/src/content/changelog/workers/2025-01-31-html-rewriter-streaming.mdx
index 8e92cfe7723a68..f6efc1178682c5 100644
--- a/src/content/changelog/workers/2025-01-31-html-rewriter-streaming.mdx
+++ b/src/content/changelog/workers/2025-01-31-html-rewriter-streaming.mdx
@@ -3,7 +3,7 @@ title: Transform HTML quickly with streaming content
 description: HTMLRewriter now supports streamed content for more efficient replacement of HTML elements
 products:
   - workers
-date: 2025-01-31T01:00:00Z
+date: 2025-01-31
 ---
 
 import { Render, TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/workers/2025-02-03-workers-metrics-revamp.mdx b/src/content/changelog/workers/2025-02-03-workers-metrics-revamp.mdx
index ca7791066fefdb..d0d4e985feff47 100644
--- a/src/content/changelog/workers/2025-02-03-workers-metrics-revamp.mdx
+++ b/src/content/changelog/workers/2025-02-03-workers-metrics-revamp.mdx
@@ -3,7 +3,7 @@ title: Revamped Workers Metrics
 description: Monitor your Worker's performance with a default set of automatically enabled metrics.
 products:
   - workers
-date: 2025-02-03T18:00:00Z
+date: 2025-02-03
 ---
 
 We've revamped the [Workers Metrics dashboard](https://dash.cloudflare.com/?to=/:account/workers/services/view/:worker/production/metrics/).
diff --git a/src/content/changelog/workers/2025-02-20-builds-name-conflict.mdx b/src/content/changelog/workers/2025-02-20-builds-name-conflict.mdx
index a0d1a4c35884b1..d8d07b4d117cb3 100644
--- a/src/content/changelog/workers/2025-02-20-builds-name-conflict.mdx
+++ b/src/content/changelog/workers/2025-02-20-builds-name-conflict.mdx
@@ -3,7 +3,7 @@ title: Autofix Worker name configuration errors at build time
 description: Workers Builds automatically creates a pull request to update the name field in the wrangler file if it doesn’t match your Worker's name in the Cloudflare dashboard.
 products:
   - workers
-date: 2025-02-20T11:00:00Z
+date: 2025-02-20
 ---
 
 ![Auto-fixing Workers Name in Git Repo](~/assets/images/workers/platform/ci-cd/gh-auto-pr-name.png)
diff --git a/src/content/changelog/workers/2025-02-28-wrangler-v4-rc.mdx b/src/content/changelog/workers/2025-02-28-wrangler-v4-rc.mdx
index baf68eab12a1ff..2858ac2512da90 100644
--- a/src/content/changelog/workers/2025-02-28-wrangler-v4-rc.mdx
+++ b/src/content/changelog/workers/2025-02-28-wrangler-v4-rc.mdx
@@ -3,7 +3,7 @@ title: Use the latest JavaScript features with Wrangler CLI v4.0.0-rc.0
 description: You can now try out the v4 RC for Wrangler by installing `wrangler@4.0.0-rc.0`
 products:
   - workers
-date: 2025-02-28T22:30:00Z
+date: 2025-02-28
 ---
 
 import { PackageManagers } from "~/components";
diff --git a/src/content/changelog/workers/2025-03-11-process-env-support.mdx b/src/content/changelog/workers/2025-03-11-process-env-support.mdx
index 1adf25474e2132..be11d481abe2e8 100644
--- a/src/content/changelog/workers/2025-03-11-process-env-support.mdx
+++ b/src/content/changelog/workers/2025-03-11-process-env-support.mdx
@@ -3,7 +3,7 @@ title: Access your Worker's environment variables from process.env
 description: With Node.js compatibility on, process.env is automatically populated with environment variables and secrets
 products:
   - workers
-date: 2025-03-11T15:00:00Z
+date: 2025-03-11
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/changelog/workers/2025-03-13-wrangler-v4.mdx b/src/content/changelog/workers/2025-03-13-wrangler-v4.mdx
index 7cfebc29a45924..f13da68d43334b 100644
--- a/src/content/changelog/workers/2025-03-13-wrangler-v4.mdx
+++ b/src/content/changelog/workers/2025-03-13-wrangler-v4.mdx
@@ -3,7 +3,7 @@ title: Use the latest JavaScript features with Wrangler CLI v4
 description: Wrangler v4 is available!
 products:
   - workers
-date: 2025-03-13T09:00:00Z
+date: 2025-03-13
 ---
 
 import { PackageManagers } from "~/components";
diff --git a/src/content/changelog/workers/2025-03-14-breakpoint-debugging-with-vitest.mdx b/src/content/changelog/workers/2025-03-14-breakpoint-debugging-with-vitest.mdx
index 6afc6360af74eb..c645db5dbbc698 100644
--- a/src/content/changelog/workers/2025-03-14-breakpoint-debugging-with-vitest.mdx
+++ b/src/content/changelog/workers/2025-03-14-breakpoint-debugging-with-vitest.mdx
@@ -3,7 +3,7 @@ title: Set breakpoints and debug your Workers tests with @cloudflare/vitest-pool
 description: You can now debug your workers tests with the Workers <> Vitest integration
 products:
   - workers
-date: 2025-03-13T14:00:00Z
+date: 2025-03-13
 ---
 
 You can now debug your Workers tests with our [Vitest integration](/workers/testing/vitest-integration/) by running the following command:
diff --git a/src/content/changelog/workers/2025-03-17-importable-env.mdx b/src/content/changelog/workers/2025-03-17-importable-env.mdx
index 7282d14bdc3b70..02991079303845 100644
--- a/src/content/changelog/workers/2025-03-17-importable-env.mdx
+++ b/src/content/changelog/workers/2025-03-17-importable-env.mdx
@@ -3,7 +3,7 @@ title: Import `env` to access bindings in your Worker's global scope
 description: More easily configure your Worker and call bindings from anywhere with an importable `env`
 products:
   - workers
-date: 2025-03-17T15:00:00Z
+date: 2025-03-17
 ---
 
 import { Render, TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/workers/2025-03-17-rerun-build.mdx b/src/content/changelog/workers/2025-03-17-rerun-build.mdx
index 400aeba2eaac7d..cc82d1b7ae35c6 100644
--- a/src/content/changelog/workers/2025-03-17-rerun-build.mdx
+++ b/src/content/changelog/workers/2025-03-17-rerun-build.mdx
@@ -4,7 +4,7 @@ description: Rerun builds for your Workers and Pages projects directly inside of
 products:
   - workers
   - pages
-date: 2025-03-17T11:00:00Z
+date: 2025-03-17
 ---
 
 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!
diff --git a/src/content/changelog/workers/2025-03-22-next-js-vulnerability-waf.mdx b/src/content/changelog/workers/2025-03-22-next-js-vulnerability-waf.mdx
index e49fc3bcc64da8..7a8df340d114a1 100644
--- a/src/content/changelog/workers/2025-03-22-next-js-vulnerability-waf.mdx
+++ b/src/content/changelog/workers/2025-03-22-next-js-vulnerability-waf.mdx
@@ -5,11 +5,11 @@ products:
   - workers
   - pages
   - waf
-date: 2025-03-22T13:00:00Z
+date: 2025-03-22
 ---
 
-import { Image } from 'astro:assets';
-import managedRuleNextJsAuth from "~/assets/images/changelog/workers/high-res-CVE-2025-29927.gif"
+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**.
 
@@ -33,7 +33,12 @@ To enable the rule:
 6. Click **Next**
 7. Scroll down and choose **Save**
 
-<Image src={managedRuleNextJsAuth} alt="Enable the CVE-2025-29927 rule" width="1280" height="1039" />
+<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.
 
@@ -62,9 +67,9 @@ We've made a WAF (Web Application Firewall) rule available to all sites on Cloud
 
 **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.
+- 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.
diff --git a/src/content/changelog/workers/2025-03-22-smart-placement-stablization.mdx b/src/content/changelog/workers/2025-03-22-smart-placement-stablization.mdx
index 8653d647dd990c..086d5e66d29d5b 100644
--- a/src/content/changelog/workers/2025-03-22-smart-placement-stablization.mdx
+++ b/src/content/changelog/workers/2025-03-22-smart-placement-stablization.mdx
@@ -4,7 +4,7 @@ description: Workers and Pages Functions with Smart Placement enabled will not u
 products:
   - workers
   - pages
-date: 2025-03-22T00:00:00Z
+date: 2025-03-22
 ---
 
 [Smart Placement](/workers/configuration/smart-placement/) is a unique Cloudflare feature that can make decisions to move your Worker to run in a more optimal location (such as closer to a database). Instead of always running in the default location (the one closest to where the request is received), Smart Placement uses certain “heuristics” (rules and thresholds) to decide if a different location might be faster or more efficient.
diff --git a/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx b/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx
index 4e332701cc4946..4fbef6c2c8fe17 100644
--- a/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx
+++ b/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx
@@ -3,7 +3,7 @@ title: Source Maps are Generally Available
 description: Source maps are now Generally Available with a larger maximum size limit
 products:
   - workers
-date: 2025-03-25T00:00:00Z
+date: 2025-03-25
 ---
 
 import { WranglerConfig } from "~/components";
@@ -11,9 +11,9 @@ import { WranglerConfig } from "~/components";
 Source maps are now Generally Available (GA). You can now be uploaded with a maximum gzipped size of 15 MB.
 Previously, the maximum size limit was 15 MB uncompressed.
 
-Source maps help map between the original source code and the transformed/minified code that gets deployed 
+Source maps help map between the original source code and the transformed/minified code that gets deployed
 to production. By uploading your source map, you allow Cloudflare to map the stack trace from exceptions
- onto the original source code making it easier to debug. 
+onto the original source code making it easier to debug.
 
 ![Stack Trace without Source Map remapping](src/assets/images/workers-observability/without-source-map.png)
 
@@ -30,8 +30,4 @@ traces are accessible through Tail Workers, Workers Logs, and Workers Logpush.
 To enable source maps, add the following to your
 [Pages Function's](/pages/functions/source-maps/) or [Worker's](/workers/observability/source-maps/) wrangler configuration:
 
-<WranglerConfig>
-```toml
-upload_source_maps = true
-```
-</WranglerConfig>
+<WranglerConfig>```toml upload_source_maps = true ```</WranglerConfig>
diff --git a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
index f810adc33e558a..f651164ee14bfd 100644
--- a/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
+++ b/src/content/changelog/workers/2025-03-25-higher-cpu-limits.mdx
@@ -3,7 +3,7 @@ title: Run Workers for up to 5 minutes of CPU-time
 description: Workers now support up to 5 minutes of CPU time per request. Allowing more CPU-intensive workloads.
 products:
   - workers
-date: 2025-03-26T17:00:00Z
+date: 2025-03-26
 ---
 
 import { Render, TypeScriptExample, WranglerConfig } from "~/components";
@@ -47,4 +47,4 @@ CPU time was limited.
 For more information on the updates limits, see the documentation on [Wrangler configuration for `cpu_ms`](/workers/wrangler/configuration/#limits)
 and on [Workers CPU time limits](/workers/platform/limits/#cpu-time).
 
-For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/). 
\ No newline at end of file
+For building long-running tasks on Cloudflare, we also recommend checking out [Workflows](/workflows/) and [Queues](/queues/).
\ No newline at end of file
diff --git a/src/content/changelog/workers/2025-04-07-increase-trace-events-limit.mdx b/src/content/changelog/workers/2025-04-07-increase-trace-events-limit.mdx
index b1864f049a9690..1099ead4931ae7 100644
--- a/src/content/changelog/workers/2025-04-07-increase-trace-events-limit.mdx
+++ b/src/content/changelog/workers/2025-04-07-increase-trace-events-limit.mdx
@@ -3,17 +3,17 @@ title: Capture up to 256 KB of log events in each Workers Invocation
 description: You can now capture up to 256 KB of log events per Workers Invocation helping you gain better visibility into application behavior.
 products:
   - workers
-date: 2025-04-07T00:00:00Z
+date: 2025-04-07
 ---
 
 You can now capture a maximum of 256 KB of log events per Workers invocation, helping you gain better visibility into application behavior.
 
 All console.log() statements, exceptions, request metadata, and headers are automatically captured during the Worker invocation and emitted
-as [JSON object](/logs/reference/log-fields/account/workers_trace_events). [Workers Logs](/workers/observability/logs/workers-logs) deserializes 
+as [JSON object](/logs/reference/log-fields/account/workers_trace_events). [Workers Logs](/workers/observability/logs/workers-logs) deserializes
 this object before indexing the fields and storing them. You can also capture, transform, and export the JSON object in a
 [Tail Worker](/workers/observability/logs/tail-workers).
 
 256 KB is a 2x increase from the previous 128 KB limit. After you exceed this limit, further context associated with the request will not be
- recorded in your logs.
+recorded in your logs.
 
 This limit is automatically applied to all Workers.
diff --git a/src/content/changelog/workers/2025-04-08-fullstack-on-workers.mdx b/src/content/changelog/workers/2025-04-08-fullstack-on-workers.mdx
index 4ade4d0ba06e51..d2d3d171db6da6 100644
--- a/src/content/changelog/workers/2025-04-08-fullstack-on-workers.mdx
+++ b/src/content/changelog/workers/2025-04-08-fullstack-on-workers.mdx
@@ -4,7 +4,7 @@ description: Cloudflare Workers now provides production ready, generally availab
 products:
   - workers
   - workers-for-platforms
-date: 2025-04-08T18:00:00Z
+date: 2025-04-08
 ---
 
 import { Image } from "astro:assets";
@@ -32,5 +32,4 @@ You can also build complete full-stack apps on Workers **without a framework**:
 
 - You can [“just use Vite"](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and React together, and build a back-end API in the same Worker. Follow our [React SPA with an API tutorial](/workers/vite-plugin/tutorial/) to learn how.
 
-
-**Get started building today with our [framework guides](/workers/framework-guides/)**,  or read our [Developer Week 2025 blog post](https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers) about all the updates to building full-stack applications on Workers.
+**Get started building today with our [framework guides](/workers/framework-guides/)**, or read our [Developer Week 2025 blog post](https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers) about all the updates to building full-stack applications on Workers.
diff --git a/src/content/changelog/workers/2025-04-08-nodejs-crypto-and-tls.mdx b/src/content/changelog/workers/2025-04-08-nodejs-crypto-and-tls.mdx
index 00085cbe210e22..414ca6e88de2cc 100644
--- a/src/content/changelog/workers/2025-04-08-nodejs-crypto-and-tls.mdx
+++ b/src/content/changelog/workers/2025-04-08-nodejs-crypto-and-tls.mdx
@@ -3,7 +3,7 @@ title: Improved support for Node.js Crypto and TLS APIs in Workers
 description: Node.js APIs from the node:crypto and node:tls modules are now available when using nodejs_compat.
 products:
   - workers
-date: 2025-04-08T14:00:00Z
+date: 2025-04-08
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/workers/2025-04-08-vite-plugin.mdx b/src/content/changelog/workers/2025-04-08-vite-plugin.mdx
index b75328902c6364..7d1ea2a98e9fd7 100644
--- a/src/content/changelog/workers/2025-04-08-vite-plugin.mdx
+++ b/src/content/changelog/workers/2025-04-08-vite-plugin.mdx
@@ -3,7 +3,7 @@ title: The Cloudflare Vite plugin is now Generally Available
 description: Cloudflare Vite Plugin 1.0 is out now — with official support for Vite 6, React Router v7, and the full Developer Platform. Now you can run Vite’s dev server locally, while executing your code directly in the Workers runtime!
 products:
   - workers
-date: 2025-04-08T18:00:00Z
+date: 2025-04-08
 ---
 
 The [Cloudflare Vite plugin](/workers/vite-plugin/) has [reached v1.0](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and is now Generally Available ("GA").
diff --git a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
index 70cf17bfb496b5..0b73c111845041 100644
--- a/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
+++ b/src/content/changelog/workers/2025-04-09-qb-workers-logs-ga.mdx
@@ -3,7 +3,7 @@ title: Investigate your Workers with the Query Builder in the new Observability
 description: Workers Observability now offers a Query Builder to help developers construct structured queries to investigate their telemtry data.
 products:
   - workers
-date: 2025-04-09T00:00:00Z
+date: 2025-04-09
 hidden: false
 ---
 
@@ -19,11 +19,11 @@ The **Investigate** tab presents a Query Builder, which helps you write structur
 - Which paths are experiencing the most 5XX errors?
 - What is the wall time distribution by status code for my Worker?
 - What are the slowest requests, and where are they coming from?
-- Who are my top N users? 
+- Who are my top N users?
 
 ![Workers Observability Overview Tab](src/assets/images/changelog/workers/observability/2025-04-09-query-builder.png)
 
-The Query Builder can use any field that you store in your logs as a key to visualize, filter, and group by. Use the Query Builder to quickly access your data, build visualizations, save queries, and share them with your team. 
+The Query Builder can use any field that you store in your logs as a key to visualize, filter, and group by. Use the Query Builder to quickly access your data, build visualizations, save queries, and share them with your team.
 
 ### Workers Logs is now Generally Available
 
diff --git a/src/content/changelog/workers/2025-04-09-workers-timing.mdx b/src/content/changelog/workers/2025-04-09-workers-timing.mdx
index 17c79b041b6f1c..dbdb3fdcd818d3 100644
--- a/src/content/changelog/workers/2025-04-09-workers-timing.mdx
+++ b/src/content/changelog/workers/2025-04-09-workers-timing.mdx
@@ -3,8 +3,7 @@ title: CPU time and Wall time now published for Workers Invocations
 description: Workers Observability tooling now shows CPU time and Wall time for a Workers Invocation.
 products:
   - workers
-date: 2025-04-09T00:00:00Z
-
+date: 2025-04-09
 ---
 
 You can now observe and investigate the CPU time and Wall time for every Workers Invocations.
diff --git a/src/content/changelog/workers/2025-04-15-workers-api-fixes.mdx b/src/content/changelog/workers/2025-04-15-workers-api-fixes.mdx
index 2b38b8f507ba8a..78d10917a1ae61 100644
--- a/src/content/changelog/workers/2025-04-15-workers-api-fixes.mdx
+++ b/src/content/changelog/workers/2025-04-15-workers-api-fixes.mdx
@@ -4,7 +4,7 @@ description: The Workers Routes API now returns a correct response and the Secre
 products:
   - workers
   - workers-for-platforms
-date: 2025-04-15T00:00:00Z
+date: 2025-04-15
 ---
 
 ## Workers Routes API
diff --git a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
index c43ce4b3263098..50cbb354fb8d0d 100644
--- a/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
+++ b/src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
@@ -3,7 +3,7 @@ title: Cron triggers are now supported in Python Workers
 description: You can now set up scheduled handlers in your Python Workers
 products:
   - workers
-date: 2025-04-24T12:00:00Z
+date: 2025-04-24
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/changelog/workers/2025-05-08-finalization-registry.mdx b/src/content/changelog/workers/2025-05-08-finalization-registry.mdx
index 3563a96c542bd3..c2c5fb23082fdf 100644
--- a/src/content/changelog/workers/2025-05-08-finalization-registry.mdx
+++ b/src/content/changelog/workers/2025-05-08-finalization-registry.mdx
@@ -3,11 +3,11 @@ title: Improved memory efficiency for WebAssembly Workers
 description: With the introduction of FinalizationRegistry in Workers Runtime, toolchains like Emscripten and wasm-bindgen can automatically reclaim unused WebAssembly heap and reduce memory leaks.
 products:
   - workers
-date: 2025-05-08T00:00:00Z
+date: 2025-05-08
 ---
 
 [FinalizationRegistry](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/FinalizationRegistry) is now available in Workers. You can opt-in using the [`enable_weak_ref`](/workers/configuration/compatibility-flags/#enable-finalizationregistry-and-weakref) compatibility flag.
 
 This can reduce memory leaks when using WebAssembly-based Workers, which includes [Python Workers](/workers/languages/python/) and [Rust Workers](/workers/languages/rust/). The FinalizationRegistry works by enabling toolchains such as [Emscripten](https://emscripten.org/) and [wasm-bindgen](https://rustwasm.github.io/wasm-bindgen/) to automatically free WebAssembly heap allocations. If you are using WASM and seeing Exceeded Memory errors and cannot determine a cause using [memory profiling](/workers/observability/dev-tools/memory-usage/), you may want to enable the FinalizationRegistry.
 
-For more information refer to the [`enable_weak_ref`](/workers/configuration/compatibility-flags/#enable-finalizationregistry-and-weakref) compatibility flag documentation.
\ No newline at end of file
+For more information refer to the [`enable_weak_ref`](/workers/configuration/compatibility-flags/#enable-finalizationregistry-and-weakref) compatibility flag documentation.
diff --git a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
index 3beb3bac2e54c2..d1131dac63bb86 100644
--- a/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
+++ b/src/content/changelog/workers/2025-05-14-python-worker-durable-object.mdx
@@ -4,14 +4,14 @@ description: You can now create Durable Objects using Python
 products:
   - workers
   - durable-objects
-date: 2025-05-16T12:00:00Z
+date: 2025-05-16
 ---
 
 import { WranglerConfig } from "~/components";
 
 You can now create [Durable Objects](/durable-objects/) using
 [Python Workers](/workers/languages/python/). A Durable Object is a special kind of
-Cloudflare Worker which uniquely combines compute with storage, enabling stateful 
+Cloudflare Worker which uniquely combines compute with storage, enabling stateful
 long-running applications which run close to your users. For more info see
 [here](https://developers.cloudflare.com/durable-objects/what-are-durable-objects/).
 
@@ -26,7 +26,7 @@ class MyDurableObject(DurableObject):
     def __init__(self, ctx, env):
         self.ctx = ctx
         self.env = env
-    
+
     def on_fetch(self, request):
         result = self.ctx.storage.sql.exec("SELECT 'Hello, World!' as greeting").one()
         return Response(result.greeting)
diff --git a/src/content/changelog/workers/2025-05-21-vite-plugin-chrome-devtools.mdx b/src/content/changelog/workers/2025-05-21-vite-plugin-chrome-devtools.mdx
index 1daf583a0e45e2..0a14dfa81b90a2 100644
--- a/src/content/changelog/workers/2025-05-21-vite-plugin-chrome-devtools.mdx
+++ b/src/content/changelog/workers/2025-05-21-vite-plugin-chrome-devtools.mdx
@@ -3,7 +3,7 @@ title: Debug, profile, and view logs for your Worker in Chrome Devtools — now
 description: The Cloudflare Vite plugin now supports debugging Cloudflare Workers using Chrome Devtools
 products:
   - workers
-date: 2025-05-30T13:00:00Z
+date: 2025-05-30
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components";
@@ -32,4 +32,3 @@ For more information on how to get the most out of Chrome Devtools, refer to the
 - [Debug code by setting breakpoints](/workers/observability/dev-tools/breakpoints/)
 - [Profile CPU usage](/workers/observability/dev-tools/cpu-usage/)
 - [Observe memory usage and debug memory leaks](/workers/observability/dev-tools/memory-usage/)
-
diff --git a/src/content/changelog/workers/2025-05-22-handle-request-cancellation.mdx b/src/content/changelog/workers/2025-05-22-handle-request-cancellation.mdx
index 89205f2b639ab6..19a6c8b0cca6ad 100644
--- a/src/content/changelog/workers/2025-05-22-handle-request-cancellation.mdx
+++ b/src/content/changelog/workers/2025-05-22-handle-request-cancellation.mdx
@@ -3,7 +3,7 @@ title: Handle incoming request cancellation in Workers with Request.signal
 description: Workers can now add event listeners on Request.signal and perform tasks when the request is cancelled by the client
 products:
   - workers
-date: 2025-05-22T01:00:00Z
+date: 2025-05-22
 ---
 
 import { Render } from "~/components";
@@ -14,5 +14,4 @@ You can use a listener to perform cleanup tasks or write to logs before your Wor
 
 <Render file="request-signal-example" product="workers" />
 
-
 For more information see the [`Request` documentation](/workers/runtime-apis/request).
diff --git a/src/content/changelog/workers/2025-06-03-visualize-your-worker-architecture.mdx b/src/content/changelog/workers/2025-06-03-visualize-your-worker-architecture.mdx
index 8817ce8bb1bd22..35465c74844f2a 100644
--- a/src/content/changelog/workers/2025-06-03-visualize-your-worker-architecture.mdx
+++ b/src/content/changelog/workers/2025-06-03-visualize-your-worker-architecture.mdx
@@ -3,7 +3,7 @@ title: View an architecture diagram of your Worker directly in the Cloudflare da
 description: Explore and modify your Workers' architecture directly in the Cloudflare dashboard
 products:
   - workers
-date: 2025-06-03T01:00:00Z
+date: 2025-06-03
 ---
 
 import { Render } from "~/components";
@@ -13,9 +13,9 @@ You can now visualize, explore and modify your Worker’s architecture directly
 ![Bindings canvas](src/assets/images/changelog/workers/bindings-canvas.png)
 
 With this new view, you can easily:
-* Explore existing bindings in a visual, architecture-style diagram
-* Add and manage bindings directly from the same interface
-* Discover the full range of compute, storage, AI, and media resources you can attach to your Workers application. 
 
-To get started, head to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages) and open the **Bindings** tab of any Workers application. 
+- Explore existing bindings in a visual, architecture-style diagram
+- Add and manage bindings directly from the same interface
+- Discover the full range of compute, storage, AI, and media resources you can attach to your Workers application.
 
+To get started, head to the [Cloudflare dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages) and open the **Bindings** tab of any Workers application.
diff --git a/src/content/changelog/workers/2025-06-09-workers-integrations-changes.mdx b/src/content/changelog/workers/2025-06-09-workers-integrations-changes.mdx
index 2e62d3c5954bda..88c7d9d0a56441 100644
--- a/src/content/changelog/workers/2025-06-09-workers-integrations-changes.mdx
+++ b/src/content/changelog/workers/2025-06-09-workers-integrations-changes.mdx
@@ -3,29 +3,34 @@ title: Workers native integrations were removed from the Cloudflare dashboard
 description: The Workers native integrations have been removed from the Workers dashboard. Existing integrations continue to work, and new connections should be configured using Wrangler secrets or the dashboard.
 products:
   - workers
-date: 2025-06-09T19:00:00Z
-
+date: 2025-06-09
 ---
- Workers native integrations were [originally launched in May 2023](https://blog.cloudflare.com/announcing-database-integrations/) to connect to popular database and observability providers with your Worker in just a few clicks. We are changing how developers connect Workers to these external services. The **Integrations** tab in the dashboard has been removed in favor of a more direct, command-line-based approach using [Wrangler secrets](/workers/wrangler/commands/#secret). 
+
+Workers native integrations were [originally launched in May 2023](https://blog.cloudflare.com/announcing-database-integrations/) to connect to popular database and observability providers with your Worker in just a few clicks. We are changing how developers connect Workers to these external services. The **Integrations** tab in the dashboard has been removed in favor of a more direct, command-line-based approach using [Wrangler secrets](/workers/wrangler/commands/#secret).
 
 ## What's changed
+
 - **Integrations tab removed**: The integrations setup flow is no longer available in the Workers dashboard.
 - **Manual secret configuration**: New connections should be configured by adding credentials as secrets to your Workers using `npx wrangler secret put` commands.
 
 ## Impact on existing integrations
+
 **Existing integrations will continue to work without any changes required.** If you have integrations that were previously created through the dashboard, they will remain functional.
 
 ## Updating existing integrations
-If you'd like to modify your existing integration, you can update the secrets, environment variables, or [Tail Workers](/workers/observability/logs/tail-workers/) that were created from the original integration setup. 
-- **Update secrets**: Use `npx wrangler secret put <SECRET_NAME>` to update credential values. 
-- **Modify environment variables**: Update variables through the dashboard or Wrangler configuration. 
-- **Dashboard management**: Access your Worker's settings in the [Cloudflare dashboard](https://dash.cloudflare.com) to modify connections created by our removed native integrations feature. 
 
-If you have previously set up an observability integration with [Sentry](https://sentry.io),  the following environment variables were set and are still modifiable: 
-  - `BLOCKED_HEADERS`: headers to exclude sending to Sentry
-  - `EXCEPTION_SAMPLING_RATE`: number from 0 - 100, where 0 = no events go through to Sentry, and 100 = all events go through to Sentry
-  - `STATUS_CODES_TO_SAMPLING_RATES`: a map of status codes -- like 400 or with wildcards like 4xx -- to sampling rates described above
+If you'd like to modify your existing integration, you can update the secrets, environment variables, or [Tail Workers](/workers/observability/logs/tail-workers/) that were created from the original integration setup.
+
+- **Update secrets**: Use `npx wrangler secret put <SECRET_NAME>` to update credential values.
+- **Modify environment variables**: Update variables through the dashboard or Wrangler configuration.
+- **Dashboard management**: Access your Worker's settings in the [Cloudflare dashboard](https://dash.cloudflare.com) to modify connections created by our removed native integrations feature.
+
+If you have previously set up an observability integration with [Sentry](https://sentry.io), the following environment variables were set and are still modifiable:
+
+- `BLOCKED_HEADERS`: headers to exclude sending to Sentry
+- `EXCEPTION_SAMPLING_RATE`: number from 0 - 100, where 0 = no events go through to Sentry, and 100 = all events go through to Sentry
+- `STATUS_CODES_TO_SAMPLING_RATES`: a map of status codes -- like 400 or with wildcards like 4xx -- to sampling rates described above
 
 ## Setting up new database and observability connections
-For new connections, refer to our step-by-step guides on connecting to popular database and observability providers including: [Sentry](/workers/observability/third-party-integrations/sentry), [Turso](/workers/databases/third-party-integrations/turso/), [Neon](/workers/databases/third-party-integrations/neon/), [Supabase](/workers/databases/third-party-integrations/supabase/), [PlanetScale](/workers/databases/third-party-integrations/planetscale/), [Upstash](/workers/databases/third-party-integrations/upstash/), [Xata](/workers/databases/third-party-integrations/xata/). 
 
+For new connections, refer to our step-by-step guides on connecting to popular database and observability providers including: [Sentry](/workers/observability/third-party-integrations/sentry), [Turso](/workers/databases/third-party-integrations/turso/), [Neon](/workers/databases/third-party-integrations/neon/), [Supabase](/workers/databases/third-party-integrations/supabase/), [PlanetScale](/workers/databases/third-party-integrations/planetscale/), [Upstash](/workers/databases/third-party-integrations/upstash/), [Xata](/workers/databases/third-party-integrations/xata/).
diff --git a/src/content/changelog/workers/2025-06-10-default-env-vars.mdx b/src/content/changelog/workers/2025-06-10-default-env-vars.mdx
index e1cb3f0529a9e3..e5b5b2cb972bfc 100644
--- a/src/content/changelog/workers/2025-06-10-default-env-vars.mdx
+++ b/src/content/changelog/workers/2025-06-10-default-env-vars.mdx
@@ -3,7 +3,7 @@ title: Access git commit sha and branch name as environment variables in Workers
 description: Workers Builds now automatically injects environment variables containingGit metadata, including the commit SHA and branch name.
 products:
   - workers
-date: 2025-06-10T01:00:00Z
+date: 2025-06-10
 ---
 
 [Workers Builds](/workers/ci-cd/builds/) connects your Worker to a [Git repository](/workers/ci-cd/builds/git-integration/), and automates building and deploying your code on each pushed change.
diff --git a/src/content/changelog/workers/2025-06-16-workers-platform-admin-role.mdx b/src/content/changelog/workers/2025-06-16-workers-platform-admin-role.mdx
index f4d2f42bfef677..390c8dc86d266c 100644
--- a/src/content/changelog/workers/2025-06-16-workers-platform-admin-role.mdx
+++ b/src/content/changelog/workers/2025-06-16-workers-platform-admin-role.mdx
@@ -1,7 +1,7 @@
 ---
 title: Grant account members read-only access to the Workers Platform
 description: You can now grant members of your Cloudflare account read-only access to the Workers Platform.
-date: 2025-06-16T00:00:00Z
+date: 2025-06-16
 ---
 
 You can now grant members of your Cloudflare account read-only access to the Workers
diff --git a/src/content/changelog/workers/2025-06-17-advanced-routing.mdx b/src/content/changelog/workers/2025-06-17-advanced-routing.mdx
index 441605cd61eb20..6e23ce93fb6942 100644
--- a/src/content/changelog/workers/2025-06-17-advanced-routing.mdx
+++ b/src/content/changelog/workers/2025-06-17-advanced-routing.mdx
@@ -3,7 +3,7 @@ title: Control which routes invoke your Worker script for Single Page Applicatio
 description: New configuration options for specifying which routes invoke your Worker script.
 products:
   - workers
-date: 2025-06-17T01:00:00Z
+date: 2025-06-17
 ---
 
 import { WranglerConfig } from "~/components";
diff --git a/src/content/changelog/workers/2025-06-17-open-next-ssrf.mdx b/src/content/changelog/workers/2025-06-17-open-next-ssrf.mdx
index 6f0de7461fa5ec..5d882216f60383 100644
--- a/src/content/changelog/workers/2025-06-17-open-next-ssrf.mdx
+++ b/src/content/changelog/workers/2025-06-17-open-next-ssrf.mdx
@@ -3,7 +3,7 @@ title: SSRF vulnerability in @opennextjs/cloudflare proactively mitigated for al
 description: Mitigations have been put in place for all existing and future deployments of sites with the Cloudflare adapter for Open Next in response to an identified Server-Side Request Forgery (SSRF) vulnerability in the @opennextjs/cloudflare package
 products:
   - workers
-date: 2025-06-17T01:00:00Z
+date: 2025-06-17
 ---
 
 Mitigations have been put in place for all existing and future deployments of sites with the Cloudflare adapter for Open Next in response to an identified Server-Side Request Forgery (SSRF) vulnerability in the `@opennextjs/cloudflare` package.
diff --git a/src/content/changelog/workers/2025-06-17-workers-terraform-sdk-api-fixes.mdx b/src/content/changelog/workers/2025-06-17-workers-terraform-sdk-api-fixes.mdx
index 1b08787630a56a..1b1851155ede0f 100644
--- a/src/content/changelog/workers/2025-06-17-workers-terraform-sdk-api-fixes.mdx
+++ b/src/content/changelog/workers/2025-06-17-workers-terraform-sdk-api-fixes.mdx
@@ -5,7 +5,7 @@ products:
   - d1
   - workers
   - workers-for-platforms
-date: 2025-06-19T14:00:00Z
+date: 2025-06-19
 ---
 
 import { TypeScriptExample } from "~/components";
diff --git a/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx b/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx
index 1b52f07812ce11..d5191e42eeef08 100644
--- a/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx
+++ b/src/content/changelog/workers/2025-06-18-remote-bindings-beta.mdx
@@ -3,7 +3,7 @@ title: Remote bindings public beta - Connect to remote resources (D1, KV, R2, et
 description: You can now connect to R2 buckets, D1 databases, and other resources running on Cloudflare, while running your Worker's code locally, on your own machine.
 products:
   - workers
-date: 2025-06-18T17:00:00Z
+date: 2025-06-18
 ---
 
 import { WranglerConfig, Aside } from "~/components";
diff --git a/src/content/changelog/workers/2025-06-20-increased-blob-size-limits-in-Workers-Analytics.mdx b/src/content/changelog/workers/2025-06-20-increased-blob-size-limits-in-Workers-Analytics.mdx
index df7d0e6cebd2b5..bcb4ebbedc4cb8 100644
--- a/src/content/changelog/workers/2025-06-20-increased-blob-size-limits-in-Workers-Analytics.mdx
+++ b/src/content/changelog/workers/2025-06-20-increased-blob-size-limits-in-Workers-Analytics.mdx
@@ -3,7 +3,7 @@ title: Increased blob size limits in Workers Analytics Engine
 description: We’ve increased the total allowed size of blob fields per request from 5 KB to 16 KB in the Workers Analytics Engine.
 products:
   - workers
-date: 2025-06-20T11:29:00Z
+date: 2025-06-20
 ---
 import { TypeScriptExample } from "~/components";
 
diff --git a/src/content/changelog/workers/2025-06-25-getPlatformProxy-support-remote-bindings.mdx b/src/content/changelog/workers/2025-06-25-getPlatformProxy-support-remote-bindings.mdx
index 1f923b2c9a3377..8b24ac2d37855a 100644
--- a/src/content/changelog/workers/2025-06-25-getPlatformProxy-support-remote-bindings.mdx
+++ b/src/content/changelog/workers/2025-06-25-getPlatformProxy-support-remote-bindings.mdx
@@ -3,7 +3,7 @@ title: Remote bindings (beta) now works with Next.js — connect to remote resou
 description: You can now use remote bindings with OpenNext applications.
 products:
   - workers
-date: 2025-06-30T17:00:00Z
+date: 2025-06-30
 ---
 
 import { TypeScriptExample, WranglerConfig } from "~/components";
diff --git a/src/content/changelog/workers/2025-06-26-vite-plugin-cross-commands-binding.mdx b/src/content/changelog/workers/2025-06-26-vite-plugin-cross-commands-binding.mdx
index 52320b8e93f840..f63e5a51b616fd 100644
--- a/src/content/changelog/workers/2025-06-26-vite-plugin-cross-commands-binding.mdx
+++ b/src/content/changelog/workers/2025-06-26-vite-plugin-cross-commands-binding.mdx
@@ -3,7 +3,7 @@ title: Run and connect Workers in separate dev commands with the Cloudflare Vite
 description: Workers running in separate dev commands can now communicate with each other using the Cloudflare Vite plugin.
 products:
   - workers
-date: 2025-06-26T15:30:00Z
+date: 2025-06-26
 ---
 
 Workers can now talk to each other across separate dev commands using service bindings and tail consumers, whether started with `vite dev` or `wrangler dev`.
@@ -14,10 +14,10 @@ Simply start each Worker in its own terminal:
 # Terminal 1
 vite dev
 
-# Terminal 2  
+# Terminal 2
 wrangler dev
 ```
 
 This is useful when different teams maintain different Workers, or when each Worker has its own build setup or tooling.
 
-Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
\ No newline at end of file
+Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
diff --git a/src/content/changelog/workers/2025-07-01-vite-plugin-enhanced-assets-support.mdx b/src/content/changelog/workers/2025-07-01-vite-plugin-enhanced-assets-support.mdx
index 35e6e62c2ccfb3..d59d6e0c2abb0e 100644
--- a/src/content/changelog/workers/2025-07-01-vite-plugin-enhanced-assets-support.mdx
+++ b/src/content/changelog/workers/2025-07-01-vite-plugin-enhanced-assets-support.mdx
@@ -3,7 +3,7 @@ title: Enhanced support for static assets with the Cloudflare Vite plugin
 description: The Cloudflare Vite plugin now supports using all of Vite's static assets features in your Worker
 products:
   - workers
-date: 2025-07-01T01:00:00Z
+date: 2025-07-01
 ---
 
 You can now use any of Vite's [static asset handling](https://vite.dev/guide/assets) features in your Worker as well as in your frontend.
diff --git a/src/content/changelog/workers/2025-07-04-javascript-debug-terminals.mdx b/src/content/changelog/workers/2025-07-04-javascript-debug-terminals.mdx
index bb213e96ad96df..69a06e715ccb2b 100644
--- a/src/content/changelog/workers/2025-07-04-javascript-debug-terminals.mdx
+++ b/src/content/changelog/workers/2025-07-04-javascript-debug-terminals.mdx
@@ -3,7 +3,7 @@ title: Workers now supports JavaScript debug terminals in VSCode, Cursor and Win
 description: Wrangler, the Cloudflare Vite plugin, and Miniflare now support breakpoint debugging via JavaScript debug terminals in VSCode
 products:
   - workers
-date: 2025-07-04T01:00:00Z
+date: 2025-07-04
 ---
 
 Workers now support breakpoint debugging using VSCode's built-in [JavaScript Debug Terminals](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_javascript-debug-terminal). All you have to do is open a JS debug terminal (`Cmd + Shift + P` and then type `javascript debug`) and run `wrangler dev` (or `vite dev`) from within the debug terminal. VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.
diff --git a/src/content/changelog/workflows/2024-10-24-workflows-beta.mdx b/src/content/changelog/workflows/2024-10-24-workflows-beta.mdx
index 8f1d1e158c2379..edb36b4a2c0bdd 100644
--- a/src/content/changelog/workflows/2024-10-24-workflows-beta.mdx
+++ b/src/content/changelog/workflows/2024-10-24-workflows-beta.mdx
@@ -1,13 +1,13 @@
 ---
 title: Workflows is now in open beta
 description: Build long-running, reliable and durable applications on Cloudflare Workers
-products: 
+products:
   - workers
   - workflows
-date: 2024-10-24T14:00:00Z
+date: 2024-10-24
 ---
 
-import { Render, PackageManagers } from "~/components"
+import { Render, PackageManagers } from "~/components";
 
 Workflows is now in open beta, and available to any developer a free or paid Workers plan.
 
@@ -23,6 +23,6 @@ npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflo
 
 You can open the `src/index.ts` file, extend it, and use `wrangler deploy` to deploy your first Workflow. From there, you can:
 
-* Learn the [Workflows API](/workflows/build/workers-api/)
-* [Trigger Workflows](/workflows/build/trigger-workflows/) via your Workers apps.
-* Understand the [Rules of Workflows](/workflows/build/rules-of-workflows/) and how to adopt best practices
+- Learn the [Workflows API](/workflows/build/workers-api/)
+- [Trigger Workflows](/workflows/build/trigger-workflows/) via your Workers apps.
+- Understand the [Rules of Workflows](/workflows/build/rules-of-workflows/) and how to adopt best practices
diff --git a/src/content/changelog/workflows/2025-02-25-workflows-concurrency-increased.mdx b/src/content/changelog/workflows/2025-02-25-workflows-concurrency-increased.mdx
index 3c5daf42f1036c..ee7cf68e7bc31e 100644
--- a/src/content/changelog/workflows/2025-02-25-workflows-concurrency-increased.mdx
+++ b/src/content/changelog/workflows/2025-02-25-workflows-concurrency-increased.mdx
@@ -2,11 +2,11 @@
 title: Concurrent Workflow instances limits increased.
 description: Increased concurrency limits for Workflows instances
   - workflows
-date: 2025-02-25T15:00:00Z
+date: 2025-02-25
 ---
 
-import { Render, PackageManagers, TypeScriptExample } from "~/components"
+import { Render, PackageManagers, TypeScriptExample } from "~/components";
 
-[Workflows](/workflows/) now supports up to 4,500 concurrent (running) instances, up from the previous limit of 100. This limit will continue to increase during the Workflows open beta. This increase applies to all users on the Workers Paid plan, and takes effect immediately. 
+[Workflows](/workflows/) now supports up to 4,500 concurrent (running) instances, up from the previous limit of 100. This limit will continue to increase during the Workflows open beta. This increase applies to all users on the Workers Paid plan, and takes effect immediately.
 
 Review the Workflows [limits documentation](/workflows/reference/limits) and/or dive into the [get started guide](/workflows/get-started/guide/) to start building on Workflows.
diff --git a/src/content/changelog/workflows/2025-04-07-workflows-ga.mdx b/src/content/changelog/workflows/2025-04-07-workflows-ga.mdx
index 8e632cf4079531..b08e30f91b4ca9 100644
--- a/src/content/changelog/workflows/2025-04-07-workflows-ga.mdx
+++ b/src/content/changelog/workflows/2025-04-07-workflows-ga.mdx
@@ -4,7 +4,7 @@ description: Workflows is now GA - ship Workflows that you can rely on in produc
 products:
   - workflows
   - workers
-date: 2025-04-07T13:00:00Z
+date: 2025-04-07
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components"
diff --git a/src/content/changelog/zaraz/2025-02-24-zaraz-dash-placement.mdx b/src/content/changelog/zaraz/2025-02-24-zaraz-dash-placement.mdx
index faf78304de78a2..2e4f7308f5fdab 100644
--- a/src/content/changelog/zaraz/2025-02-24-zaraz-dash-placement.mdx
+++ b/src/content/changelog/zaraz/2025-02-24-zaraz-dash-placement.mdx
@@ -1,14 +1,13 @@
 ---
 title: Zaraz moves to the “Tag Management” category in the Cloudflare dashboard
-description: Easier tag management and configuration with Zaraz at the account level 
+description: Easier tag management and configuration with Zaraz at the account level
 products:
-  - zaraz 
-date: 2025-02-24T11:00:00Z
+  - zaraz
+date: 2025-02-24
 ---
 
 ![Zaraz at zone level to Tag management at account level](~/assets/images/zaraz/zaraz-account-level.jpg)
 
 Previously, you could only configure Zaraz by going to each individual zone under your Cloudflare account. Now, if you’d like to get started with Zaraz or manage your existing configuration, you can navigate to the [Tag Management](https://dash.cloudflare.com/?to=/:account/tag-management/zaraz) section on the Cloudflare dashboard – this will make it easier to compare and configure the same settings across multiple zones.
 
-These changes will not alter any existing configuration or entitlements for zones you already have Zaraz enabled on. If you’d like to edit existing configurations, you can go to the [Tag Setup](https://dash.cloudflare.com/?to=/:account/tag-management/zaraz) section of the dashboard, and select the zone you'd like to edit.  
-
+These changes will not alter any existing configuration or entitlements for zones you already have Zaraz enabled on. If you’d like to edit existing configurations, you can go to the [Tag Setup](https://dash.cloudflare.com/?to=/:account/tag-management/zaraz) section of the dashboard, and select the zone you'd like to edit.
diff --git a/src/content/changelog/zero-trust-warp/2024-06-16-cloudflare-one.mdx b/src/content/changelog/zero-trust-warp/2024-06-16-cloudflare-one.mdx
index 023727dc41771b..4750e14cd581c4 100644
--- a/src/content/changelog/zero-trust-warp/2024-06-16-cloudflare-one.mdx
+++ b/src/content/changelog/zero-trust-warp/2024-06-16-cloudflare-one.mdx
@@ -17,7 +17,7 @@ products:
   - magic-wan
   - network-interconnect
   - risk-score
-date: 2024-06-16T11:00:00Z
+date: 2024-06-16
 ---
 
 import { Details } from "~/components";
diff --git a/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-android.mdx b/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-android.mdx
index 14cb95728c055e..20b3d40e08c58c 100644
--- a/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-android.mdx
+++ b/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-android.mdx
@@ -1,7 +1,7 @@
 ---
 title: Cloudflare One Agent for Android (version 2.4)
 description: Cloudflare One Agent for Android (version 2.4)
-date: 2025-03-17T11:00:00Z
+date: 2025-03-17
 ---
 
 A new GA release for the Android Cloudflare One Agent is now available in the [Google Play Store](https://play.google.com/store/apps/details?id=com.cloudflare.cloudflareoneagent). This release includes a new feature allowing [team name insertion by URL](/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment/#enroll-using-a-url) during enrollment, as well as fixes and minor improvements.
diff --git a/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-ios.mdx b/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-ios.mdx
index 72f01fae1bcf55..046b998bb37c7d 100644
--- a/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-ios.mdx
+++ b/src/content/changelog/zero-trust-warp/2025-03-17-warp-ga-ios.mdx
@@ -1,7 +1,7 @@
 ---
 title: Cloudflare One Agent for iOS (version 1.10)
 description: Cloudflare One Agent for iOS (version 1.10)
-date: 2025-03-17T11:00:00Z
+date: 2025-03-17
 ---
 
 A new GA release for the iOS Cloudflare One Agent is now available in the [iOS App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492). This release includes a new feature allowing [team name insertion by URL](/cloudflare-one/connections/connect-devices/warp/deployment/manual-deployment/#enroll-using-a-url) during enrollment, as well as fixes and minor improvements.
diff --git a/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-android.mdx b/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-android.mdx
index 3e07e15a29f17f..d682d4f41a4726 100644
--- a/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-android.mdx
+++ b/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-android.mdx
@@ -1,11 +1,11 @@
 ---
 title: Cloudflare One Agent for Android (version 2.4.2)
 description: Cloudflare One Agent for Android (version 2.4.2)
-date: 2025-06-30T11:00:00Z
+date: 2025-06-30
 ---
 
-A new GA release for the Android Cloudflare One Agent is now available in the [Google Play Store](https://play.google.com/store/apps/details?id=com.cloudflare.cloudflareoneagent). This release 
-contains improvements and new exciting features, including [post-quantum cryptography](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#enable_post_quantum). 
+A new GA release for the Android Cloudflare One Agent is now available in the [Google Play Store](https://play.google.com/store/apps/details?id=com.cloudflare.cloudflareoneagent). This release
+contains improvements and new exciting features, including [post-quantum cryptography](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#enable_post_quantum).
 By tunneling your corporate network traffic over Cloudflare, you can now gain the immediate [protection of post-quantum cryptography](https://blog.cloudflare.com/pq-2024/) without needing to upgrade any of your individual corporate applications or systems.
 
 **Changes and improvements**
@@ -13,4 +13,4 @@ By tunneling your corporate network traffic over Cloudflare, you can now gain th
 - QLogs are now disabled by default and can be enabled in the app by turning on **Enable qlogs** under **Settings** > **Advanced** > **Diagnostics** > **Debug Logs**. The QLog setting from previous releases will no longer be respected.
 - DNS over HTTPS traffic is now included in the WARP tunnel by default.
 - The WARP client now applies [post-quantum cryptography](https://blog.cloudflare.com/pq-2024/) end-to-end on enabled devices accessing resources behind a Cloudflare Tunnel. This feature can be enabled by [MDM](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#enable_post_quantum).
-- Fixed an issue that caused WARP connection failures on ChromeOS devices. 
+- Fixed an issue that caused WARP connection failures on ChromeOS devices.
diff --git a/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-ios.mdx b/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-ios.mdx
index f13dcfb2eb965e..915e015f6774be 100644
--- a/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-ios.mdx
+++ b/src/content/changelog/zero-trust-warp/2025-06-30-warp-ga-ios.mdx
@@ -1,11 +1,11 @@
 ---
 title: Cloudflare One Agent for iOS (version 1.11)
 description: Cloudflare One Agent for iOS (version 1.11)
-date: 2025-06-30T11:00:00Z
+date: 2025-06-30
 ---
 
-A new GA release for the iOS Cloudflare One Agent is now available in the [iOS App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492). This release 
-contains improvements and new exciting features, including [post-quantum cryptography](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#enable_post_quantum). 
+A new GA release for the iOS Cloudflare One Agent is now available in the [iOS App Store](https://apps.apple.com/us/app/cloudflare-one-agent/id6443476492). This release
+contains improvements and new exciting features, including [post-quantum cryptography](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#enable_post_quantum).
 By tunneling your corporate network traffic over Cloudflare, you can now gain the immediate [protection of post-quantum cryptography](https://blog.cloudflare.com/pq-2024/) without needing to upgrade any of your individual corporate applications or systems.
 
 **Changes and improvements**

From 8771f64adf2dbcfec450d95f063035bfb62a4bf4 Mon Sep 17 00:00:00 2001
From: kodster28 <kody@cloudflare.com>
Date: Tue, 15 Jul 2025 13:49:43 -0500
Subject: [PATCH 2/4] update

---
 .../changelog/workers/2025-03-25-gzip-source-maps.mdx      | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx b/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx
index 4fbef6c2c8fe17..0fbf0a1378549a 100644
--- a/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx
+++ b/src/content/changelog/workers/2025-03-25-gzip-source-maps.mdx
@@ -30,4 +30,9 @@ traces are accessible through Tail Workers, Workers Logs, and Workers Logpush.
 To enable source maps, add the following to your
 [Pages Function's](/pages/functions/source-maps/) or [Worker's](/workers/observability/source-maps/) wrangler configuration:
 
-<WranglerConfig>```toml upload_source_maps = true ```</WranglerConfig>
+{/* prettier-ignore */}
+<WranglerConfig>
+```toml
+upload_source_maps = true
+```
+</WranglerConfig>

From 61526b354f8a8135d14bcfe09d8d579dc3cb3e01 Mon Sep 17 00:00:00 2001
From: kodster28 <kody@cloudflare.com>
Date: Tue, 15 Jul 2025 13:53:24 -0500
Subject: [PATCH 3/4] style guide tweak

---
 .../documentation-content-strategy/content-types/changelog.mdx  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/style-guide/documentation-content-strategy/content-types/changelog.mdx b/src/content/docs/style-guide/documentation-content-strategy/content-types/changelog.mdx
index 87425edffa0736..626a7152923620 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/content-types/changelog.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/content-types/changelog.mdx
@@ -70,7 +70,7 @@ Each entry will be its own MDX file, similar to the following.
 ---
 title: Account-level DNS analytics now available via GraphQL Analytics API
 description: Authoritative DNS analytics can now be accessed on the account level via the GraphQL Analytics API.
-date: 2025-06-19T12:00:00Z
+date: 2025-06-19
 ---
 
 Authoritative DNS analytics are now available on the **account level** via the [Cloudflare GraphQL Analytics API](/analytics/graphql-api/).

From b3ff81b64bf47f1cd2b07d261354dd5ffd64f41d Mon Sep 17 00:00:00 2001
From: kodster28 <kody@cloudflare.com>
Date: Tue, 15 Jul 2025 14:14:56 -0500
Subject: [PATCH 4/4] update test

---
 worker/index.worker.test.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/worker/index.worker.test.ts b/worker/index.worker.test.ts
index 7916f337b98922..428f4664a60f40 100644
--- a/worker/index.worker.test.ts
+++ b/worker/index.worker.test.ts
@@ -168,7 +168,7 @@ describe("Cloudflare Docs", () => {
 				expect(item).toBeDefined();
 				expect(item.product).toBe("Access");
 				expect(item.category).toBe("Access");
-				expect(item.pubDate).toBe("Mon, 03 Mar 2025 06:00:00 GMT");
+				expect(item.pubDate).toBe("Mon, 03 Mar 2025 00:00:00 GMT");
 			});
 
 			it("legacy product-specific", async () => {