wrangler@4.113.0
📦 cloudflare-workersView on GitHub →
✨ 8 features🐛 3 fixes🔧 13 symbols
Summary
This release enhances Wrangler with improved Email Routing integration, new configuration options for dependency instrumentation, and expanded resource provisioning. It also includes bug fixes for remote binding previews and error reporting.
Migration Steps
- For users utilizing the experimental new-config path (`wrangler --experimental-new-config` or `@cloudflare/vite-plugin` `experimental.newConfig` option), migrate account-level settings (`accountId`, `complianceRegion`) to a dedicated `settings` export using `defineSettings` in `cloudflare.config.ts`.
✨ New Features
- Worker trigger deployment now reconciles the Worker's Email Routing rules with the top-level `addresses` config.
- Added `exclude_packages` option to `dependencies_instrumentation` configuration, allowing exclusion of package name patterns from dependency metadata.
- Support for `artifacts` and `artifacts.repo` source types when creating Queue event subscriptions via `wrangler queues subscription create`.
- Expanded automatic resource provisioning to Queue, Dispatch Namespace, and Flagship bindings, allowing deployments to omit resource names or IDs.
- When `wrangler dev` is started in a headless AI agent environment, Wrangler now prints the Local Explorer API URL and basic resource routes.
- Added a `settings` export to the experimental `cloudflare.config.ts` config for account-level settings like `accountId` and `complianceRegion`.
- Wrangler now recognizes `nub` as a package manager and autoconfig detects `nub` projects.
- Added support for redacting sensitive Workflows step output in local dev for steps configured with `sensitive: "output"`.
🐛 Bug Fixes
- Fixed remote binding previews for accounts without a workers.dev subdomain by automatically registering one when required.
- Fixed stray characters in the Workers Sites asset-key-too-long error message, ensuring a clean termination at the documentation URL.
- Report the Worker's error for `HEAD` requests instead of an internal JSON parse error, preventing misleading error messages from miniflare's internals.