Changelog

D1 is now generally available and production ready. Read the blog post Open external link for more details on new features in GA and to learn more about the upcoming D1 read replication API.

• Developers with a Workers Paid plan now have a 10GB GB per-database limit (up from 2GB), which can be combined with existing limit of 50,000 databases per account.
• Developers with a Workers Free plan retain the 500 MB per-database limit and can create up to 10 databases per account.
• D1 databases can be exported as a SQL file.

Hyperdrive is now Generally Available and ready for production applications.

Read the announcement blog Open external link to learn more about the Hyperdrive and the roadmap, including upcoming support for MySQL databases.

• #5371 Open external link 77152f3 Open external link Thanks @G4brym Open external link ! - feature: remove requirement for @cloudflare/ai package to use Workers AI

  Previously, to get the correct Workers AI API, you needed to wrap your env.AI binding with new Ai() from @cloudflare/ai. This change moves the contents of @cloudflare/ai into the Workers runtime itself, meaning env.AI is now an instance of Ai, without the need for wrapping.

• Updated dependencies [ d994066 Open external link ]:

  • miniflare@3.20240329.0

• #5425 Open external link b7a6d9d Open external link Thanks @rozenmd Open external link ! - feat: implement wrangler d1 export

• #5426 Open external link 9343714 Open external link Thanks @RamIdeas Open external link ! - feature: added a new wrangler triggers deploy command

  This command currently requires the --experimental-versions flag.

  This command extracts the trigger deployment logic from wrangler deploy and allows users to update their currently deployed Worker’s triggers without doing another deployment. This is primarily useful for users of wrangler versions upload and wrangler versions deploy who can then run wrangler triggers deploy to apply trigger changes to their currently deployed Worker Versions.

  The command can also be used even if not using the wrangler versions ... commands. And, in fact, users are already using it implicitly when running wrangler deploy.

• #4932 Open external link dc0c1dc Open external link Thanks @xortive Open external link ! - feature: Add support for private networking in Hyperdrive configs

• #5369 Open external link 7115568 Open external link Thanks @mattdeboard Open external link ! - fix: Use queue name, not ID, for r2 bucket event-notification subcommands

  Since the original command was not yet operational, this update does not constitute a breaking change.

  Instead of providing the queue ID as the parameter to --queue, users must provide the queue name. Under the hood, we will query the Queues API for the queue ID given the queue name.

• #5413 Open external link 976adec Open external link Thanks @pmiguel Open external link ! - feature: Added Queue delivery controls support in wrangler.toml

• #5412 Open external link 3e5a932 Open external link Thanks @RamIdeas Open external link ! - feature: adds the --json option to wrangler deployments list --experimental-versions, wrangler deployments status --experimental-versions, wrangler versions list --experimental-versions and wrangler versions view --experimental-versions which will format the output as clean JSON. The --experimental-versions flag is still required for these commands.

• #5258 Open external link fbdca7d Open external link Thanks @OilyLime Open external link ! - feature: URL decode components of the Hyperdrive config connection string

• #5416 Open external link 47b325a Open external link Thanks @mattdeboard Open external link ! - fix: minor improvements to R2 notification subcommand

  1. r2 bucket event-notification <subcommand> becomes r2 bucket notification <subcommand>
  2. Parameters to --event-type use - instead of _ (e.g. object_create -> object-create)

  Since the original command was not yet operational, this update does not constitute a breaking change.

• #5419 Open external link daac6a2 Open external link Thanks @RamIdeas Open external link ! - chore: add helpful logging to –experimental-versions commands

• #5400 Open external link c90dd6b Open external link Thanks @RamIdeas Open external link ! - chore: log of impending change of “Deployment ID” to “Version ID” in wrangler deploy, wrangler deployments list, wrangler deployments view and wrangler rollback. This is a warning of a future change for anyone depending on the output text format, for example by grepping the output in automated flows.

• #5422 Open external link b341614 Open external link Thanks @geelen Open external link ! - fix: remove d1BetaWarning and all usages

  This PR removes the warning that D1 is in beta for all D1 commands.

• Updated dependencies [ fbdca7d Open external link ]:

  • miniflare@3.20240320.1

• #5373 Open external link 5bd8db8 Open external link Thanks @RamIdeas Open external link ! - feature: Implement versioned rollbacks via wrangler rollback [version-id] --experimental-versions.

  Please note, the experimental-versions flag is required to use the new behaviour. The original wrangler rollback command is unchanged if run without this flag.

• #5366 Open external link e11e169 Open external link Thanks @RamIdeas Open external link ! - fix: save non-versioned script-settings (logpush, tail_consumers) on wrangler versions deploy. This command still requires --experimental-versions.

• #5405 Open external link 7c701bf Open external link Thanks @RamIdeas Open external link ! - chore: add wrangler deployments view [deployment-id] --experimental-versions command

  This command will display an error message which points the user to run either wrangler deployments status --experimental-versions or wrangler versions view <version-id> --experimental-versions instead.

Messages published to a queue and/or marked for retry from a queue consumer can now be explicitly delayed. Delaying messages allows you to defer tasks until later, and/or respond to backpressure when consuming from a queue.

Refer to Batching and Retries to learn how to delay messages written to a queue.

• #5310 Open external link 528c011 Open external link Thanks @penalosa Open external link ! - feat: Watch the entire module root for changes in --no-bundle mode, rather than just the entrypoint file.

• #5327 Open external link 7d160c7 Open external link Thanks @penalosa Open external link ! - feat: Add wrangler pages download config

• #5284 Open external link f5e2367 Open external link Thanks @CarmenPopoviciu Open external link ! - feat: Add wrangler.toml support in wrangler pages dev

  As we are adding wrangler.toml support for Pages, we want to ensure that wrangler pages dev works with a configuration file.

• #5353 Open external link 3be826f Open external link Thanks @penalosa Open external link ! - feat: Updates wrangler pages functions build to support using configuration from wrangler.toml in the generated output.

• #5102 Open external link ba52208 Open external link Thanks @pmiguel Open external link ! - feature: add support for queue delivery controls on wrangler queues create

• #5327 Open external link 7d160c7 Open external link Thanks @penalosa Open external link ! - fix: Use specific error code to signal a wrangler.toml file not being found in build-env

• #5310 Open external link 528c011 Open external link Thanks @penalosa Open external link ! - fix: Reload Python workers when the requirements.txt file changes

Queues now supports pull-based consumers. A pull-based consumer allows you to pull from a queue over HTTP from any environment and/or programming language outside of Cloudflare Workers. A pull-based consumer can be useful when your message consumption rate is limited by upstream infrastructure or long-running tasks.

Review the documentation on pull-based consumers to configure HTTP-based pull.

• Added more supported languages.

• #5294 Open external link bdc121d Open external link Thanks @mattdeboard Open external link ! - feature: Add event-notification commands in support of event notifications for Cloudflare R2.

  Included are commands for creating and deleting event notification configurations for individual buckets.

