Core Platform Updates & Release Notes

Follow

188 updates curated from 1 source by the Releasebot Team. Last updated: Nov 18, 2026

Get this feed:
  • Nov 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Workers, Cloudflare CLI - Cloudflare CLI (cf) 1.0 release candidate

    Core Platform releases a Cloudflare CLI 1.0 release candidate with live observability log streaming, smoother project development and deployment, and expanded API command support. The update also stabilizes key configuration and build formats ahead of the full 1.0 release.

    Cloudflare CLI (cf) 1.0.0-rc.1 is a release candidate for cf 1.0. cf has been in beta since late September. This is the release we recommend you try on your own projects, and we want your feedback before 1.0. To install or update to the latest release: npmyarnpnpmbun npm install --global cf@latest yarn global add cf@latest pnpm add --global cf@latest bun add --global cf@latest What is stable We expect the following features to remain stable to cf 1.0: The cloudflare.config.ts configuration format. The Build Output format that cf build writes and cf deploy reads. The commands that create, develop, build, and deploy projects, including cf init, cf dev, cf build, cf deploy, cf previews deploy, and cf workers versions create. The large majority of commands generated from the Cloudflare API and used in the beta. A small number of less commonly used API commands may still change before 1.0. cf generates these commands from the Cloudflare API schema, so their call path may still change before 1.0. Upgrade from a beta This release moves Build Output to version 1, in .cloudflare/output/v1/. cf deploy will automatically create a new build on first run in this location. The release candidate also moves to caret (^) version ranges for its dependencies, requiring: @cloudflare/vite-plugin 2.0.0-rc.0 or later, for projects that build with Vite. Wrangler 4.163.0 or later, for legacy projects that build with Wrangler. 1.0.0-rc.1 renames a few generated API commands without aliases. For example, cf workers secrets bulk is now cf workers secrets bulk-edit. For the full list, refer to the release notes ↗︎. If you last updated early in the beta, these earlier changes may also affect you: Prompts, progress, and status messages are written to stderr. Stdout holds only command output, so scripts that read messages from stdout must read stderr instead. Commands generated from camelCase or snake_case API names use kebab-case. For example, cf accounts billing getCredits is now cf accounts billing get-credits. cf previews deploy takes the Preview name as --preview-name instead of a positional argument. Commands run with --local store state in the project's .cloudflare/state directory. cf no longer saves your account choice between runs. Set accountId in cloudflare.config.ts or CLOUDFLARE_ACCOUNT_ID to skip the prompt. Streaming tail consumers move to experimental.streamingTailConsumers in cloudflare.config.ts. Destructive commands run without a terminal exit with an error unless you pass --force. cf supports the latest versions of the Node.js LTS releases and the latest active release of Node.js. Stream live logs cf observability tail streams live logs and other observability events as newline-delimited JSON. Select a Worker with --worker, a zone and its subdomains with --zone, or every event in the account with --all. Narrow the results with --filters, as inline JSON or from a file: cf observability tail --worker my-worker cf observability tail --worker my-worker --filters @filters.json Worker events require Workers Logs to be turned on for the Worker. For filter shapes and examples, run cf observability tail --help. What changed during the beta Deploy Deploy a directory of static assets with cf deploy ./dist. cf skips the build step and creates an assets-only Worker. cf deploy --no-provision fails when a binding has no resource ID, instead of creating a new resource. cf deploy --force deploys when the Worker was last deployed through the API, or when its remote configuration conflicts with your local Build Output. Redeploying no longer removes secrets that you added outside cloudflare.config.ts. Stack traces from deployed Workers show project paths such as src/index.ts. Python Workers with vendored packages deploy correctly. cf deploy applies SSH settings for Containers managed by Durable Objects. cf deploy --dry-run shows the project setup changes it would make, without making them. Set CLOUDFLARE_DEPENDENCIES_INSTRUMENTATION=false to stop uploading package dependency metadata with each deployment. Develop cf init creates new Worker projects with Vite+, including checks, formatting, and tests that run in the Workers runtime. cf dev and cf build run the Vite or Vite+ executable installed in your project, including dependencies hoisted in a workspace. cf dev passes arguments such as --port and --host to your framework's development server. cf dev --profile <name> passes the selected authentication profile to your development server. cf dev, cf build, and cf deploy offer to run cf migrate when they find a Wrangler configuration file. On Windows, Ctrl+C exits cleanly when your framework runs through npm, Wrangler and Vite start without spawn EFTYPE errors, and cf d1 migrations create rejects names that Windows cannot store. cf init approves the build scripts that pnpm 11 and later block by default, so installation succeeds. Sign in and accounts Pass --temporary-account to create a short-lived account without signing in. cf prints a URL you can use to claim the account. cf auth login summarizes the scopes you granted, and cf auth scopes lists them by product. cf auth whoami, also available as cf whoami, prints a short summary in a terminal and full JSON for scripts and agents. cf auth login now uses the system keyring where available. Long-running commands, such as cf observability tail, refresh an expired OAuth login instead of failing. cf auth whoami reports the status of scoped API tokens correctly. Set CLOUDFLARE_API_HEADERS to send custom headers with API requests. API commands Every command accepts --dry-run to preview what it would do and it redacts sensitive fields in request previews. cf checks --body input before it asks you to sign in or confirm, and rejects array bodies larger than the API allows instead of splitting them across several requests. More request fields are available as flags, including JSON objects and maps, arrays of objects, and file uploads. For example, cf pages deployments create --worker-js @./_worker.js and cf ai to-markdown --files @first.html @second.pdf. Error outputs have been improved with additional messages the API returns, such as the names of missing parameters. cf workers commands accept --worker to select a Worker. --zone finds zones by name in accounts with many zones. cf tunnels quick-start --allowed-mail limits a temporary tunnel to the email addresses and domains you allow. Scripts and agents cf --version prints only the version number. Shell completions and cf tools list every flag a command accepts. cf cli search has reranked cf deploy and other key commands to improve their ranking for static site and Pages deployment searches. cf docs search finds Cloudflare documentation from the terminal. Send feedback To report a bug or tell us what is missing, open an issue in the cf repository ↗︎. For every change in each release, refer to the Cloudflare CLI release notes ↗︎.

    Original source
  • Nov 13, 2026
    • Date parsed from source:
      Nov 13, 2026
    • First seen by Releasebot:
      Nov 14, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Billing, Workers, Durable Objects - Set spending limits for Workers and Durable Objects

    Core Platform adds spending limits and email alerts for Workers and Durable Objects, helping customers manage usage costs while applications continue running or block supported operations when a limit takes effect. Controls are available in the dashboard and CLI.

    You can now set spending limits for Workers and Durable Objects to help control unexpected usage costs, or receive email alerts while your applications keep running. Support for more products is coming soon.

    Use these controls alongside AI Gateway spend limits to manage compute and AI inference costs across your application. AI Gateway supports per-user and per-model budgets for Workers AI and other AI providers, applied to requests routed through your gateway.

    Workers and Durable Objects limits apply across your account for the current subscription billing period. Each product has its own spending controls.

    Set your limits and alerts

    In the Cloudflare dashboard ↗︎, select your account and go to Billing > Spend limits. Choose a spending limit, notification email, and alert thresholds for Workers or Durable Objects.

    For example, configure a $10 Workers spending limit with email alerts at $5 and $9. To receive alerts while your applications keep running, turn off Block usage.

    See when a limit takes effect

    The overview shows each product's recorded spend, alert thresholds, and pause status. Email alerts notify you without stopping usage. When a spending limit takes effect, Cloudflare blocks the product's supported operations.

    To resume usage, raise the limit above current spend, turn it off, or remove it. Usage also resumes when the next billing period starts.

    Usage reporting and blocking take time, so recorded spend can exceed a limit. Read about what counts toward a limit.

    Choose alerts, limits, or both

    For example, set a $50 spending limit for Workers and a $20 email alert for Durable Objects:

    flowchart LR
    A["Durable Objects reaches $20"] --> B["Email alert sent"]
    B --> C["Usage continues"]
    D["Workers reaches $50"] --> E["Spending limit takes effect"]
    E --> F["New Worker invocations blocked"]
    

    Set a spending limit with the cf CLI

    Install the cf CLI and select your account, then run this command to set a $50 spending limit for Workers usage in the current billing period:

    cf billing spend-policies create \
    --name 'Workers $50 spending limit' \
    --product-id workers \
    --enabled true \
    --threshold-cents 5000 \
    --action usage_block
    

    The amount is in US cents: 5000 means $50. To set a spending limit for Durable Objects, use --product-id durable_objects and update the name. Limits count usage already recorded in the current billing period.

    You can also give this prompt to your coding agent. It will ask which product you want to manage and what spending limit to set, then use the CLI to configure it.

    Copy promptPrompt copied!

    Use spending limits alongside budget alerts

    The budget alerts introduced earlier this year notify you about account-wide usage costs without stopping usage. You can keep using them alongside the new product-specific spending limits and email alerts for Workers and Durable Objects.

    To configure account-wide alerts, go to Billing > Billable Usage or follow the budget alerts guide.

    Read the spending limits and alerts guide to learn how spending limits work and manage limits and alerts through the dashboard or cf CLI.

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Cloudflare and hundreds of other software products.

    Create account
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Rules - New hash functions — sha1(), md5(), and sha512()

    Core Platform adds SHA-1, MD5, and SHA-512 hash functions to Cloudflare Rules for computing hashes from strings or byte arrays.

    Cloudflare Rules supports three new hash functions: sha1(), md5(), and sha512(). Use them to compute hashes for systems that require these algorithms.

    Like the existing sha256() function, each accepts a string or byte array and returns raw bytes:

    Function Algorithm Output length md5() MD5 16 bytes sha1() SHA-1 20 bytes sha512() SHA-512 64 bytes

    For example, combine sha512() with encode_base64() to produce a Base64-encoded hash:

    encode_base64(sha512("hello world"))
    

    For details, refer to the sha1(), md5(), and sha512() function references.

    Original source
  • Nov 12, 2026
    • Date parsed from source:
      Nov 12, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Cloudflare Tunnel, Cloudflare Tunnel for SASE - Cloudflare Tunnel extends URL normalization

    Core Platform extends Cloudflare Tunnel URL normalization to semicolon-delimited path parameters before ingress matching, improving security for Access-validated tunnels. Normalization remains off by default for now and is scheduled to turn on in new cloudflared releases starting February 8, 2027.

    Starting from version 2026.11.0, Cloudflare Tunnel extends the URL normalization introduced in 2026.10.0. Normalization now handles semicolon-delimited path parameters before matching ingress rules. This improves security for tunnels with rules that require Cloudflare Access validation. The URL path sent to your origin stays the same.

    Starting 2027-02-08, new cloudflared releases will turn on URL normalization by default. This replaces the previously announced date of 2027-01-25, giving you time to test the updated behavior. Upgrade to version 2026.11.0 or later and test your path-based routing before that date, including rules that match paths containing semicolons. Configurations without rules requiring Access validation are unaffected.

    This setting is currently off by default. To turn it on, run:

    cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>
    

    Alternatively, set TUNNEL_DISABLE_PATH_NORMALIZATION=false on each cloudflared replica and restart it.

    For more information, refer to ingress matching and Access validation at the origin.

    Original source
  • Nov 11, 2026
    • Date parsed from source:
      Nov 11, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Cloudflare CLI, Workers - Send custom API headers with Wrangler and Cloudflare CLI

    Core Platform adds custom API request headers to Wrangler and Cloudflare CLI through an environment variable, with protected headers remaining restricted.

    Wrangler 4.160.0 and Cloudflare CLI (cf) 1.0.0-beta.29 support custom headers for Cloudflare API requests. Use CLOUDFLARE_API_HEADERS to add headers or override most generated values, with the exception of protected body and transport headers.

    For example, to send X-Custom-Header: value, set:

    export CLOUDFLARE_API_HEADERS='{"X-Custom-Header":"value"}'
    

    Then run your Wrangler or cf command.

    For usage and restrictions, refer to the Wrangler environment variable reference and Cloudflare CLI environment variable reference.

    Original source
  • Similar to Core Platform with recent updates:

  • Nov 11, 2026
    • Date parsed from source:
      Nov 11, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Workers, Cloudflare CLI - Serve a Worker's static assets from a URL path like /blog/

    Core Platform adds support for serving Worker static assets from a URL path prefix without changing build output, with configuration options for the Cloudflare CLI and Wrangler.

    You can now serve your Worker's static assets from a URL path prefix, such as example.com/blog/, without changing your build output.

    Previously, to serve assets from /blog/, you had to nest your files in a matching blog directory. Now, set assets.base_path in your Wrangler configuration file, or worker.assets.basePath in cloudflare.config.ts, and keep your files at the root of your asset directory.

    Use Wrangler 4.148.0 ↗︎ or later. With cloudflare.config.ts, use cf 1.0.0-beta.13 ↗︎ or later.

    For example, this configuration serves your built assets from /blog/:

    The following content appears twice: first for the Cloudflare CLI (cf), then for Wrangler. Use cf for new projects. In an existing project, use the CLI that the project already uses.

    Cloudflare CLI

    import { defineConfig } from "cf/config";
    export default defineConfig({
      worker: {
        name: "blog",
        // Set this to today's date
        compatibilityDate: "2026-11-13",
        assets: {
          basePath: "/blog",
        },
      },
    });
    

    Wrangler

    {
      "$schema": "./node_modules/wrangler/config-schema.json",
      "assets": {
        "directory": "./dist",
        "base_path": "/blog"
      }
    }
    
    [assets]
    directory = "./dist"
    base_path = "/blog"
    

    Requests to /blog/ serve dist/index.html, and requests to /blog/posts/post1 serve dist/posts/post1.html. Requests outside /blog/ do not match your static assets and run your Worker, if it has one.

    Paths in _headers, _redirects, and run_worker_first use the full public path, including /blog. If you build with the Cloudflare Vite plugin, also set Vite's base option to /blog/.

    For more information, refer to Serving a subdirectory.

    Original source
  • Nov 9, 2026
    • Date parsed from source:
      Nov 9, 2026
    • First seen by Releasebot:
      Nov 10, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Cloudflare Fundamentals - Markdown for Agents analytics and tracing

    Core Platform releases Markdown for Agents with analytics, sampled conversion logs, a page comparison playground, GraphQL reporting, and tracing to help teams monitor conversion outcomes, token savings, and partial or failed output.

    Markdown for Agents is generally available, with new tools to monitor conversions and investigate partial or failed output.

    Cloudflare dashboard

    In the Cloudflare dashboard, select your zone and go to Agent Readiness > Markdown for Agents:

    • Analytics shows conversion outcomes, estimated token reduction, top converted pages, top user agents, failure reasons, content limits, and pages with partial or failed conversions.
    • Logs provides sampled conversion events with outcome, failure reason, and content-limit filters.
    • Playground requests Markdown for a page on your zone and compares it with HTML. Inspect the Markdown, preview, response headers, and estimated token reduction.

    GraphQL Analytics API

    The GraphQL Analytics API exposes the same analytics through markdownForAgentsAdaptiveGroups at zone and account scope. Query conversion totals, outcomes, estimated token savings, and page diagnostics over the last seven days. Counts are sample-weighted estimates. Token savings use byte-based estimates from full conversions, not tokenizer counts.

    Cloudflare Traces

    Cloudflare Traces includes a markdown_conversion span for sampled streaming conversions. Inspect conversion outcomes, input and output bytes, converter CPU time, and content-limit flags alongside the rest of the request timeline.

    For details and a GraphQL query example, refer to the Markdown for Agents documentation.

    Original source
  • Nov 6, 2026
    • Date parsed from source:
      Nov 6, 2026
    • First seen by Releasebot:
      Nov 6, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Cloudflare Fundamentals - User API tokens have a redesigned creation experience

    Core Platform improves the User API token dashboard with a clearer creation and review flow, easier policy editing, and expiration and IP restrictions in one place, while tokens remain scoped to the creating user.

    User API tokens now use a redesigned dashboard experience that more closely matches Account API tokens, making it easier to create and review user-owned credentials while preserving their user-scoped behavior.

    What's new

    • A more consistent creation flow: User API tokens now follow the same modern dashboard pattern as Account API tokens, including a clearer create and review experience.
    • Improved policy editing: Policies are now easier to read and manage, with inline controls to add, edit, and remove policy blocks before creating the token.
    • Clearer restrictions during setup: Expiration presets and client IP address filtering are built directly into the creation flow so you can review token restrictions in one place.

    These tokens still act on behalf of the creating user, even though the dashboard experience is now more consistent with Account API tokens. For more information, refer to Create API token, Create tokens via API, and Account API tokens.

    Original source
  • Nov 4, 2026
    • Date parsed from source:
      Nov 4, 2026
    • First seen by Releasebot:
      Nov 5, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Load Balancing, Cloudflare Tunnel, Cloudflare Mesh - Steer Cloudflare One users and private networks to the same endpoint with session affinity and hash steering in private load balancers

    Core Platform adds session affinity for private load balancers, keeping users on the same healthy endpoint for stateful applications. Hash steering and IP-based affinity work with traffic through Cloudflare Tunnel, Mesh, and WAN.

    Private load balancers can now keep each user on the same endpoint. This helps with applications that keep session state on a single server.

    How it works

    • Cloudflare One Client or Cloudflare WAN site
    • Connects to 100.112.0.0
    • Private load balancer
    • Picks a healthy endpoint based on your steering policy
    • Health monitors
    • Steering
    • Session affinity
    • Pool 1
      • Cloudflare Tunnel
      • 10.0.0.1
      • vnet-a
    • Pool 2
      • Cloudflare Mesh node
      • 10.1.0.1
      • default
    • Pool 3
      • Cloudflare WAN
      • 10.2.0.1
      • default

    Endpoint = IP address + virtual network

    Two options are available

    • Hash endpoint steering. In the dashboard, set a pool's Endpoint steering to Hash. Each user is mapped to an endpoint within the pool.
    • Session affinity. With the API, set session_affinity to ip_cookie on the load balancer. Each user stays on the same endpoint while it remains healthy and your pools do not change. Refer to Session affinity.

    For traffic from the Cloudflare One Client, Cloudflare identifies the user by their device, so a user stays on the same endpoint even if their IP address changes. For other traffic, such as from a Cloudflare WAN site, Cloudflare uses the source IP address.

    This works for endpoints reached through Cloudflare Tunnel, Cloudflare Mesh, and Cloudflare WAN. Affinity pins the endpoint, not the cloudflared or Mesh replica that carries the traffic.

    To learn how private load balancing fits with your connectors, refer to Load balance private network traffic.

    Original source
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 3, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Audit Logs - Audit Logs v2: Account analytics

    Core Platform adds account-level audit log analytics to the Cloudflare dashboard, with action trends, summary metrics, and filters to investigate actors, products, authentication methods, and failures.

    Audit Logs v2 now includes analytics for account-level audit logs in the Cloudflare dashboard. The Actions over time chart separates successful and failed actions for the selected time range.

    Summary cards show Total actions, Unique actors, Products impacted, and Failure rate. Select a card to investigate action types, authentication methods, top actors, top products, or failed actions. You can apply or exclude values as filters to update both the analytics and audit log table.

    Account analytics are not available for organization-level audit logs.

    For more information, refer to the account analytics documentation.

    Original source
  • Oct 28, 2026
    • Date parsed from source:
      Oct 28, 2026
    • First seen by Releasebot:
      Oct 29, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Workers, Cloudflare CLI - Serve Workers Static Assets from a URL path prefix

    Core Platform adds support for serving Workers Static Assets under a URL path prefix without restructuring asset directories, configured through Wrangler or cloudflare.config.ts.

    Workers Static Assets can now serve assets from a URL path prefix without changing their directory structure. Set assets.base_path in Wrangler, or worker.assets.basePath in cloudflare.config.ts.

    Use Wrangler 4.148.0 ↗︎ or later. With cloudflare.config.ts, use cf 1.0.0-beta.13 ↗︎ or later.

    For example, this configuration serves your built assets from /blog/:

    Select your preferred CLI

    Wrangler

    {
      "$schema": "./node_modules/wrangler/config-schema.json",
      "assets": {
        "directory": "./dist",
        "base_path": "/blog"
      }
    }
    

    CF

    [assets]
    directory = "./dist"
    base_path = "/blog"
    

    cloudflare.config.ts

    import { defineConfig } from "cf/config";
    
    export default defineConfig({
      worker: {
        name: "blog",
        // Set this to today's date
        compatibilityDate: "2026-10-28",
        assets: {
          basePath: "/blog",
        },
      },
    });
    

    Changes examples on this page to use the selected CLI.

    With Wrangler, assets.directory selects the directory to serve. With cloudflare.config.ts, your build configuration supplies the assets.

    To configure the option, refer to Serving a subdirectory.

    Original source
  • Oct 27, 2026
    • Date parsed from source:
      Oct 27, 2026
    • First seen by Releasebot:
      Oct 28, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Analytics - SQL API introspection: `include_attributes` parameter

    Core Platform adds an SQL API introspection parameter that discovers dataset attribute keys and types from the past seven days, while keeping the previous parameter and response field available as deprecated options.

    The SQL API introspection endpoint has a new include_attributes query parameter. Setting it to true discovers the keys of a dataset's attributes JSON column, and their types, from the preceding seven days of your account's data. Discovered keys are returned in the dataset's attributes response field.

    Some datasets store additional key-value data in an attributes JSON column, which you query with exact-key lookups such as attributes['http.method']. The previous way to discover these keys, include_custom_attributes, returned names in a custom_attributes field. The new names make it clearer that each returned name is a key you access through the attributes column.

    include_custom_attributes and custom_attributes are deprecated but still work. Update integrations to use include_attributes and attributes.

    curl --get "https://api.cloudflare.com/client/v4/analytics/sql/introspection" \
    --header "Authorization: Bearer <API_TOKEN>" \
    --data-urlencode "account_tag=<ACCOUNT_TAG>" \
    --data-urlencode "dataset_name=events.httpRequests" \
    --data-urlencode "include_attributes=true"
    

    For more information, refer to Attributes.

    Original source
  • Oct 22, 2026
    • Date parsed from source:
      Oct 22, 2026
    • First seen by Releasebot:
      Oct 23, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Cloudflare Tunnel, Cloudflare Tunnel for SASE - Cloudflare Tunnel supports URL normalization

    Core Platform’s Cloudflare Tunnel now supports URL normalization before ingress-rule matching, improving security for tunnels using Access validation. The setting is opt-in today and is scheduled to become the default in new cloudflared releases starting January 25, 2027.

    Starting from version 2026.10.0, Cloudflare Tunnel can normalize URLs before matching ingress rules. This improves security for tunnels with rules that require Cloudflare Access validation. The URL path sent to your origin stays the same.

    In three months, starting 2027-01-25, new cloudflared releases will turn on URL normalization by default. Test your path-based routing before that date, as this change may affect which ingress rule matches a request. Configurations without rules requiring Access validation are unaffected.

    This setting is currently off by default. To turn it on, run:

    cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>
    

    Alternatively, set TUNNEL_DISABLE_PATH_NORMALIZATION=false on each cloudflared replica and restart it.

    For more information, refer to ingress matching and Access validation at the origin.

    Original source
  • Oct 22, 2026
    • Date parsed from source:
      Oct 22, 2026
    • First seen by Releasebot:
      Oct 23, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    Cloudflare Fundamentals, Cloudflare One, Cloudflare Tunnel for SASE, Cloudflare Tunnel - Granular Tunnel Read And Monitor role is generally available

    Core Platform adds general availability for Cloudflare Tunnel’s granular cloudflared Read And Monitor role, giving members access to selected Tunnels and remote log streaming for troubleshooting without write permissions or account-wide access.

    The Cloudflare Tunnel - Granular Connector cloudflared Read And Monitor role is now generally available. You can grant a member read access and log streaming for specific Cloudflare Tunnel instances without granting write access or access to every Tunnel in your account.

    This role includes the same access as Cloudflare Tunnel - Granular Connector cloudflared Read: viewing selected Tunnels, their IP and hostname routes, and connector host details. It also grants remote log streaming, so support operators can troubleshoot a Tunnel without changing its configuration. The existing Read role does not grant log streaming access.

    To assign the role, follow Grant a granular permission. For the available roles, refer to the resource-scoped roles reference.

    Original source
  • Oct 21, 2026
    • Date parsed from source:
      Oct 21, 2026
    • First seen by Releasebot:
      Oct 28, 2026
    Cloudflare logo

    Core Platform by Cloudflare

    logpush, Logs - Account-scoped HTTP request logs in Logpush

    Core Platform's Cloudflare Logpush adds account-scoped HTTP request logs, letting one job collect logs across every zone.

    Cloudflare Logpush now supports HTTP request logs as an account-scoped dataset. Use one job to deliver logs for every zone in an account instead of maintaining a separate job for each zone.

    Create the job at the account level in the Cloudflare dashboard or through the Logpush API. The ZoneName field identifies the source zone in each log entry.

    Custom fields remain configured per zone. An account-scoped job honors the custom fields configuration for each zone but does not support account-wide custom fields configuration.

    For setup details, refer to API configuration.

    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.