wrangler@4.64.0
📦 cloudflare-workersView on GitHub →
✨ 8 features🐛 1 fixes🔧 4 symbols
Summary
This release introduces new CLI capabilities for managing Pages deployments and enhances build context awareness via environment variables. It also significantly improves telemetry coverage and error reporting during project autoconfiguration.
Migration Steps
- If you rely on the output of `wrangler pages project list` being strictly formatted text, update scripts to handle JSON output when using the `--json` flag, or ensure the flag is omitted.
- If you use custom build commands and need to differentiate between `wrangler dev` and `wrangler deploy` builds, check for the presence and value of the `WRANGLER_COMMAND` environment variable in your build scripts.
✨ New Features
- Added logic to the registries delete subcommand to prompt the user to delete the associated secret if the API returns a secret store secret reference after deletion.
- Added detailed telemetry events to track the autoconfig workflow, including process start/end, detection, configuration phases, CI detection, and framework information.
- Introduced `wrangler pages deployment delete <deployment-id> --project-name <name>` command to delete Pages deployments via CLI.
- Added `--force` or `-f` flag to `wrangler pages deployment delete` to skip the confirmation prompt.
- Ensured all ad-hoc telemetry events sent via `sendAdhocEvent` now include the complete set of common properties (session ID, version, OS info, CI status, etc.).
- When running autoconfig interactively, users are now prompted to confirm or change the detected framework, defaulting to "Static" if none is detected.
- Added `--json` flag to `wrangler pages project list` command to output results as JSON for easier programmatic processing.
- Added `WRANGLER_COMMAND` environment variable to custom build commands, set to the invoking command (e.g., "dev", "deploy"), allowing context-aware build customization.
🐛 Bug Fixes
- When running `wrangler setup` or `wrangler deploy --x-autoconfig`, a descriptive error is now thrown if the output directory cannot be detected, replacing generic configuration errors.