• #5231 Open external link e88ad44 Open external link Thanks @w-kuhn Open external link ! - feature: Add support for configuring HTTP Pull consumers for Queues

  HTTP Pull consumers can be used to pull messages from queues via https request.

• #5317 Open external link 9fd7eba Open external link Thanks @GregBrimble Open external link ! - chore: Deprecate -- <command>, --proxy and --script-path options from wrangler pages dev.

  Build your application to a directory and run the wrangler pages dev <directory> instead. This results in a more faithful emulation of production behavior.

• Updated dependencies [ 248a318 Open external link ]:

  • miniflare@3.20240320.0

• #5337 Open external link 35660e27 Open external link Thanks @RamIdeas Open external link ! - fix: Ignore OPTIONS requests in Wrangler’s oauth server

  In Chrome v123, the auth requests from the browser back to wrangler now first include a CORS OPTIONS preflight request before the expected GET request. Wrangler was able to successfully complete the login with the first (OPTIONS) request, and therefore upon the second (GET) request, errored because the token exchange had already occured and could not be repeated.

  Wrangler now stops processing the OPTIONS request before completing the token exchange and only proceeds on the expected GET request.

  If you see a ErrorInvalidGrant in a previous wrangler version when running wrangler login, please try upgrading to this version or later.

• #5234 Open external link e739b7f Open external link Thanks @CarmenPopoviciu Open external link ! - feat: Implement environment inheritance for Pages configuration

  For Pages, Wrangler will not require both of the supported named environments (“preview” | “production”) to be explicitly defined in the config file. If either [env.production] or [env.preview] is left unspecified, Wrangler will use the top-level environment when targeting that named Pages environment.

• #5306 Open external link c60fed0 Open external link Thanks @taylorlee Open external link ! - fix: Remove triggered_by annotation from experimental versions deploy command which is now set by the API and cannot be set by the client.

• #5321 Open external link ac93411 Open external link Thanks @RamIdeas Open external link ! - fix: rename --experimental-gradual-rollouts to --experimental-versions flag

  The --experimental-gradual-rollouts flag has been made an alias and will still work.

  And additional shorthand alias --x-versions has also been added and will work too.

• #5324 Open external link bfc4282 Open external link Thanks @penalosa Open external link ! - fix: Ignore OPTIONS requests in Wrangler’s oauth server

• #5099 Open external link 93150aa Open external link Thanks @KaiSpencer Open external link ! - feat: expose --show-interactive-dev-session flag

  This flag controls the interactive mode of the dev session, a feature that already exists internally but was not exposed to the user. This is useful for CI/CD environments where the interactive mode is not desired, or running in tools like turbo and nx.

Hyperdrive now supports a WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME> environmental variable for configuring local development to use a test/non-production database, in addition to the localConnectionString configuration in wrangler.toml.

Refer to Local development for instructions on how to configure Hyperdrive locally.

• #5166 Open external link 133a190 Open external link Thanks @CarmenPopoviciu Open external link ! - feat: Implement config file validation for Pages projects

  Wrangler proper has a mechanism in place through which it validates a wrangler.toml file for Workers projects. As part of adding wrangler toml support for Pages, we need to put a similar mechanism in place, to validate a configuration file against Pages specific requirements.

• #5279 Open external link 0a86050 Open external link Thanks @penalosa Open external link ! - feat: Support the hidden command wrangler pages functions build-env

• #5093 Open external link a676f55 Open external link Thanks @benycodes Open external link ! - feature: add –dispatch-namespace to wrangler deploy to support uploading Workers directly to a Workers for Platforms dispatch namespace.

• #5275 Open external link e1f2576 Open external link Thanks @petebacondarwin Open external link ! - fix: ensure tail exits when the WebSocket disconnects

  Previously when the tail WebSocket disconnected, e.g. because of an Internet failure, the wrangler tail command would just hang and neither exit nor any longer receive tail messages.

  Now the process exits with an exit code of 1, and outputs an error message.

  The error message is formatted appropriately, if the tail format is set to json.

  Fixes #3927

• #5069 Open external link 8f79981 Open external link Thanks @RamIdeas Open external link ! - chore: deprecate wrangler version command

  wrangler version is an undocumented alias for wrangler --version. It is being deprecated in favour of the more conventional flag syntax to avoid confusion with a new (upcoming) wrangler versions command.

• Updated dependencies [ 1720f0a Open external link ]:

  • miniflare@3.20240314.0

The default content type for messages published to a queue is now json, which improves compatibility with the upcoming pull-based queues.

Any Workers created on or after the compatibility date of 2024-03-18, or that explicitly set the queues_json_messages compatibility flag, will use the new default behaviour. Existing Workers with a compatibility date prior will continue to use v8 as the default content type for published messages.

As of wrangler@3.33.0, wrangler d1 execute and wrangler d1 migrations apply now default to using a local database, to match the default behavior of wrangler dev.

It is also now possible to specify one of --local or --remote to explicitly tell wrangler which environment you wish to run your commands against.

• Built-in APIs that return Promises will now produce stack traces when the Promise rejects. Previously, the rejection error lacked a stack trace.
• A new compat flag fetcher_no_get_put_delete removes the get(), put(), and delete() methods on service bindings and Durable Object stubs. This will become the default as of compatibility date 2024-03-26. These methods were designed as simple convenience wrappers around fetch(), but were never documented.
• Updated v8 to version 12.3.

As of 2024-03-05, D1 usage will start to be counted and may incur charges for an account’s future billing cycle.

Developers on the Workers Paid plan with D1 usage beyond included limits will incur charges according to D1’s pricing.

Developers on the Workers Free plan can use up to the included limits. Usage beyond the limits below requires signing up for the $5/month Workers Paid plan.

Account billable metrics are available in the Cloudflare Dashboard Open external link and GraphQL API.

• API Shield no longer prevents Version Management enablement and zone settings configurations.

Calling retry() or retryAll() on a message or message batch will no longer have an impact on how Queues scales consumer concurrency.

Previously, using explicit retries via retry() or retryAll() would count as an error and could result in Queues scaling down the number of concurrent consumers.

• Sockets now support an opened attribute.
• Durable Object alarm handlers now impose a maximum wall time of 15 minutes.

A previous change (made on 2024-02-13) to the run() query statement method has been reverted.

run() now returns a D1Result, including the result rows, matching its original behaviour prior to the change on 2024-02-13.

Future change to run() to return a D1ExecResult, as originally intended and documented, will be gated behind a compatibility date as to avoid breaking existing Workers relying on the way run() currently works.

• NEW: add manager.route support for Managed Components
• NEW: introduce zaraz.spaPageview() for manually triggering SPA pageviews
• NEW: add support for client-evaluated triggers (UI update following shortly)
• Pinterest MC: Add ecommerce support
• Google Ads MC: Append url and rnd params to pagead/landing endpoint
• Bugfix: Add noindex robots headers for Zaraz GET endpoint responses
• Bugfix: Gracefully handle responses from custom MCs without mapped endpoints

D1’s raw(), all() and run() query statement methods have been updated to reflect their intended behaviour and improve compatibility with ORM libraries.

