Cloudflare Release Notes
2538 release notes curated from 14 sources by the Releasebot Team. Last updated: Nov 17, 2026
Cloudflare Products (14)
- AI Gateway31 release notes
- Analytics147 release notes
- Application Performance98 release notes
- Application Security220 release notes
- Cloudflare AI208 release notes
- Cloudflare One263 release notes
- Consumer Services72 release notes
- Core Platform187 release notes
- Developer Platform465 release notes
- Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
Developer Platform by Cloudflare
Artifacts, Workers - Artifacts now supports local development
Developer Platform now supports local development and testing for Artifacts, including creating and importing repositories, using Git, and testing repository events and workflows before deployment. Local repos stay separate from production, with Wrangler and supported development tools using the simulator by default.
You can now develop and test Artifacts locally. Create repos, import Git repositories over HTTPS, issue repo tokens, and clone or push with Git on your machine before deploying to Cloudflare's global network. Local repos are separate from your deployed repos, so you can test changes without affecting production data. Local repos also emit the same Artifacts events as production when a repo is created, imported, forked, or deleted, or when a repo token is created or revoked. This lets you test the Workflows that react to them before you deploy. To use local repos when you run your Worker locally, add an Artifacts binding to your Wrangler configuration file: { "$schema": "./node_modules/wrangler/config-schema.json", "name": "artifacts-worker", "main": "src/index.ts", // Set this to today's date "compatibility_date": "2026-11-17", "artifacts": [ { "binding": "ARTIFACTS", "namespace": "default" } ] } name = "artifacts-worker" main = "src/index.ts" # Set this to today's date compatibility_date = "2026-11-17" [[artifacts]] binding = "ARTIFACTS" namespace = "default" Run npx wrangler dev, then use the binding the same way you would in production: const created = await env.ARTIFACTS.create("starter-repo"); return Response.json({ remote: created.remote, token: created.token, }); const created = await env.ARTIFACTS.create("starter-repo"); return Response.json({ remote: created.remote, token: created.token, }); The returned remote points to your local dev session, so you can use it with a standard Git client to clone and push. Local development requires the latest version of Wrangler and Git 2.32 or later on your PATH. When you develop with npx wrangler dev, the Cloudflare Vite plugin, or the Workers Vitest integration, Artifacts bindings use the local simulator by default. To use your deployed repos instead, set remote = true on the binding. To learn more, refer to Local development.
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
Cloudflare One, Gateway - Cloudflare One adds Periodic Beaconing Traffic detection
Cloudflare One adds Periodic Beaconing Traffic as a risk behavior, identifying unusual, regular HTTP check-ins to the same destination to help teams investigate potential command-and-control activity. The feature is off by default and available on Enterprise plans.
Cloudflare One now includes Periodic Beaconing Traffic as a risk behavior. It analyzes Gateway HTTP traffic for regular check-ins to the same destination. Cloudflare flags a user after more than 30 contacts to the same destination in six hours. Contacts must be evenly spaced, from 10 seconds to about 12 minutes apart. Few other users in your organization contact that destination. Detection uses traffic behavior only. It does not use threat intelligence, categories, or reputation. Malware can check in with a command-and-control (C2) server this way, but legitimate software also checks in regularly. Treat each event as a lead to investigate, not proof that a destination is C2. By default, the behavior is off and its risk level is Info. To turn it on, go to Risk score > Risk behaviors. Cloudflare reports a continuing beacon once. Events usually arrive 3 to 6 hours after the six-hour window closes. Periodic Beaconing Traffic is available on Enterprise plans.
Original source All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
Workers SDK ships Build Output v1 support, local Workflow starts from Artifacts events, and improved Vite project builds. It also fixes Wrangler config watching and container rollout defaults, while updating compatibility dates and dependencies.
Minor Changes #16917 d36b39d Thanks @jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location. #16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports. Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions. Patch Changes #16803 b219078 Thanks @petebacondarwin! - Run experimental cf projects with their installed Vite or Vite+ commands cf dev, cf build, and deployments that build your project can use Vite or Vite+ even when no framework command is detected. This removes the need for the internal cf-vite delegate and supports dependencies declared and hoisted at the root of a configured workspace. A workspace application using a custom-named Vite config should declare @cloudflare/vite-plugin in its own manifest, or add vite or vite-plus as a dependency or dev dependency to identify its tooling; this keeps shared root tools from selecting Vite for non-Vite siblings. Configs passed later via --config are evaluated by Vite when the command runs. Existing framework commands keep their priority. Consumers resolve bare executables using the detected nodeModulesPaths in order, adding .bin to each directory. Lookup stops at the validated workspace root; standalone applications use only their own node_modules/.bin. Project inspection can recognize an existing Cloudflare configuration before dependencies are installed. Running a command provides guidance when the required tools are missing or the plugin version does not support cf profiles (>=2.0.0-beta.v.13 <3). Vite evaluates the project configuration when the command runs, including dynamic configs and custom config files. Repair guidance uses the project’s detected package manager. Automatic setup asks users to convert CommonJS .cjs and .cts Vite configs to ESM imports and exports in .mjs or .mts before adding the ESM-only Cloudflare plugin. Native builds also work with the Windows shell. Pages migration safeguards, unsupported-framework setup checks, and Wrangler command selection retain their existing behavior. #16944 db3c071 Thanks @danlapid! - Stop wrangler dev from missing config file changes made soon after a reload wrangler dev replaced its config file watcher on every reload without waiting for the new one to start, so a change saved in that gap was never applied. It now keeps one watcher while the set of watched files is unchanged, and reports a config as applied only once its files are being watched. A second change saved within 50 ms of the previous one is no longer dropped either. #16920 81e56dd Thanks @benbuzbee! - Use the effective max_instances value when choosing the default container rollout steps When max_instances was omitted, Wrangler deployed 20 instances but chose rollout steps as if there were 0 instances, so the rollout used a single 100% step. Wrangler now uses [10, 100] for omitted max_instances, while still using a single 100% step when max_instances is 0 or 1. #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured. #16946 e97c9f8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler" The following dependency versions have been updated: Dependency From To @cloudflare/workers-types ^5.20261113.1 ^5.20261116.1 workerd 1.20261113.1 1.20261116.1 #16874 4335eac Thanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials Check access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token. #16917 d36b39d Thanks @jamesopstad! - Detect Cloudflare Build Output of any version before deploying wrangler deploy, wrangler versions upload and wrangler preview refuse to run in a project that has Cloudflare Build Output, because that output belongs to cf. Detection now looks for any .cloudflare/output/v<N>/ directory rather than only the root config of the current version, so output left by an older or newer cf is still caught. Updated dependencies [e97c9f8, e97c9f8, 349fc4e, 0bf81ac]: [email protected]
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
Workers SDK adds local Workflow starts from Artifacts events, aligns Pipelines, K2, and Analytics SQL binding fields with Cloudflare config, and updates the default compatibility date and bundled dependencies.
Minor Changes #16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events Declare Artifacts events on exports.workflow({ name, events }) in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports. Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions. #16907 0bf81ac Thanks @jamesopstad! - Rename the Pipelines, K2 and Analytics SQL env binding fields to match @cloudflare/config Config-style env bindings now use these shapes: { type: "pipeline", streamId } instead of { type: "pipeline", name } { type: "k2", id } instead of { type: "k2", stream } { type: "analytics-sql" } instead of { type: "analytics" } Patch Changes #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured. #16946 e97c9f8 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler" The following dependency versions have been updated: Dependency From To @cloudflare/workers-types ^5.20261113.1 ^5.20261116.1 workerd 1.20261113.1 1.20261116.1
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
Workers SDK improves deployment name detection by reading Build Output v1 with a v0 fallback, updates create-cloudflare framework dependencies, and adopts the bundled workerd compatibility date by default for newly scaffolded projects.
Patch Changes #16917 d36b39d Thanks @jamesopstad! - Find the deployed Worker's name in Build Output v1 After cf deploy, C3 reads the Worker's name from the Build Output to look up its workers.dev URL. It now reads .cloudflare/output/v1/, falling back to .cloudflare/output/v0/ because C3 installs cf@latest, which may still write v0. #16933 80f0e5b Thanks @dependabot! - Update dependencies of "create-cloudflare" The following dependency versions have been updated: Dependency From To @angular/create 22.2.6 22.2.7 #16934 6a6f10f Thanks @dependabot! - Update dependencies of "create-cloudflare" The following dependency versions have been updated: Dependency From To create-qwik 1.20.3 1.20.4 #16935 819ed90 Thanks @dependabot! - Update dependencies of "create-cloudflare" The following dependency versions have been updated: Dependency From To create-vike 0.0.692 0.0.694 #16936 f518803 Thanks @dependabot! - Update dependencies of "create-cloudflare" The following dependency versions have been updated: Dependency From To create-astro 5.3.1 5.3.2 #16937 4bca70b Thanks @dependabot! - Update dependencies of "create-cloudflare" The following dependency versions have been updated: Dependency From To create-analog 2.9.6 2.9.7 #16938 c46d179 Thanks @dependabot! - Update dependencies of "create-cloudflare" The following dependency versions have been updated: Dependency From To create-next-app 16.4.5 16.4.6 #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Original source Similar to Cloudflare with recent updates:
- Anthropic release notes960 release notes · Latest Nov 17, 2026
- OpenAI release notes1244 release notes · Latest Nov 16, 2026
- Google release notes2518 release notes · Latest Nov 16, 2026
- Apple release notes169 release notes · Latest Nov 16, 2026
- xAI release notes305 release notes · Latest Nov 5, 2026
- Perplexity release notes33 release notes · Latest Nov 6, 2026
- Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK updates the default compatibility date for new projects and adds local Workflow triggers from Artifacts events, with repository and token changes delivered to Workflow exports across supported local environments.
Patch Changes
#16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16246 349fc4e Thanks @leostera! - Start local Workflows from Artifacts events
Declare Artifacts events on
exports.workflow({ name, events })in cloudflare.config.ts to start the owning Workflow locally in cf, Vite, and Workers Vitest. Wrangler configurations continue to use triggers.events. Native config conversion derives those targets from the Workflow export, and cf migrate attaches existing event subscriptions to their matching Workflow exports.
Local Artifacts namespaces publish the documented cf.artifacts.* messages for repository create, import, fork, and delete operations and token creation and revocation. Successful create, import, and fork operations also publish the initial token-created event. Delivery follows the committed mutation, is unordered, and does not fail the repository operation if a destination rejects it. Push, clone, and fetch events are not yet published locally. This feature does not provide local Artifacts-to-queue subscriptions.
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK updates its default compatibility date for new projects and improves OAuth credential handling, reusing valid tokens from sibling processes to avoid redundant refreshes and prevent stale credentials from overwriting newer ones.
Patch Changes #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured. #16874 4335eac Thanks @petebacondarwin! - Avoid redundant OAuth refreshes after a sibling process updates credentials Check access-token expiry and select the refresh token from the same fresh credential snapshot. When a sibling has already saved a valid access token, reuse it without another exchange or write. This prevents an unnecessary rotation that can let an older response overwrite a newer refresh token. Updated dependencies [e97c9f8, 349fc4e]: @cloudflare/[email protected]
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK updates new-project scaffolding to default to the bundled workerd compatibility date, alongside dependency updates.
Patch Changes
#16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [b219078, d36b39d, db3c071, 81e56dd, e97c9f8, e97c9f8, 349fc4e, 0bf81ac, 4335eac, d36b39d]:
[email protected]
Original source
[email protected] - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK releases Vite plugin v2 as a release candidate and adds Build Output v1 support, clearer preview rebuild guidance, improved Worker configuration typing, and an updated default compatibility date.
Minor Changes #16917 d36b39d Thanks @jamesopstad! - Write Build Output to .cloudflare/output/v1/ and record the producer vite build and the experimental wrangler build --experimental-cf-build-output now write Build Output v1, with account settings nested under settings in the root config.json. They also record themselves as the producer, so readers can name the tool that wrote the output in error messages. Previews from Build Output read the account settings from their new location. #16921 6785363 Thanks @jamesopstad! - Release Vite plugin v2 as a release candidate Vite plugin v2 is now published as 2.0.0-rc.<n> under the rc npm tag. The deprecated ParsedInputConfigWithWorker type has been removed; use CloudflareConfig instead. #16907 0bf81ac Thanks @jamesopstad! - Make WorkerConfig the type accepted by auxiliary and prerender Worker config WorkerConfig from @cloudflare/vite-plugin is now the parsed Worker configuration that auxiliary and prerender Worker config accepts and returns, and that their callbacks receive as entryWorkerConfig. It previously re-exported the defineConfig() Worker type from @cloudflare/config, which didn't type-check as an auxiliary Worker config. To type a Worker in cloudflare.config.ts, import WorkerConfig from cf/config instead. Patch Changes #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured. #16917 d36b39d Thanks @jamesopstad! - Ask for a rebuild when preview finds missing or outdated Build Output When preview finds no Build Output, Build Output in the older v0 format, or Build Output in more than one format, it now says to build the project and preview again, rather than suggesting an upgrade. Updated dependencies [d36b39d, d36b39d, 0bf81ac, e97c9f8, e97c9f8, 349fc4e, 0bf81ac]: @cloudflare/[email protected] @cloudflare/[email protected] @cloudflare/[email protected] [email protected]
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK updates the default compatibility date to match bundled workerd when scaffolding projects or when no date is configured.
Patch Changes #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured. Updated dependencies [e97c9f8, e97c9f8, 349fc4e, 0bf81ac]: [email protected]
Original source - Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK updates its deployment, utilities, authentication, and Miniflare dependencies in a patch release.
Patch Changes
Updated dependencies [d36b39d, e97c9f8, e97c9f8, 349fc4e, 0bf81ac, 4335eac]:
- @cloudflare/[email protected]
- @cloudflare/[email protected]
- @cloudflare/[email protected]
- [email protected]
- Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
@cloudflare/[email protected]
Workers SDK now defaults new projects to the bundled workerd compatibility date and updates its Miniflare dependency.
Patch Changes #16946 e97c9f8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-16 Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured. Updated dependencies [e97c9f8, e97c9f8, 349fc4e, 0bf81ac]: [email protected]
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Developer Platform by Cloudflare
Browser Run - Browser Run Quick Actions now work in local development
Developer Platform now supports testing Browser Run Quick Actions locally with Wrangler and a local Chrome instance. The JSON action returns schema-matched placeholder data, and Kitesurf browser support is not yet available.
You can now test Browser Run Quick Actions locally. Under
npx wrangler dev, the browser binding's.quickAction()method runs against a Chrome instance on your machine. Before,.quickAction()worked only in remote mode, and local calls failed with The RPC receiver does not implement the method "quickAction".Note
There are currently two limitations in the local simulation:
- The json action is emulated. It requires an AI model to extract data, and the model is not available locally, so the action returns placeholder data that matches your schema.
- The Kitesurf browser is not supported yet.
For details, refer to Test Quick Actions locally.
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Developer Platform by Cloudflare
AI Search - Manage AI Search instances in any namespace with Terraform
Developer Platform’s Cloudflare Terraform provider now supports managing AI Search instances in any namespace, with namespace-aware imports and data sources. The update preserves the default namespace behavior while requiring explicit namespace settings for data sources.
Starting with Cloudflare Terraform provider ↗︎ v5.29.0, you can manage AI Search instances in any namespace, not only default.
The
cloudflare_ai_search_instanceresource has a newnamespaceargument. It defaults todefault, so existing configurations keep managing the same instances.resource "cloudflare_ai_search_namespace" "support" { account_id = var.account_id name = "support" } resource "cloudflare_ai_search_instance" "docs" { account_id = var.account_id id = "docs" namespace = cloudflare_ai_search_namespace.support.name }You can import existing instances and namespaces:
terraform import cloudflare_ai_search_instance.docs <account_id>/support/docs terraform import cloudflare_ai_search_namespace.support <account_id>/supportThe data sources read instances from the namespace you set:
data "cloudflare_ai_search_instance" "docs" { account_id = var.account_id namespace = "support" id = "docs" } data "cloudflare_ai_search_instances" "support" { account_id = var.account_id namespace = "support" }When you upgrade to v5.29.0, review these changes:
- The
cloudflare_ai_search_instanceimport ID now includes the namespace:<account_id>/<namespace>/<id>. For instances in the default namespace, use<account_id>/default/<id>. - The
cloudflare_ai_search_instanceandcloudflare_ai_search_instancesdata sources requirenamespace. Setnamespace = "default"for instances in the default namespace. cloudflare_ai_search_instancesreturns the instances in one namespace. Thefilter.namespaceargument ofcloudflare_ai_search_instanceis removed.- Changing namespace replaces the instance.
- Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
Developer Platform by Cloudflare
Billing, Workers, Durable Objects - Set spending limits for Workers and Durable Objects
Developer Platform adds spending limits and email alerts for Workers and Durable Objects, helping customers control compute costs without necessarily interrupting usage. Controls are available in the Cloudflare dashboard and cf CLI, alongside AI Gateway budgets and account-wide budget alerts.
You can now set spending limits for Workers and Durable Objects to help control unexpected usage costs, or receive email alerts while your applications keep running. Support for more products is coming soon.
Use these controls alongside AI Gateway spend limits to manage compute and AI inference costs across your application. AI Gateway supports per-user and per-model budgets for Workers AI and other AI providers, applied to requests routed through your gateway.
Workers and Durable Objects limits apply across your account for the current subscription billing period. Each product has its own spending controls.
Set your limits and alerts
In the Cloudflare dashboard ↗︎, select your account and go to Billing > Spend limits. Choose a spending limit, notification email, and alert thresholds for Workers or Durable Objects.
For example, configure a $10 Workers spending limit with email alerts at $5 and $9. To receive alerts while your applications keep running, turn off Block usage.
See when a limit takes effect
The overview shows each product's recorded spend, alert thresholds, and pause status. Email alerts notify you without stopping usage. When a spending limit takes effect, Cloudflare blocks the product's supported operations.
To resume usage, raise the limit above current spend, turn it off, or remove it. Usage also resumes when the next billing period starts.
Usage reporting and blocking take time, so recorded spend can exceed a limit. Read about what counts toward a limit.
Choose alerts, limits, or both
For example, set a $50 spending limit for Workers and a $20 email alert for Durable Objects:
flowchart LR A["Durable Objects reaches $20"] --> B["Email alert sent"] B --> C["Usage continues"] D["Workers reaches $50"] --> E["Spending limit takes effect"] E --> F["New Worker invocations blocked"]Set a spending limit with the cf CLI
Install the cf CLI and select your account, then run this command to set a $50 spending limit for Workers usage in the current billing period:
cf billing spend-policies create \ --name 'Workers $50 spending limit' \ --product-id workers \ --enabled true \ --threshold-cents 5000 \ --action usage_blockThe amount is in US cents: 5000 means $50. To set a spending limit for Durable Objects, use --product-id durable_objects and update the name. Limits count usage already recorded in the current billing period.
You can also give this prompt to your coding agent. It will ask which product you want to manage and what spending limit to set, then use the CLI to configure it.
Copy prompt
Prompt copied!
Use spending limits alongside budget alerts
The budget alerts introduced earlier this year notify you about account-wide usage costs without stopping usage. You can keep using them alongside the new product-specific spending limits and email alerts for Workers and Durable Objects.
To configure account-wide alerts, go to Billing > Billable Usage or follow the budget alerts guide.
Read the spending limits and alerts guide to learn how spending limits work and manage limits and alerts through the dashboard or cf CLI.
Original source
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.