Cloudflare Release Notes

Follow

2557 release notes curated from 14 sources by the Releasebot Team. Last updated: Nov 18, 2026

Get this feed:

Cloudflare Products (14)

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

    Developer Platform by Cloudflare

    Hyperdrive, Workers VPC - Custom CA and client certificates (mTLS) for Workers VPC

    Developer Platform now supports custom certificate authorities and mutual TLS for VPC Services, enabling verified connections to private services and origins that require client certificates. Configure certificates with Wrangler, the API, or Terraform for HTTPS and TCP services, including PostgreSQL databases.

    VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with verify_ca or disabled, and origins that required client certificates were unreachable. Upload your CA certificate and client certificate, then reference them from the TLS settings of a VPC Service: npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client npx wrangler vpc service create private-db \ --type tcp \ --tcp-port 5432 \ --app-protocol postgresql \ --hostname db.internal.example \ --tunnel-id <TUNNEL_ID> \ --certificate-authority <CA_CERTIFICATE_ID> \ --client-certificate <CLIENT_CERTIFICATE_ID> \ --cert-verification-mode verify_full You can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle. You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later. For details, refer to Custom CA and client certificates.

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

    Storage by Cloudflare

    Custom CA and client certificates (mTLS) for Workers VPC

    Storage VPC Services now supports custom certificate authorities and mutual TLS for private services, enabling verified HTTPS and TLS connections with custom CA or client certificates. Configuration is available through Wrangler, the API, and Terraform.

    VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with verify_ca or disabled, and origins that required client certificates were unreachable.

    Upload your CA certificate and client certificate, then reference them from the TLS settings of a VPC Service:

    npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca
    npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client
    npx wrangler vpc service create private-db \
    --type tcp \
    --tcp-port 5432 \
    --app-protocol postgresql \
    --hostname db.internal.example \
    --tunnel-id <TUNNEL_ID> \
    --certificate-authority <CA_CERTIFICATE_ID> \
    --client-certificate <CLIENT_CERTIFICATE_ID> \
    --cert-verification-mode verify_full
    

    You can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle.

    You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later.

    For details, refer to Custom CA and client certificates.

    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 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    Cloudflare logo

    Developer Platform by Cloudflare

    AI Search - AI Search can generate file summaries during indexing

    Developer Platform adds optional AI Search file summaries during indexing, generating summaries, topics, and keywords to enrich context metadata and improve retrieval. The feature is off by default and incurs Workers AI usage charges.

    AI Search can now summarize your files while it indexes them. For each text document that produces at least three chunks, AI Search uses a large language model (LLM) to generate a summary, topics, and keywords: The summary and keywords are stored in the item's context metadata. A context value you already set is kept. The topics are added to the context header of the file's chunks to help retrieval. Turn on file summaries in the dashboard, or set indexing_options.file_summary to true when you create or update an instance. File summaries are off by default, and changing the setting triggers a full reindex. indexing_options is replaced as a whole on every update. Include the current value of every option, or the options you leave out return to their defaults. The LLM costs are billed to your account. File summaries are not part of the AI Search ingestion allotment. AI Search uses a Workers AI model suited to summarization and calls it through your instance's AI Gateway, or the default gateway if none is set, and the calls are billed as Workers AI usage. Each new or modified file is summarized once, so costs grow with the amount of content you index. For more information, refer to File summaries.

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

    Developer Platform by Cloudflare

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

    Developer Platform releases a candidate for Cloudflare CLI 1.0, bringing live observability logs, improved deployment and development workflows, and clearer scripting support. The update also establishes stable configuration and build output formats while detailing migration changes for beta users.

    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 &lt;name&gt; 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 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    Cloudflare logo

    Developer Platform by Cloudflare

    Cloudflare Images - Optimize original TIFF files with Images

    Developer Platform’s Cloudflare Images now accepts TIFF originals, converting them on demand to web-friendly formats such as WebP and AVIF. Users can also resize outputs while preserving originals, helping deliver image assets more efficiently.

    Cloudflare Images lets you optimize images for web delivery while storing only the original, high-resolution version. With Images, you can dynamically serve compressed and resized versions in the most efficient format for the requesting browser. Starting today, Images accepts TIFF as an input format. In publishing and e-commerce, TIFF is widely deployed as a master format for product photography, high-resolution scans, print assets, and archival collections. TIFF is a mature format, but it has limited support in modern browsers and tends to produce larger files than formats optimized for web delivery. You can dynamically transcode original TIFF files to formats such as WebP or AVIF. These formats offer more efficient compression, which can reduce file sizes and improve page load performance. You can also resize each output without converting or modifying your original image. For multi-page TIFF files, Images decodes only the first page. For supported formats and limits, refer to Limits and formats.

    Original source
  • Similar to Cloudflare with recent updates:

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

    Cloudflare One by Cloudflare

    Cloudflare One Appliance, Cloudflare One, Cloudflare WAN - Configure a separate WAN gateway for each appliance in a high availability site

    Cloudflare One now supports separate default gateways for each appliance in a high-availability site with a static WAN, letting appliances connect through distinct Internet circuits. Configure the secondary gateway in the dashboard or API, or leave it blank to retain the existing shared-gateway behavior.

    You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway. In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address. In the API, set static_addressing.secondary_gateway_address when you create or update a WAN. To remove the value with a PATCH request, set it to null. The field is optional. If you leave it blank, the secondary appliance uses the primary gateway address, which matches how HA sites worked before. You can only use this field on sites in HA mode. curl --request PATCH \ https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id} \ --header "Authorization: Bearer &lt;API_TOKEN&gt;" \ --header "Content-Type: application/json" \ --data '{ "static_addressing": { "address": "203.0.113.2/30", "gateway_address": "203.0.113.1", "secondary_address": "198.51.100.2/30", "secondary_gateway_address": "198.51.100.1" } }' For details, refer to About high availability configurations.

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

    Cloudflare One by Cloudflare

    Risk Score - Investigate user risk events in a timeline

    Cloudflare One adds a customizable risk-event timeline to User Risk Scoring, helping Enterprise teams trace triggers and later detections.

    User Risk Scoring now groups risk behavior instances in a timeline. Each group highlights its trigger and shows later detections in time order. Customize the date range to focus on the events you want to investigate. Select a timeline marker to view its events. The sequence helps security teams follow how risk events relate during investigations. Switch to Table to return to the existing table view whenever you prefer. User Risk Scoring is available on Enterprise plans. For more information, refer to User risk score.

    Original source
  • 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 &lt;name&gt; 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 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 18, 2026
    • Modified by Releasebot:
      Nov 18, 2026
    Cloudflare logo

    Media by Cloudflare

    Optimize original TIFF files with Images

    Media (Cloudflare Images) now accepts TIFF uploads, letting users dynamically resize and transcode original images to web-ready formats such as WebP and AVIF for more efficient delivery.

    Cloudflare Images lets you optimize images for web delivery while storing only the original, high-resolution version. With Images, you can dynamically serve compressed and resized versions in the most efficient format for the requesting browser.

    Starting today, Images accepts TIFF as an input format.

    In publishing and e-commerce, TIFF is widely deployed as a master format for product photography, high-resolution scans, print assets, and archival collections. TIFF is a mature format, but it has limited support in modern browsers and tends to produce larger files than formats optimized for web delivery.

    You can dynamically transcode original TIFF files to formats such as WebP or AVIF. These formats offer more efficient compression, which can reduce file sizes and improve page load performance. You can also resize each output without converting or modifying your original image.

    For multi-page TIFF files, Images decodes only the first page. For supported formats and limits, refer to Limits and formats.

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

    Cloudflare AI by Cloudflare

    AI Search can generate file summaries during indexing

    Cloudflare AI Search now summarizes text files during indexing, adding summaries, topics, and keywords to help improve retrieval. File summaries are optional, off by default, and billed as Workers AI usage.

    AI Search can now summarize your files while it indexes them. For each text document that produces at least three chunks, AI Search uses a large language model (LLM) to generate a summary, topics, and keywords:

    • The summary and keywords are stored in the item's context metadata. A context value you already set is kept.
    • The topics are added to the context header of the file's chunks to help retrieval.

    Turn on file summaries in the dashboard, or set indexing_options.file_summary to true when you create or update an instance. File summaries are off by default, and changing the setting triggers a full reindex.

    indexing_options is replaced as a whole on every update. Include the current value of every option, or the options you leave out return to their defaults.

    The LLM costs are billed to your account. File summaries are not part of the AI Search ingestion allotment. AI Search uses a Workers AI model suited to summarization and calls it through your instance's AI Gateway, or the default gateway if none is set, and the calls are billed as Workers AI usage. Each new or modified file is summarized once, so costs grow with the amount of content you index.

    For more information, refer to File summaries.

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

    Workers SDK by Cloudflare

    Workers SDK updates its default compatibility date to match bundled workerd and aligns local email handling with production by exposing the canBeForwarded property. Dependencies are also refreshed.

    Patch Changes

    • #16974 77b5ca7 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-17

      Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

    • #16974 77b5ca7 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

      The following dependency versions have been updated:

      Dependency From To @cloudflare/workers-types ^5.20261116.1 ^5.20261117.1 workerd 1.20261116.1 1.20261117.1
    • #16811 51064e6 Thanks @mindulle! - Expose canBeForwarded boolean property on ForwardableEmailMessage in email handler

      Previously, in wrangler dev, the ForwardableEmailMessage passed to a Worker's email() handler did not expose the documented canBeForwarded property, causing it to read as undefined locally while production exposes it as a read-only boolean. canBeForwarded: true is now set on the incoming message object in Miniflare, matching production behavior.

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

    Workers SDK by Cloudflare

    Workers SDK updates its default compatibility date to match bundled workerd when scaffolding projects or when no date is configured.

    Patch Changes

    #16974 77b5ca7 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-17
    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

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

    Workers SDK by Cloudflare

    @cloudflare/[email protected]

    Workers SDK updates its default compatibility date to match bundled workerd when scaffolding projects or when none is configured.

    Patch Changes

    #16974 77b5ca7 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-17 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

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

    Workers SDK by Cloudflare

    @cloudflare/[email protected]

    Workers SDK updates the default compatibility date to match bundled workerd when scaffolding projects or when none is configured.

    Patch Changes

    • #16974 77b5ca7 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-17

      Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

      Updated dependencies [77b5ca7]:

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

    Workers SDK by Cloudflare

    @cloudflare/[email protected]

    Workers SDK updates the default compatibility date to match bundled workerd when scaffolding projects or when none is configured.

    Patch Changes

    • #16974 77b5ca7 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-17

      Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

    • Updated dependencies [77b5ca7, 77b5ca7, 51064e6, 5f05841]:

    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official release notes 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.