raw() now correctly returns results as an array of arrays, allowing the correct handling of duplicate column names (such as when joining tables), as compared to all(), which is unchanged and returns an array of objects. To include an array of column names in the results when using raw(), use raw({columnNames: true}).

run() no longer incorrectly returns a D1Result and instead returns a D1ExecResult as originally intended and documented.

This may be a breaking change for some applications that expected raw() to return an array of objects.

Refer to D1 client API to review D1’s query methods, return types and TypeScript support in detail.

• Dashboard: rename “tracks” to “events” for consistency
• Pinterest Conversion API MC: update parameters sent to api
• HTTP MC: update _settings prefix usage handling
• Bugfix: better minification of client-side js
• Bugfix: fix bug where anchor link click events were not bubbling when using click listener triggers
• API update: begin migration support from deprecated tool.neoEvents array to tool.actions object config schema migration

Vectorize /query HTTP endpoint has the following changes:

• returnVectors request body property is deprecated in favor of returnValues and returnMetadata properties.
• Response format has changed to the below format to match [Workers API change]:(/workers/configuration/compatibility-dates/#vectorize-query-with-metadata-optionally-returned)

{
  "result": {
    "count": 1,
    "matches": [
      {
        "id": "4",
        "score": 0.789848214,
        "values": [ 75.0999984741211, 67.0999984741211, 29.899999618530273],
        "metadata": {
          "url": "/products/sku/418313",
          "streaming_platform": "netflix"
        }
      }
    ]
  },
  "errors": [],
  "messages": [],
  "success": true
}

• Google Analytics 4 Managed Component: Fix Google Analytics 4 average engagement time metric.

Databases using D1’s legacy alpha backend will no longer run automated hourly backups. You may still choose to take manual backups of these databases.

The D1 team recommends moving to D1’s new production backend, which will require you to export and import your existing data. D1’s production backend is faster than the original alpha backend. The new backend also supports Time Travel, which allows you to restore your database to any minute in the past 30 days without relying on hourly or manual snapshots.

• Added Pre-Clearance mode.

Vectorize now supports metadata filtering with equals ($eq) and not equals ($neq) operators. Metadata filtering limits query() results to only vectors that fulfill new filter property.

let metadataMatches = await env.YOUR_INDEX.query(queryVector, { topK: 3, filter: { streaming_platform: "netflix" }, returnValues: true, returnMetadata: true } )

Only new indexes created on or after 2023-12-06 support metadata filtering. Currently, there is no way to migrate previously created indexes to work with metadata filtering.

• The Web Platform standard navigator.sendBeacon(...) API is now provided by the Workers runtime.
• V8 updated to 12.0.

• Added meta.lastUpdated to all summaries and top endpoints (timeseries and timeseriesGroups already had this).
• Fix meta.dateRange to return date ranges for all requested series.

• Added Layer 3 top origin locations Open API docs link and top target location Open API docs link .
• Added Layer 7 Summaries by http_method, http_version, ip_version, managed_rules, mitigation_product.
• Added Layer 7 Timeseries Groups by http_method, http_version, ip_version, managed_rules, mitigation_product, industry, vertical.
• Added Layer 7 Top by industry, vertical.
• Deprecated Layer 7 timeseries groups without dimension Open API docs link .
  • To continue getting this data, switch to the new timeseries group by mitigation_product Open API docs link endpoint.
• Deprecated Layer 7 summary without dimension) Open API docs link .
  • To continue getting this data, switch to the new summary by mitigation_product Open API docs link endpoint.
• Added new Error codes.

• HTTP Request Managed Component: Re-added __zarazTrack property.

Vectorize now supports distinct returnMetadata and returnValues arguments when querying an index, replacing the now-deprecated returnVectors argument. This allows you to return metadata without needing to return the vector values, reducing the amount of unnecessary data returned from a query. Both returnMetadata and returnValues default to false.

For example, to return only the metadata from a query, set returnMetadata: true.

let matches = await env.YOUR_INDEX.query(queryVector, { topK: 5, returnMetadata: true })

New Workers projects created on or after 2023-11-08 or that update the compatibility date for an existing project will use the new return type.

• Added a direction parameter to all Layer 3 endpoints. Use together with location parameter to filter by origin or target location timeseries groups Open API docs link .

• Google Analytics 4 Managed Component: Remove debug_mode key if falsy or false.

• A new usage model called Workers Standard is available for Workers and Pages Functions pricing. This is now the default usage model for accounts that are first upgraded to the Workers Paid plan. Read the blog post Open external link for more information.
• The usage model set in a script’s wrangler.toml will be ignored after an account has opted-in to Workers Standard pricing. It must be configured through the dashboard (Workers & Pages > Select your Worker > Settings > Usage Model).
• Workers and Pages Functions on the Standard usage model can set custom CPU limits for their Workers

• Real-time Logs: Logs are now real-time, showing logs for the last hour. If you have a need for persistent logs, please let the team know on Discord. We are building out a persistent logs feature for those who want to store their logs for longer.
• Providers: Azure OpenAI is now supported as a provider!
• Docs: Added Azure OpenAI example.
• Bug Fixes: Errors with costs and tokens should be fixed.

• Custom HTML: Added support for non-JavaScript script tags.

• Added the crypto_preserve_public_exponent compatibility flag to correct a wrong type being used in the algorithm field of RSA keys in the WebCrypto API.

• Bing Managed Component: Fixed an issue where some events were not being sent to Bing even after being triggered.
• Dashboard: Improved welcome screen for new Zaraz users".

• The limit of 3 Cron Triggers per Worker has been removed. Account-level limits on the total number of Cron Triggers across all Workers still apply.

• A TCP Socket’s WritableStream now ensures the connection has opened before resolving the promise returned by close.

• Partners can now create and view accounts through the Cloudflare dashboard by going to Tenants > Managed Accounts.

• Logs: Logs will now be limited to the last 24h. If you have a use case that requires more logging, please reach out to the team on Discord.
• Dashboard: Logs now refresh automatically.
• Docs: Fixed Workers AI example in docs and dash.
• Caching: Embedding requests are now cacheable. Rate limit will not apply for cached requests.
• Bug Fixes: Identical requests to different providers are not wrongly served from cache anymore. Streaming now works as expected, including for the Universal endpoint.
• Known Issues: There’s currently a bug with costs that we are investigating.

• The Web Platform standard CustomEvent class Open external link is now available in Workers.
• Fixed a bug in the WebCrypto API where the publicExponent field of the algorithm of RSA keys would have the wrong type. Use the crypto_preserve_public_exponent compatibility flag to enable the new behavior.

Developers building on Queues can now create up to 10,000 queues per account, enabling easier per-user, per-job and sharding use-cases.

Refer to Limits to learn more about Queues’ current limits.

• Added Traffic Anomalies Alerts to notify customers when traffic to their domain has an unexpected spike or drop.

Queue consumers can now scale to 20 concurrent invocations (per queue), up from 10. This allows you to scale out and process higher throughput queues more quickly.

