#12433 2acb277 Thanks @martinezjandrew! - Updated registries delete subcommand to handle new API response that now returns a secrets store secret reference after deletion. Wrangler will now prompt the user if they want to delete the associated secret. If so, added new logic to retrieve a secret by its name. The subcommand will then delete the secret.
#12307 e02b5f5 Thanks @dario-piotrowicz! - Improve autoconfig telemetry with granular event tracking
Adds detailed telemetry events to track the autoconfig workflow, including process start/end, detection, and configuration phases. Each event includes a unique session ID (appId), CI detection, framework information, and success/error status to help diagnose issues and understand usage patterns.
#12474 8ba1d11 Thanks @petebacondarwin! - Add wrangler pages deployment delete command to delete Pages deployments via CLI
You can now delete a Pages deployment directly from the command line:
wrangler pages deployment delete <deployment-id> --project-name <name>Use the --force (or -f) flag to skip the confirmation prompt, which is useful for CI/CD automation.
#12307 e02b5f5 Thanks @dario-piotrowicz! - Include all common telemetry properties in ad-hoc telemetry events
Previously, only command-based telemetry events (e.g., "wrangler command started/completed") included the full set of common properties. Ad-hoc events sent via sendAdhocEvent were missing important context like OS information, CI detection, and session tracking.
Now, all telemetry events include the complete set of common properties:
amplitude_session_id and amplitude_event_id for session trackingwranglerVersion (and major/minor/patch variants)osPlatform, osVersion, nodeVersionpackageManagerconfigFileTypeisCI, isPagesCI, isWorkersCIisInteractiveisFirstUsagehasAssetsagent#12479 fd902aa Thanks @dario-piotrowicz! - Add framework selection prompt during autoconfig
When running autoconfig in interactive mode, users are now prompted to confirm or change the detected framework. This allows correcting misdetected frameworks or selecting a framework when none was detected, defaulting to "Static" in that case.
#12465 961705c Thanks @petebacondarwin! - Add --json flag to wrangler pages project list command
You can now use the --json flag to output the project list as clean JSON instead of a formatted table. This enables easier programmatic processing and scripting workflows.
> wrangler pages project list --json
[
{
"Project Name": "my-pages-project",
"Project Domains": "my-pages-project-57h.pages.dev",
"Git Provider": "No",
"Last Modified": "23 hours ago"
},
...
]#12470 21ac7ab Thanks @petebacondarwin! - Add WRANGLER_COMMAND environment variable to custom build commands
When using a custom build command in wrangler.toml, you can now detect whether wrangler dev or wrangler deploy triggered the build by reading the WRANGLER_COMMAND environment variable.
This variable will be set to "dev", "deploy", "versions upload", or "types" depending on which command invoked the build. This allows you to customize your build process based on the deployment context.
Example usage in a build script:
if [ "$WRANGLER_COMMAND" = "dev" ]; then
echo "Building for development..."
else
echo "Building for production..."
fi#12468 5d56487 Thanks @petebacondarwin! - Add debug logs for git branch detection in wrangler pages deploy command
When running wrangler pages deploy, the command automatically detects git information (branch, commit hash, commit message, dirty state) from the local repository. Previously, when this detection failed, there was no way to troubleshoot the issue.
Now, running with WRANGLER_LOG=debug will output detailed information about:
Example usage:
WRANGLER_LOG=debug wrangler pages deploy ./dist --project-name=my-project#12447 c8dda16 Thanks @dario-piotrowicz! - fix: Throw a descriptive error when autoconfig cannot detect an output directory
When running wrangler setup or wrangler deploy --x-autoconfig on a project where the output directory cannot be detected, you will now see a clear error message explaining what's missing (e.g., "Could not detect a directory containing the static (html, css and js) files for the project") instead of a generic configuration error. This makes it easier to understand and resolve the issue.
#12440 555b32a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260205.0 | 1.20260206.0 |
#12485 d636d6a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260206.0 | 1.20260207.0 |
#12502 bf8df0c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260207.0 | 1.20260210.0 |
#12280 988dea9 Thanks @penalosa! - Fix wrangler init failing with Yarn Classic
When using Yarn Classic (v1.x), running wrangler init or wrangler init --from-dash would fail because Yarn Classic doesn't properly handle version specifiers with special characters like ^ in yarn create commands. Yarn would install the package correctly but then fail to find the binary because it would look for a path like .yarn/bin/create-cloudflare@^2.5.0 instead of .yarn/bin/create-cloudflare.
This fix removes the version specifier from the default C3 command entirely. Since C3 has had auto-update behavior for over two years, specifying a version is no longer necessary and removing it resolves the Yarn Classic compatibility issue.
#12486 1f1c3ce Thanks @vicb! - Bump esbuild to 0.27.3
This update includes several bug fixes from esbuild versions 0.27.1 through 0.27.3. See the esbuild changelog for details.
#12472 62635a0 Thanks @petebacondarwin! - Improve D1 database limit error message to match Cloudflare dashboard
When attempting to create a D1 database after reaching your account's limit, the CLI now shows a more helpful error message with actionable guidance instead of the raw API error.
The new message includes:
#12411 355c6da Thanks @jbwcloudflare! - Fix wrangler pages deploy to respect increased file count limits
#12449 bfd17cd Thanks @penalosa! - fix: Display unsafe metadata separately from bindings
Unsafe metadata are not bindings and should not be displayed in the bindings table. They are now printed as a separate JSON block.
Before:
Your Worker has access to the following bindings:
Binding Resource
env.extra_data ("interesting value") Unsafe Metadata
env.more_data ("dubious value") Unsafe Metadata
After:
The following unsafe metadata will be attached to your Worker:
{
"extra_data": "interesting value",
"more_data": "dubious value"
}
#12463 3388c84 Thanks @petebacondarwin! - Add User-Agent header to remote dev inspector WebSocket connections
When running wrangler dev --remote, the inspector WebSocket connection now includes a User-Agent header (wrangler/<version>). This resolves issues where WAF rules blocking empty User-Agent headers prevented remote dev mode from working with custom domains.
#12421 937425c Thanks @ryanking13! - Fix Python Workers deployment failing on Windows due to path separator handling
Previously, deploying Python Workers on Windows would fail because the backslash path separator (\) was not properly handled, causing the entire full path to be treated as a single filename. The deployment process now correctly normalizes paths to use forward slashes on all platforms.
Updated dependencies [2d90127, 555b32a, d636d6a, bf8df0c, 312b5eb, ce9dc01]:
Fetched March 31, 2026