Releasesby GlyphWorkers - Workers will use the new module registry by default on November 17
Starting November 17, 2026, JavaScript Workers with a compatibility date of 2026-11-17 or later will use the new module registry by default. You will no longer need the new_module_registry flag for these dates. Python Workers keep using the legacy registry. The module registry finds and loads JavaScript modules in your Worker.
Also shipped Nov 2, 2026Cloudflare in November 2026 →
Managed warehouse for MLflow (Beta)
Managed warehouse for MLflow is available in Beta, enabling users to view Unity Catalog traces in the MLflow UI without manually choosing a SQL warehouse.
Check out GitHub code without long-lived credentials on self-hosted agents
Self-hosted agents can now use temporary, read-only GitHub App tokens for repository checkout. This eliminates the need to distribute and rotate long-lived SSH keys or personal access tokens across your agent fleet.
Serving tuned Gemini 3.x models on global endpoints
Serving tuned Gemini 3.x models on global endpoints is available in General Availability (GA) . You can copy fine-tuned Gemini 3.x models to the global region using the Model Registry models:copy API, deploy them to global serving endpoints, and send inference requests directly to aiplatform.googleapis.com .
[Launched] Generally Available: Change from virtual network integration to a private endpoint capable network configuration in Azure Database for PostgreSQL flexible server
You now have greater flexibility in network design for Azure Database for PostgreSQL Flexible Server workloads. Now you can change existing VNet-integrated servers from delegated-subnet networking to a private endpoint-capable configuration, enabling secu
[Launched] Generally Available: Restart databases in Azure SQL DB via the Azure portal
You can now restart or fail over databases directly from the Azure portal, including single databases, Hyperscale databases, and databases in elastic pools, without writing scripts against the Rest API or contacting support. Learn more.
Lakehouse caching for cross-cloud data access is generally available (GA)
Lakehouse caching for cross-cloud data access is generally available (GA). Cross-cloud caching is disabled by default. You can opt in to caching on a Lakehouse federated catalog or a BigQuery cross-cloud connection to cache remote files in your Google Cloud region. This helps reduce cross-cloud egress costs and accelerate subsequent queries.
More from Cloudflare developer platformEvery Cloudflare developer platform release →
AI Search billing postponed to December 1, 2026, and default sync interval is now 24 hours
Billing postponed to December 1, 2026 AI Search billing has been postponed by one month and now begins on December 1, 2026, instead of November 1, 2026. You will not be charged for AI Search usage before December 1, 2026. Pricing and included usage are unchanged. For rates and included usage, refer to Limits & pricing .
Cloudflare One, Access - Organize and authorize Access service tokens with tags
You can now assign key-value tags to Access service tokens and use those tags to organize credentials or control application access. Each token supports up to five tags, such as environment: production or team: payments . Add or edit tags when you create or update a token in the dashboard or service token API.
Flagship - Evaluate Flagship flags locally
Flagship bindings now evaluate flags against a local flag store during local development, instead of calling your remote app. You can develop offline and test flag changes without affecting production. This applies to wrangler dev , the Cloudflare Vite plugin , the Vitest integration , and cf dev .
Workers - Request.signal will be enabled by default in Workers on November 17
Starting November 17, 2026, Workers with a compatibility date of 2026-11-17 or later will receive client disconnection events through request.signal by default. Use these events to stop unnecessary work when a client leaves. You will no longer need the enable_request_signal compatibility flag for these dates. We introduced this feature in May 2025 .
Bots - Granular access controls for the top Personal Agents
The Configure AI bot policies setting is now named AI Crawler and Agent access policies . Personal agents act on a person's behalf, fetching information or browsing in response to a request. The updated policies let you set actions for the top Personal Agents individually.
Cloudflare One, Access - Inspect provisioned users and groups with the SCIM population viewer
The new SCIM population viewer allows administrators to inspect users and groups provisioned to Cloudflare One directly from the dashboard.
Audit Logs v2: Account analytics
Audit Logs v2 now includes account-level analytics, providing charts and summary cards for action success rates and top actors.
Browser Run now runs Chrome 152
Browser Run now uses Chrome 152 by default, improving site compatibility and web platform feature support.