Queues with no explicit limit specified will automatically scale to the new maximum.

This limit will continue to grow during the Queues beta.

Developers using D1 on a Workers Paid plan can now create up to 50,000 databases as part of ongoing increases to D1’s limits.

• This further enables database-per-user use-cases and allows you to isolate data between customers.
• Total storage per account is now 50 GB.
• D1’s analytics and metrics provide per-database usage data.

If you need to create more than 50,000 databases or need more per-account storage, reach out to the D1 team to discuss.

• Bugfix: Fixed an issue that prevented some server-side requests from arriving to their destination
• Google Analytics 4 Managed Component: Add support for dbg and ir fields.

D1 is now in public beta, and storage limits have been increased:

• Developers with a Workers Paid plan now have a 2 GB per-database limit (up from 500 MB) and can create 25 databases per account (up from 10). These limits will continue to increase automatically during the public beta.
• Developers with a Workers Free plan retain the 500 MB per-database limit and can create up to 10 databases per account.

Databases must be using D1’s new storage subsystem to benefit from the increased database limits.

Read the announcement blog Open external link for more details about what is new in the beta and what is coming in the future for D1.

Hyperdrive is now available in public beta to any developer with a Workers paid plan.

To start using Hyperdrive, visit the get started guide or read the announcement blog Open external link to learn more.

• Added Incident Alerts Open external link .

Vectorize, Cloudflare’s vector database, is now in open beta Open external link . Vectorize allows you to store and efficiently query vector embeddings from AI/ML models from Workers AI, OpenAI, and other embeddings providers or machine-learning workflows.

To get started with Vectorize, see the guide.

Low-Latency HTTP Live Streaming (LL-HLS) is now in open beta. Enable LL-HLS on your live input for automatic low-latency playback using the Stream built-in player where supported.

For more information, refer to live input and custom player docs.

• Version Management now supports versioning for Bot Management.

• An implementation of the node:crypto API from Node.js is now available when the nodejs_compat compatibility flag is enabled.

• Added support for D1’s new storage subsystem Open external link . All Git builds and deployments done with Wrangler v3.5.0 and up can use the new subsystem.
• Builds which fail due to exceeding the build time limit will return a proper error message indicating so rather than Internal error.
• New and improved error messages for other build failures

• Consent Management: Add support for custom button translations.
• Consent Management: Modal stays fixed when scrolling.
• Google Analytics 4 Managed Component: hideOriginalIP and ga-audiences can be set from tool event.

• Reddit Managed Component: Support new “Account ID” formats (e.g. “ax_xxxxx”).

• Added Connection Tampering summary Open API docs link and timeseries Open API docs link endpoints.

• Advanced Waiting Room customers can now add multiple hostname and path combinations to a single waiting room via the UI and API.

• Consent Management: Consent cookie name can now be customized.

• Segment Managed Component: API Endpoint can be customized.

• Added Client-side errors.

• Added Logo Match Alert.

• Commit messages can now be up to 384 characters before being trimmed.

• TikTok Managed Component: Support setting ttp and event_id.
• Consent Management: Accessibility improvements.
• Facebook Managed Component: Support for using “Limited Data Use” features.

D1 now returns a count of rows_written and rows_read for every query executed, allowing you to assess the cost of query for both pricing and index optimization purposes.

The meta object returned in D1’s Client API contains a total count of the rows read (rows_read) and rows written (rows_written) by that query. For example, a query that performs a full table scan (for example, SELECT * FROM users) from a table with 5000 rows would return a rows_read value of 5000:

"meta": {
  "duration": 0.20472300052642825,
  "size_after": 45137920,
  "rows_read": 5000,
  "rows_written": 0
}

Refer to D1 pricing documentation to understand how reads and writes are measured. D1 remains free to use during the alpha period.

• Added Regional Internet Registry (see field source in response) to get asn by id Open API docs link and get asn by ip Open API docs link endpoints.
• Stopped collecting data in the old Layer 3 data source.
• Updated Layer 3 timeseries Open API docs link endpoint to start using the new Layer 3 data source by default, fetching the old data source now requires sending the parameter metric=bytes_old.
• Deprecated Layer 3 summary Open API docs link endpoint, this will stop receiving data after 2023-08-14.
  • To continue getting this data, switch to the new timeseries group protocol Open API docs link endpoint.
• Deprecated Layer 3 timeseries groups Open API docs link endpoint, this will stop receiving data after 2023-08-14.
  • To continue getting this data, switch to the new timeseries group protocol Open API docs link endpoint.

You can now bind a D1 database to your Workers directly in the Cloudflare dashboard Open external link . To bind D1 from the Cloudflare dashboard, select your Worker project -> Settings -> Variables -> and select D1 Database Bindings.

Note: If you have previously deployed a Worker with a D1 database binding with a version of wrangler prior to 3.5.0, you must upgrade to wrangler v3.5.0 Open external link first before you can edit your D1 database bindings in the Cloudflare dashboard. New Workers projects do not have this limitation.

Legacy D1 alpha users who had previously prefixed their database binding manually with __D1_BETA__ should remove this as part of this upgrade. Your Worker scripts should call your D1 database via env.BINDING_NAME only. Refer to the latest D1 getting started guide for best practices.

We recommend all D1 alpha users begin using wrangler 3.5.0 (or later) to benefit from improved TypeScript types and future D1 API improvements.

Stream now supports adding a scheduled deletion date to new and existing videos. Live inputs support deletion policies for automatic recording deletion.

For more, refer to the video on demand or live input docs.

Databases using D1’s new storage subsystem can now grow to 500 MB each, up from the previous 100 MB limit. This applies to both existing and newly created databases.

Refer to Limits to learn about D1’s limits.

• Support newer TLDs such as .party and .music.

• Updated HTTP timeseries endpoints urls to timeseries_groups ( example Open API docs link ) due to consistency. Old timeseries endpoints are still available, but will soon be removed.

• Added [turnstile.isExpired].
• Added uk language.

Databases created via the Cloudflare dashboard and Wrangler (as of v3.4.0) now use D1’s new storage subsystem by default. The new backend can be 6 - 20x faster Open external link than D1’s original alpha backend.

To understand which storage subsystem your database uses, run wrangler d1 info YOUR_DATABASE and inspect the version field in the output.

Databases with version: beta use the new storage backend and support the Time Travel API. Databases with version: alpha only use D1’s older, legacy backend.

Time Travel is now available. Time Travel allows you to restore a D1 database back to any minute within the last 30 days (Workers Paid plan) or 7 days (Workers Free plan), at no additional cost for storage or restore operations.

Refer to the Time Travel documentation to learn how to travel backwards in time.

Databases using D1’s new storage subsystem Open external link can use Time Travel. Time Travel replaces the snapshot-based backups used for legacy alpha databases.

• Added urlscanner endpoints Open API docs link , read more here.

• An implementation of the util.MIMEType Open external link API from Node.js is now available when the nodejs_compat compatibility flag is enabled.

• V2 build system is now default for all new projects.

