wrangler@4.79.0
📦 cloudflare-workersView on GitHub →
✨ 2 features🐛 5 fixes🔧 7 symbols
Summary
This release introduces CLI commands for managing Cloudflare AI Search and adds local development support for Workflows commands. It also includes several stability improvements, particularly around project auto-configuration and asset directory handling.
Migration Steps
- When using Workflows CLI commands locally, pass the `--local` flag to target `wrangler dev` (e.g., `wrangler workflows list --local`). Optionally use `--port` to specify a custom dev server port if it is not the default 8787.
✨ New Features
- Introduced `wrangler ai-search` command namespace for managing Cloudflare AI Search instances, including instance management (`list`, `create`, `get`, `update`, `delete`), semantic search (`search`), and instance stats (`stats`).
- Added `--local` flag to Workflows CLI commands (`wrangler workflows`) to target a running `wrangler dev` session instead of the Cloudflare production API.
🐛 Bug Fixes
- Fixed `getPlatformProxy` and `unstable_getMiniflareWorkerOptions` crashing when `assets` is configured without a `directory` by skipping asset setup in that scenario.
- Fixed autoconfig failing on `waku` projects that use `hono` by filtering out Hono detection when Waku is also detected.
- Suppressed misleading lock file warning during autoconfig for static projects (projects with no framework detected).
- Skipped unnecessary `GET /versions?deployable=true` API call in `wrangler versions deploy` when all version IDs are explicitly provided and `--yes` is passed.
- Improved error message when the assets directory path points to a file instead of a directory during autoconfig/deployment.