wrangler@4.86.0
Breaking Changes📦 cloudflare-workersView on GitHub →
⚠ 1 breaking✨ 5 features🐛 3 fixes🔧 10 symbols
Summary
This release enhances CLI tooling with namespace support for AI Search, public sharing via Quick Tunnels in `wrangler dev`, and improved queue consumer listing. It also enforces remote access for Flagship bindings during local development.
⚠️ Breaking Changes
- Flagship bindings now exclusively use remote mode during local development, matching AI bindings. Previously, Flagship supported local stubs that returned default values. Users relying on the local stub behavior must update their expectations; the `remote` config field now only controls a warning about remote access charges during local dev.
Migration Steps
- If you were relying on the local stub behavior for Flagship bindings (which returned default values), be aware that local development now always accesses the remote Flagship service.
- If you use service bindings or tail consumers configured with `props` that target workers running in separate `wrangler dev` instances, no action is required; props forwarding is now fixed.
✨ New Features
- Added namespace support to all `wrangler ai-search` instance commands (`create`, `list`, `get`, `update`, `delete`, `stats`, `search`) via the `--namespace` or `-n` flag. Defaults to the `default` namespace if omitted.
- Introduced a new `wrangler ai-search namespace` subcommand group for managing namespaces directly (`list`, `create`, `get`, `update`, `delete`).
- Added `--tunnel` flag to `wrangler dev` to expose the local dev server publicly via a temporary Cloudflare Quick Tunnel (random *.trycloudflare.com URL).
- `wrangler tail` now logs stack traces, resolving frames if sourcemaps are uploaded.
- Added `wrangler queues consumer list` subcommands: `wrangler queues consumer list <queue-name>` (lists all types), `wrangler queues consumer worker list <queue-name>`, and `wrangler queues consumer http list <queue-name>`.
🐛 Bug Fixes
- Fixed service binding and tail consumer `props` being dropped when targeting workers in separate local dev instances via the dev registry; props are now forwarded correctly.
- Restored telemetry tracking for common boolean CLI flags (e.g., `--remote`, `--json`, `--force`) and specific fixed-choice arguments that were unintentionally dropped during argument sanitization.
- Fixed three resource leaks in `unstable_startWorker` teardown that could prevent Node from exiting cleanly after `worker.dispose()` by ensuring esbuild contexts are disposed correctly and awaiting builds during cleanup.