• Sped up project creation.

• An implementation of the process.env API from Node.js is now available when using the nodejs_compat compatibility flag.
• An implementation of the diagnostics_channel API from Node.js is now available when using the nodejs_compat compatibility flag.

• Improved performance for ranged reads on very large files. Previously ranged reads near the end of very large files would be noticeably slower than ranged reads on smaller files. Performance should now be consistently good independent of filesize.

You can now view per-database metrics via both the Cloudflare dashboard Open external link and the GraphQL Analytics API.

D1 currently exposes read & writes per second, query response size, and query latency percentiles.

• Added the strict_crypto_checks compatibility flag to enable additional Web Crypto API error and security checking.
• Fixes regression in the TCP Sockets API where connect("google.com:443") would fail with a TypeError.

• Multipart ETags are now MD5 hashes.

• Added quality endpoints Open API docs link .

• The TCP Sockets API now reports clearer errors when a connection cannot be established.
• Updated V8 to 11.5.

• Fixed a bug where calling GetBucket Open API docs link on a non-existent bucket would return a 500 instead of a 404.
• Improved S3 compatibility for ListObjectsV1, now nextmarker is only set when truncated is true.
• The R2 worker bindings now support parsing conditional headers with multiple etags. These etags can now be strong, weak or a wildcard. Previously the bindings only accepted headers containing a single strong etag.
• S3 putObject now supports sha256 and sha1 checksums. These were already supported by the R2 worker bindings.
• CopyObject in the S3 compatible api now supports Cloudflare specific headers which allow the copy operation to be conditional on the state of the destination object.

As of wrangler v3.1.1 Open external link the D1 client API now returns detailed error messages within the top-level Error.message property, and no longer requires developers to inspect the Error.cause.message property.

To facilitate a transition from the previous Error.cause behaviour, detailed error messages will continue to be populated within Error.cause as well as the top-level Error object until approximately July 14th, 2023. Future versions of both wrangler and the D1 client API will no longer populate Error.cause after this date.

• AbortSignal.any() is now available.
• Updated V8 to 11.4.
• Following an update to the WHATWG URL spec Open external link , the delete() and has() methods of the URLSearchParams class now accept an optional second argument to specify the search parameter’s value. This is potentially a breaking change, so it is gated behind the new urlsearchparams_delete_has_value_arg and url_standard compatibility flags.
• Added the strict_compression_checks compatibility flag for additional DecompressionStream error checking.

• Added BGP stats Open API docs link , pfx2as Open API docs link and moas Open API docs link endpoints.

• A new Hibernatable WebSockets API (beta) has been added to Durable Objects. The Hibernatable WebSockets API allows a Durable Object that is not currently running an event handler (for example, processing a WebSocket message or alarm) to be removed from memory while keeping its WebSockets connected (“hibernation”). A Durable Object that hibernates will not incur billable Duration (GB-sec) charges.

• Added idempotency support for POST /siteverify requests via the idempotency_key parameter.

D1 has a new experimental storage back end that dramatically improves query throughput, latency and reliability. The experimental back end will become the default back end in the near future. To create a database using the experimental backend, use wrangler and set the --experimental-backend flag when creating a database:

$ wrangler d1 create your-database --experimental-backend

Read more about the experimental back end in the announcement blog Open external link .

• Builds which fail due to Out of memory (OOM) will return a proper error message indicating so rather than Internal error.

• The V2 build system is now available in open beta. Enable the V2 build system by going to your Pages project in the Cloudflare dashboard and selecting Settings > Build & deployments Open external link > Build system version.

• Smart placement can now be enabled for Pages within your Pages Project by going to Settings > Functions Open external link .

Stream supports adding multiple audio tracks to an existing video.

For more, refer to the documentation to get started.

• The new connect() method allows you to connect to any TCP-speaking services directly from your Workers. To learn more about other protocols supported on the Workers platform, visit the new Protocols documentation.
• We have added new native database integrations for popular serverless database providers, including Neon, PlanetScale, and Supabase. Native integrations automatically handle the process of creating a connection string and adding it as a Secret to your Worker.
• You can now also connect directly to databases over TCP from a Worker, starting with PostgreSQL. Support for PostgreSQL is based on the popular pg driver, and allows you to connect to any PostgreSQL instance over TLS from a Worker directly.
• The R2 Migrator (Super Slurper), which automates the process of migrating from existing object storage providers to R2, is now Generally Available.

• Cursor, an experimental AI assistant, trained to answer questions about Cloudflare’s Developer Platform, is now available to preview! Cursor can answer questions about Workers and the Cloudflare Developer Platform, and is itself built on Workers. You can read more about Cursor in the announcement blog Open external link .

• The performance.now() Open external link and performance.timeOrigin Open external link APIs can now be used in Cloudflare Workers. Just like Date.now(), for security reasons time only advances after I/O.

• Added IOS as an option for the OS parameter in all HTTP endpoints ( example Open API docs link ).

• The new nodeJsCompatModule type can be used with a Worker bundle to emulate a Node.js environment. Common Node.js globals such as process and Buffer will be present, and require('...') can be used to load Node.js built-ins without the node: specifier prefix.
• Fixed an issue where websocket connections would be disconnected when updating workers. Now, only websockets connected to Durable Object instances are disconnected by updates to that Durable Object’s code.

• The Web Crypto API now supports curves Ed25519 and X25519 defined in the Secure Curves specification.
• The global connect method has been moved to a cloudflare:sockets module.

Cloudflare Stream now supports player enhancement properties.

With player enhancements, you can modify your video player to incorporate elements of your branding, such as your logo, and customize additional options to present to your viewers.

For more, refer to the documentation to get started.

• Added Maintenance Notification Alerts.

• Added references to Turnstile Public API.
• Added references for [after-interactive-callback], [before-interactive-callback], and [unsupported-callback].

• No externally-visible changes this week.

• URL.canParse(...) is a new standard API for testing that an input string can be parsed successfully as a URL without the additional cost of creating and throwing an error.
• The Workers-specific IdentityTransformStream and FixedLengthStream classes now support specifying a highWaterMark for the writable-side that is used for backpressure signaling using the standard writer.desiredSize/writer.ready mechanisms.

• GetBucket Open API docs link is now available for use through the Cloudflare API.
• Location hints can now be set when creating a bucket, both through the S3 API, and the dashboard.

• Fixed a bug in Wrangler tail and live logs on the dashboard that prevented the Administrator Read-Only and Workers Tail Read roles from successfully tailing Workers.

• Files uploaded are now visible for Git projects, you can view them in the Cloudflare dashboard Open external link .

Previously, generating a download for a live recording exceeding four hours resulted in failure.

To fix the issue, now video downloads are only available for live recordings under four hours. Live recordings exceeding four hours can still be played but cannot be downloaded.

• Notifications for Pages events are now available in the Cloudflare dashboard Open external link . Events supported include:
  • Deployment started.
  • Deployment succeeded.
  • Deployment failed.

• Added AS112 endpoints Open API docs link .
• Added email endpoints Open API docs link .

• The ListParts API has been implemented and is available for use.
• HTTP2 is now enabled by default for new custom domains linked to R2 buckets.
• Object Lifecycles are now available for use.
• Bug fix: Requests to public buckets will now return the Content-Encoding header for gzip files when Accept-Encoding: gzip is used.

Queue consumers will soon automatically scale up concurrently as a queues’ backlog grows in order to keep overall message processing latency down. Concurrency will be enabled on all existing queues by 2023-03-28.

To opt-out, or to configure a fixed maximum concurrency, set max_concurrency = 1 in your wrangler.toml file or via the queues dashboard Open external link .

To opt-in, you do not need to take any action: your consumer will begin to scale out as needed to keep up with your message backlog. It will scale back down as the backlog shrinks, and/or if a consumer starts to generate a higher rate of errors. To learn more about how consumers scale, refer to the consumer concurrency documentation.

• Added Pages Alerts.

• No externally-visible changes.

• Added [execution] and [appearance].

• Workers Logpush now supports 300 characters per log line. This is an increase from the previous limit of 150 characters per line.

• Added Brand Protection Alerts.

You can now acknowledge individual messages with a batch by calling .ack() on a message.

This allows you to mark a message as delivered as you process it within a batch, and avoids the entire batch from being redelivered if your consumer throws an error during batch processing. This can be particularly useful when you are calling external APIs, writing messages to a database, or otherwise performing non-idempotent actions on individual messages within a batch.

• Added the [turnstile.ready] callback.

• Added support for Analytics Engine in Functions.

• Fixed a bug where transferring large request bodies to a Durable Object was unexpectedly slow.
• Previously, an error would be thrown when trying to access unimplemented standard Request and Response properties. Now those will be left as undefined.

• Added the [data-]language parameter.

• R2 authentication tokens created via the R2 token page are now scoped to a single account by default.

• IPv6 percentage started to be calculated as (IPv6 requests / requests for dual-stacked content), where as before it was calculated as (IPv6 requests / IPv4+IPv6 requests).

• Durable Objects can now use jurisdictions with idFromName via a new subnamespace API.
• V8 updated to 10.9.

• Added new Layer 3 data source and related endpoints.
• Updated Layer 3 timeseries Open API docs link endpoint to support fetching both current and new data sources. For retro-compatibility reasons, fetching the new data source requires sending the parameter metric=bytes else the current data source will be returned.
• Deprecated old Layer 3 endpoints TimeseriesGroups Open API docs link and Summary Open API docs link . Users should upgrade to newer endpoints.

• Added support for Queues producer in Functions.

Cloudflare Stream now detects non-video content on upload using the POST API and returns a 400 Bad Request HTTP error with code 10059.

Previously, if you or one of your users attempted to upload a file that is not a video (ex: an image), the request to upload would appear successful, but then fail to be encoded later on.

With this change, Stream responds to the upload request with an error, allowing you to give users immediate feedback if they attempt to upload non-video content.

• POST /siteverify supports JSON requests now.

• Fix CORS preflight requests for the S3 API, which allows using the S3 SDK in the browser.
• Passing a range header to the get operation in the R2 bindings API should now work as expected.

• Aliased deployments can now be deleted. If using the API, you will need to add the query parameter force=true.

• Requests with the header x-amz-acl: public-read are no longer rejected.
• Fixed issues with wildcard CORS rules and presigned URLs.
• Fixed an issue where ListObjects would time out during delimited listing of unicode-normalized keys.
• S3 API’s PutBucketCors now rejects requests with unknown keys in the XML body.
• Signing additional headers no longer breaks CORS preflight requests for presigned URLs.

Stream now supports adding multiple audio tracks to an existing video upload. This allows you to:

• Provide viewers with audio tracks in multiple languages
• Provide dubbed audio tracks, or audio commentary tracks (ex: Director’s Commentary)
• Allow your users to customize the customize the audio mix, by providing separate audio tracks for music, speech or other audio tracks.
• Provide Audio Description tracks to ensure your content is accessible. ( WCAG 2.0 Guideline 1.2 1 Open external link )

To request an invite to the beta, refer to this post Open external link .

• Fixed a bug in ListObjects where startAfter would skip over objects with keys that have numbers right after the startAfter prefix.
• Add worker bindings for multipart uploads.

• You can now deep-link to a Pages deployment in the dashboard with :pages-deployment. An example would be https://dash.cloudflare.com?to=/:account/pages/view/:pages-project/:pages-deployment.

• Pages functions are now GA. For more information, refer to the blog post Open external link .
• We also made the following updates to Functions:
  • Functions metrics Open external link are now available in the dashboard.
  • Functions billing is now available.
  • The Unbound usage model is now available for Functions.
  • Secrets are now available.
  • Functions tailing is now available via the dashboard Open external link or with Wrangler (wrangler pages deployment tail).

• Unconditionally return HTTP 206 on ranged requests to match behavior of other S3 compatible implementations.
• Fixed a CORS bug where AllowedHeaders in the CORS config were being treated case-sensitively.

• Service bindings are now available in Functions. For more details, refer to the docs.

• Added retry and retry-interval for controlling retry behavior.

• Copying multipart objects via CopyObject is re-enabled.
• UploadPartCopy is re-enabled.

Cloudflare Stream’s WHIP Open external link and WHEP Open external link implementations now support Trickle ICE Open external link , reducing the time it takes to initialize WebRTC connections, and increasing compatibility with WHIP and WHEP clients.

For more, refer to the docs.

The “per-video” analytics API is being deprecated. If you still use this API, you will need to switch to using the GraphQL Analytics API by February 1, 2023. After this date, the per-video analytics API will be no longer available.

The GraphQL Analytics API provides the same functionality and more, with additional filters and metrics, as well as the ability to fetch data about multiple videos in a single request. Queries are faster, more reliable, and built on a shared analytics system that you can use across many Cloudflare products.

For more about this change and how to migrate existing API queries, refer to this post Open external link and the GraphQL Analytics API docs.

Cloudflare Stream now has no limit on the number of live inputs Open API docs link you can create. Stream is designed to allow your end-users to go live — live inputs can be created quickly on-demand via a single API request for each of user of your platform or app.

For more on creating and managing live inputs, get started with the docs.

• Multipart upload part sizes are always expected to be of the same size, but this enforcement is now done when you complete an upload instead of being done very time you upload a part.
• Fixed a performance issue where concurrent multipart part uploads would get rejected.

• Renamed the [data-]expired-callback callback to [data-]timeout-callback (called when the challenge times out).
• Added the [data-]expired-callback callback (called when the token expires).

• Fixed ranged reads for multipart objects with part sizes unaligned to 64KiB.

• Added response-field and response-field-name for controlling the input element created by Turnstile.
• Added option for changing the size of the Turnstile widget.

When playing live video, Cloudflare Stream now provides significantly more accurate estimates of the bandwidth needs of each quality level to client video players. This ensures that live video plays at the highest quality that viewers have adequate bandwidth to play.

As live video is streamed to Cloudflare, we transcode it to make it available to viewers at mulitple quality levels. During transcoding, we learn about the real bandwidth needs of each segment of video at each quality level, and use this to provide an estimate of the bandwidth requirements of each quality level the in HLS (.m3u8) and DASH (.mpd) manifests.

If a live stream contains content with low visual complexity, like a slideshow presentation, the bandwidth estimates provided in the HLS manifest will be lower, ensuring that the most viewers possible view the highest quality level, since it requires relatively little bandwidth. Conversely, if a live stream contains content with high visual complexity, like live sports with motion and camera panning, the bandwidth estimates provided in the HLS manifest will be higher, ensuring that viewers with inadequate bandwidth switch down to a lower quality level, and their playback does not buffer.

This change is particularly helpful if you’re building a platform or application that allows your end users to create their own live streams, where these end users have their own streaming software and hardware that you can’t control. Because this new functionality adapts based on the live video we receive, rather than just the configuration advertised by the broadcaster, even in cases where your end users’ settings are less than ideal, client video players will not receive excessively high estimates of bandwidth requirements, causing playback quality to decrease unnecessarily. Your end users don’t have to be OBS Studio experts in order to get high quality video playback.

No work is required on your end — this change applies to all live inputs, for all customers of Cloudflare Stream. For more, refer to the docs.

• HeadBucket now sets x-amz-bucket-region to auto in the response.

• Added validation for action: /^[a-z0-9_-]{0,32}$/i
• Added validation for cData: /^[a-z0-9_-]{0,255}$/i

• Added turnstile.remove

• Temporarily disabled UploadPartCopy while we investigate an issue.

• You can now deep-link to a Pages project in the dashboard with :pages-project. An example would be https://dash.cloudflare.com?to=/:account/pages/view/:pages-project.

Cloudflare Stream now supports playback of live videos and live recordings using the AV1 codec Open external link , which uses 46% less bandwidth than H.264.

For more, read the blog post Open external link .

• Fixed a CORS issue where Access-Control-Allow-Headers was not being set for preflight requests.

• Fixed a bug where CORS configuration was not being applied to S3 endpoint.
• No-longer render the Access-Control-Expose-Headers response header if ExposeHeader is not defined.
• Public buckets will no-longer return the Content-Range response header unless the response is partial.
• Fixed CORS rendering for the S3 HeadObject operation.
• Fixed a bug where no matching CORS configuration could result in a 403 response.
• Temporarily disable copying objects that were created with multipart uploads.
• Fixed a bug in the Workers bindings where an internal error was being returned for malformed ranged .get requests.

• CORS preflight responses and adding CORS headers for other responses is now implemented for S3 and public buckets. Currently, the only way to configure CORS is via the S3 API.
• Fixup for bindings list truncation to work more correctly when listing keys with custom metadata that have " or when some keys/values contain certain multi-byte UTF-8 values.
• The S3 GetObject operation now only returns Content-Range in response to a ranged request.

Cloudflare Stream now supports live video streaming over WebRTC, with sub-second latency, to unlimited concurrent viewers.

For more, read the blog post Open external link or the get started with example code in the docs.

• The R2 put() binding options can now be given an onlyIf field, similar to get(), that performs a conditional upload.
• The R2 delete() binding now supports deleting multiple keys at once.
• The R2 put() binding now supports user-specified SHA-1, SHA-256, SHA-384, SHA-512 checksums in options.
• User-specified object checksums will now be available in the R2 get() and head() bindings response. MD5 is included by default for non-multipart uploaded objects.

Previously, all plans had a maximum of 10 custom domains per project.

Now, the limits are:

• Free: 100 custom domains.
• Pro: 250 custom domains.
• Business and Enterprise: 500 custom domains.

• Pages now offers support for _routes.json. For more details, refer to the documentation.

• The S3 CopyObject operation now includes x-amz-version-id and x-amz-copy-source-version-id in the response headers for consistency with other methods.
• The ETag for multipart files uploaded until shortly after Open Beta uploaded now include the number of parts as a suffix.

• The S3 DeleteObjects operation no longer trims the space from around the keys before deleting. This would result in files with leading / trailing spaces not being able to be deleted. Additionally, if there was an object with the trimmed key that existed it would be deleted instead. The S3 DeleteObject operation was not affected by this.
• Fixed presigned URL support for the S3 ListBuckets and ListObjects operations.

URLs in the Stream Dashboard and Stream API now use a subdomain specific to your Cloudflare Account: customer-{CODE}.cloudflarestream.com. This change allows you to:

1. Use Content Security Policy Open external link (CSP) directives specific to your Stream subdomain, to ensure that only videos from your Cloudflare account can be played on your website.

2. Allowlist only your Stream account subdomain at the network-level to ensure that only videos from a specific Cloudflare account can be accessed on your network.

No action is required from you, unless you use Content Security Policy (CSP) on your website. For more on CSP, read the docs.

• R2 and D1 bindings are now supported.

• Uploads will automatically infer the Content-Type based on file body if one is not explicitly set in the PutObject request. This functionality will come to multipart operations in the future.

• Fixed S3 conditionals to work properly when provided the LastModified date of the last upload, bindings fixes will come in the next release.
• If-Match / If-None-Match headers now support arrays of ETags, Weak ETags and wildcard (*) as per the HTTP standard and undocumented AWS S3 behavior.

• Added dummy implementation of the following operation that mimics the response that a basic AWS S3 bucket will return when first created: GetBucketAcl.

• Added dummy implementations of the following operations that mimic the response that a basic AWS S3 bucket will return when first created:

  • GetBucketVersioning
  • GetBucketLifecycleConfiguration
  • GetBucketReplication
  • GetBucketTagging
  • GetObjectLockConfiguration

• Fixed an S3 compatibility issue for error responses with MinIO .NET SDK and any other tooling that expects no xmlns namespace attribute on the top-level Error tag.
• List continuation tokens prior to 2022-07-01 are no longer accepted and must be obtained again through a new list operation.
• The list() binding will now correctly return a smaller limit if too much data would otherwise be returned (previously would return an Internal Error).

• Improvements to 500s: we now convert errors, so things that were previously concurrency problems for some operations should now be TooMuchConcurrency instead of InternalError. We’ve also reduced the rate of 500s through internal improvements.
• ListMultipartUpload correctly encodes the returned Key if the encoding-type is specified.

• S3 XML documents sent to R2 that have an XML declaration are not rejected with 400 Bad Request / MalformedXML.
• Minor S3 XML compatibility fix impacting Arq Backup on Windows only (not the Mac version). Response now contains XML declaration tag prefix and the xmlns attribute is present on all top-level tags in the response.
• Beta ListMultipartUploads support.

• Support the r2_list_honor_include compat flag coming up in an upcoming runtime release (default behavior as of 2022-07-14 compat date). Without that compat flag/date, list will continue to function implicitly as include: ['httpMetadata', 'customMetadata'] regardless of what you specify.
• cf-create-bucket-if-missing can be set on a PutObject/CreateMultipartUpload request to implicitly create the bucket if it does not exist.
• Fix S3 compatibility with MinIO client spec non-compliant XML for publishing multipart uploads. Any leading and trailing quotes in CompleteMultipartUpload are now optional and ignored as it seems to be the actual non-standard behavior AWS implements.

Pages now supports .dev.vars in wrangler pages, which allows you to use use environmental variables during your local development without chaining --envs.

This functionality requires Wrangler v2.0.16 or higher.

• Unsupported search parameters to ListObjects/ListObjectsV2 are now rejected with 501 Not Implemented.
• Fixes for Listing:
  • Fix listing behavior when the number of files within a folder exceeds the limit (you’d end up seeing a CommonPrefix for that large folder N times where N = number of children within the CommonPrefix / limit).
  • Fix corner case where listing could cause objects with sharing the base name of a "folder" to be skipped.
  • Fix listing over some files that shared a certain common prefix.
• DeleteObjects can now handle 1000 objects at a time.
• S3 CreateBucket request can specify x-amz-bucket-object-lock-enabled with a value of false and not have the requested rejected with a NotImplemented error. A value of true will continue to be rejected as R2 does not yet support object locks.

• Fixed a regression for some clients when using an empty delimiter.
• Added support for S3 pre-signed URLs.

• Fixed a regression in the S3 API UploadPart operation where TooMuchConcurrency & NoSuchUpload errors were being returned as NoSuchBucket.

Pages has added deltas to wrangler pages publish.

We now keep track of the files that make up each deployment and intelligently only upload the files that we have not seen. This means that similar subsequent deployments should only need to upload a minority of files and this will hopefully make uploads even faster.

This functionality requires Wrangler v2.0.11 or higher.

• Fixed a bug with the S3 API ListObjectsV2 operation not returning empty folder/s as common prefixes when using delimiters.
• The S3 API ListObjectsV2 KeyCount parameter now correctly returns the sum of keys and common prefixes rather than just the keys.
• Invalid cursors for list operations no longer fail with an InternalError and now return the appropriate error message.

• The ContinuationToken field is now correctly returned in the response if provided in a S3 API ListObjectsV2 request.
• Fixed a bug where the S3 API AbortMultipartUpload operation threw an error when called multiple times.

• PR comments for Pages previews now include the branch alias.

• Fixed a bug where the S3 API’s PutObject or the .put() binding could fail but still show the bucket upload as successful.
• If conditional headers Open external link are provided to S3 API UploadObject or CreateMultipartUpload operations, and the object exists, a 412 Precondition Failed status code will be returned if these checks are not met.

• Fixed a bug when Accept-Encoding was being used in SignedHeaders when sending requests to the S3 API would result in a SignatureDoesNotMatch response.

• Fixed a bug where requests to the S3 API were not handling non-encoded parameters used for the authorization signature.
• Fixed a bug where requests to the S3 API where number-like keys were being parsed as numbers instead of strings.

• Add support for S3 virtual-hosted style paths Open external link , such as <BUCKET>.<ACCOUNT_ID>.r2.cloudflarestorage.com instead of path-based routing (<ACCOUNT_ID>.r2.cloudflarestorage.com/<BUCKET>).
• Implemented GetBucketLocation for compatibility with external tools, this will always return a LocationConstraint of auto.

• S3 API GetObject ranges are now inclusive (bytes=0-0 will correctly return the first byte).
• S3 API GetObject partial reads return the proper 206 Partial Content response code.
• Copying from a non-existent key (or from a non-existent bucket) to another bucket now returns the proper NoSuchKey / NoSuchBucket response.
• The S3 API now returns the proper Content-Type: application/xml response header on relevant endpoints.
• Multipart uploads now have a -N suffix on the etag representing the number of parts the file was published with.
• UploadPart and UploadPartCopy now return proper error messages, such as TooMuchConcurrency or NoSuchUpload, instead of ‘internal error’.
• UploadPart can now be sent a 0-length part.

• When using the S3 API, an empty string and us-east-1 will now alias to the auto region for compatibility with external tools.
• GetBucketEncryption, PutBucketEncryption and DeleteBucketEncrypotion are now supported (the only supported value currently is AES256).
• Unsupported operations are explicitly rejected as unimplemented rather than implicitly converting them into ListObjectsV2/PutBucket/DeleteBucket respectively.
• S3 API CompleteMultipartUploads requests are now properly escaped.

• Pagination cursors are no longer returned when the keys in a bucket is the same as the MaxKeys argument.
• The S3 API ListBuckets operation now accepts cf-max-keys, cf-start-after and cf-continuation-token headers behave the same as the respective URL parameters.
• The S3 API ListBuckets and ListObjects endpoints now allow per_page to be 0.
• The S3 API CopyObject source parameter now requires a leading slash.
• The S3 API CopyObject operation now returns a NoSuchBucket error when copying to a non-existent bucket instead of an internal error.
• Enforce the requirement for auto in SigV4 signing and the CreateBucket LocationConstraint parameter.
• The S3 API CreateBucket operation now returns the proper location response header.

• The S3 API now supports unchunked signed payloads.
• Fixed .put() for the Workers R2 bindings.
• Fixed a regression where key names were not properly decoded when using the S3 API.
• Fixed a bug where deleting an object and then another object which is a prefix of the first could result in errors.
• The S3 API DeleteObjects operation no longer returns an error even though an object has been deleted in some cases.
• Fixed a bug where startAfter and continuationToken were not working in list operations.
• The S3 API ListObjects operation now correctly renders Prefix, Delimiter, StartAfter and MaxKeys in the response.
• The S3 API ListObjectsV2 now correctly honors the encoding-type parameter.
• The S3 API PutObject operation now works with POST requests for s3cmd compatibility.

• The S3 API DeleteObjects request now properly returns a MalformedXML error instead of InternalError when provided with more than 128 keys.

Cloudflare Stream now supports the SRT live streaming protocol. SRT is a modern, actively maintained streaming video protocol that delivers lower latency, and better resilience against unpredictable network conditions. SRT supports newer video codecs and makes it easier to use accessibility features such as captions and multiple audio tracks.

For more, read the blog post Open external link .

You can now opt-in to the Stream Connect beta, and use Cloudflare Stream to restream live video to any platform that accepts RTMPS input, including Facebook, YouTube and Twitch.

For more, read the blog post Open external link or the docs.

You can now use Cloudflare Stream to restream or simulcast live video to any platform that accepts RTMPS input, including Facebook, YouTube and Twitch.

For more, read the blog post Open external link or the docs.

A brand new version of the Stream Player is now available for preview. New features include:

• Unified controls across desktop and mobile devices
• Keyboard shortcuts
• Intelligent mouse cursor interactions with player controls
• Phased out support for Internet Explorer 11

For more, refer to this post Open external link on the Cloudflare Community Forum.

You can now use the tus protocol when allowing creators (your end users) to upload their own videos directly to Cloudflare Stream.

In addition, all uploads to Cloudflare Stream made using tus are now faster and more reliable as part of this change.