chore(deps): update dependency wrangler to v4 #201

renovate · 2025-03-13T14:51:22Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	`^3.91.0` → `^4.0.0`

Release Notes

cloudflare/workers-sdk (wrangler)

`v4.64.0`

Compare Source

Minor Changes

#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 tracking
- wranglerVersion (and major/minor/patch variants)
- osPlatform, osVersion, nodeVersion
- packageManager
- configFileType
- isCI, isPagesCI, isWorkersCI
- isInteractive
- isFirstUsage
- hasAssets
- agent
#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
```

Patch Changes

#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:
- Whether a git repository is detected
- Each git command being executed and its result
- The detected values (branch, commit hash, commit message, dirty status)
- Any errors that occur during detection
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:
- A clear explanation that the account limit has been reached
- A link to D1 documentation
- Commands to list and delete databases
#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]:
- miniflare@4.20260210.0
- @cloudflare/unenv-preset@2.12.1

`v4.63.0`

Compare Source

Minor Changes

#12386 447daa3 Thanks @NuroDev! - Added new "open local explorer" hotkey for experimental/WIP local resource explorer

When running wrangler dev with the experimental local explorer feature enabled, you can now press the e hotkey to open the local resource explorer UI in your browser.

Patch Changes

#11350 ee9b81f Thanks @dario-piotrowicz! - fix: improve error message when the entrypoint is incorrect

Error messages for incorrect entrypoint configuration have been improved to provide clearer and more actionable feedback. The updated messages help users understand what went wrong and how to fix their configuration.
#12402 63f1adb Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260131.0 1.20260203.0
#12418 ba13de9 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260203.0 1.20260205.0
#12216 fe3af35 Thanks @ichernetsky-cf! - Deprecate 'wrangler cloudchamber apply' in favor of 'wrangler deploy'
#12368 bd4bb98 Thanks @KianNH! - Preserve Containers configuration when using versions commands

Previously, commands like wrangler versions upload would inadvertently disable Containers on associated Durable Object namespaces because the containers property was being omitted from the API request body.
#12396 dab4bc9 Thanks @petebacondarwin! - fix: redact email addresses and account names in non-interactive mode

To prevent sensitive information from being exposed in public CI logs, email addresses and account names are now redacted when running in non-interactive mode (e.g., CI environments). Account IDs remain visible to aid debugging.
#12378 18c0784 Thanks @X6TXY! - Truncate Pages commit messages at UTF-8 boundaries to avoid invalid UTF-8
Updated dependencies [63f1adb, ba13de9, 83adb2c]:
- miniflare@4.20260205.0

`v4.62.0`

Compare Source

Minor Changes

#12064 964a39d Thanks @G4brym! - Add AI Search OAuth scopes to login

Adds ai-search:write and ai-search:run OAuth scopes to the default login scopes, enabling wrangler to authenticate with AI Search APIs.

#11867 253a85d Thanks @rahulsuresh-git! - Add wrangler r2 bucket local-uploads command to manage local uploads for R2 buckets

When enabled, object data is written to the nearest region first, then asynchronously replicated to the bucket's primary region.

Docs: https://developers.cloudflare.com/r2/buckets/local-uploads

# Get local uploads status
wrangler r2 bucket local-uploads get my-bucket

# Enable local uploads (will prompt for confirmation)
wrangler r2 bucket local-uploads enable my-bucket

# Enable without confirmation prompt
wrangler r2 bucket local-uploads enable my-bucket --force

# Disable local uploads
wrangler r2 bucket local-uploads disable my-bucket

#11803 1bd1488 Thanks @dario-piotrowicz! - Add a new subrequests limit to the limits field of the Wrangler configuration file

Before only the cpu_ms limit was supported in the limits field of the Wrangler configuration file, now a subrequests limit can be specified as well which enables the user to limit the number of fetch requests that a Worker's invocation can make.

Example:
```
{
	"$schema": "./node_modules/wrangler/config-schema.json",
	"limits": {
		"cpu_ms": 1000,
		"subrequests": 150 // newly added field
	}
}
```
#12185 f7aa8c7 Thanks @penalosa! - Add timestamp field to the version metadata binding in local development. The version metadata binding now includes id, tag, and timestamp fields, making it easier to test version-aware logic locally.

Patch Changes

#12190 ce736b9 Thanks @dario-piotrowicz! - Update autoconfig logic to handle Next.js projects by using the new @opennextjs/cloudflare migrate command
#12065 47944d1 Thanks @langningchen! - Improve error message when d1 export --output points to a directory
#12292 4c4d5a5 Thanks @dario-piotrowicz! - Add versionCommand to the autoconfig_summary field in the autoconfig output entry

Add the version upload command to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY/WRANGLER_OUTPUT_FILE_PATH. This complements the existing buildCommand and deployCommand fields and allows CI systems to know how to upload new versions of Workers.

For example, for a standard npm project this would be:
- Version command: npx wrangler versions upload
While for a Next.js project it would be:
- Version command: npx @opennextjs/cloudflare upload
#12050 b05b919 Thanks @NuroDev! - Fixed Wrangler's error handling for both invalid commands with and without the --help flag, ensuring consistent and clear error messages.

Additionally, it also ensures that if you provide an invalid argument to a valid command, Wrangler will now correctly display that specific commands help menu.
#12289 0aaf080 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260128.0 1.20260129.0
#12295 b981db5 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260129.0 1.20260130.0
#12355 a113c0d Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260130.0 1.20260131.0
#11971 fdd7a9f Thanks @dario-piotrowicz! - Add framework id, build command, and deploy command to the autoconfig_summary field in the deploy output entry

Add the framework id alongside the commands to build and deploy the project to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH.

For example for an npm Astro project these would be:
- Framework id: astro
- Build command: npm run build
- Deploy command: npx wrangler deploy
While for a Next.js project they would instead be:
- Framework id: next
- Build command: npx @opennextjs/cloudflare build
- Deploy command: npx @opennextjs/cloudflare deploy
#12211 a5fca2c Thanks @elithrar! - Remove the 'pubsub' sub-command and related functionality

The Pub/Sub product was never made publicly available and has been discontinued. This removes the wrangler pubsub command and all associated functionality.
Updated dependencies [0c9625a, 0aaf080, b981db5, a113c0d, f7aa8c7]:
- miniflare@4.20260131.0
- @cloudflare/kv-asset-handler@0.4.2

`v4.61.1`

Compare Source

Patch Changes

#12189 eb8a415 Thanks @NuroDev! - Fixed Durable Object missing migrations warning message.

If a Workers project includes some durable_objects in it but no migrations we show a warning to the user to add migrations to their config. However, this warning recommended new_classes for their migrations, but we instead now recommend all users use new_sqlite_classes instead.
#11804 3b06b18 Thanks @emily-shen! - fix: allow d1 execute, d1 export, and d1 migrations to work locally without database_id in config.
#12183 17961bb Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260124.0 1.20260127.0
#12196 52fdfe7 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260127.0 1.20260128.0
#12199 6d8d9cd Thanks @petebacondarwin! - Prevent wrangler logout from failing when the Wrangler configuration file is invalid

Previously, if your wrangler.toml or wrangler.json file contained syntax errors or invalid values, the wrangler logout command would fail. Now, configuration parsing errors are caught and logged at debug level, allowing you to log out regardless of the state of your configuration file.
#12153 cb72c11 Thanks @petebacondarwin! - Sanitize commands and arguments in telemetry to prevent accidentally capturing sensitive information.

Changes:
- Renamed telemetry fields from command/args to sanitizedCommand/sanitizedArgs to distinguish from historical fields that may have contained sensitive data in older versions
- Command names now come from command definitions rather than user input, preventing accidental capture of sensitive data pasted as positional arguments
- Sentry breadcrumbs now use the safe command name from definitions
- Argument values are only included if explicitly allowed via COMMAND_ARG_ALLOW_LIST
- Argument keys (names) are always included since they come from command definitions, not user input
Updated dependencies [8a210af, 17961bb, 52fdfe7, 5f060c9]:
- miniflare@4.20260128.0
- @cloudflare/unenv-preset@2.12.0

`v4.61.0`

Compare Source

Minor Changes

#12008 e414f05 Thanks @penalosa! - Add support for customising the inspector IP address

Adds a new --inspector-ip CLI flag and dev.inspector_ip configuration option to allow customising the IP address that the inspector server listens on. Previously, the inspector was hardcoded to listen only on 127.0.0.1.

Example usage:
```
# CLI flag
wrangler dev --inspector-ip 0.0.0.0
```
```
// wrangler.json
{
	"dev": {
		"inspector_ip": "0.0.0.0",
	},
}
```
#12034 05714f8 Thanks @emily-shen! - Add a no-op local explorer worker, which is gated by the experimental flag X_LOCAL_EXPLORER.

Patch Changes

#12134 a0a9ef6 Thanks @NuroDev! - Fixed Fish shell tab completions.

The wrangler tab completions are powered by @bomb.sh/tab which has been upgraded to version 0.0.12 which includes a fix for the Fish shell which was previously not working at all.
#12006 ad4666c Thanks @penalosa! - Remove --use-remote option from wrangler hyperdrive create command

Hyperdrive does not support remote bindings during local development - it requires a localConnectionString to connect to a local database. This change removes the confusing "remote resource" prompt that was shown when creating a Hyperdrive config.

Fixes #11674
#11853 014e7aa Thanks @43081j! - Use built-in stripVTControlCharacters utility rather than the strip-ansi package.
#12040 77e82d2 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260120.0 1.20260122.0
#12061 f08ef21 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260122.0 1.20260123.0
#12088 0641e6c Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260123.0 1.20260124.0
#12044 eacedba Thanks @edmundhung! - Fix wrangler secret list to error when the Worker is not found

Previously, running wrangler secret list against a non-existent Worker would silently return an empty array, making it difficult to diagnose issues like being logged into the wrong account. It now returns an error with suggestions for common causes.
#12150 e8b2ef5 Thanks @dario-piotrowicz! - Emit autoconfig summary as a separate output entry

Move the autoconfig summary from the deploy output entry to a dedicated autoconfig output entry type. This entry is now emitted by both wrangler deploy and wrangler setup commands when autoconfig runs, making it easier to track autoconfig results independently of deployments.
Updated dependencies [014e7aa, e414f05, 77e82d2, f08ef21, 0641e6c, 05714f8, bbd8a5e]:
- miniflare@4.20260124.0

`v4.60.0`

Compare Source

Minor Changes

#11113 bba0968 Thanks @AmirSa12! - Add wrangler complete command for shell completion scripts (bash, zsh, powershell)

Usage:
```
# Bash
wrangler complete bash >> ~/.bashrc

# Zsh
wrangler complete zsh >> ~/.zshrc

# Fish
wrangler complete fish >> ~/.config/fish/completions/wrangler.fish

# PowerShell
wrangler complete powershell > $PROFILE
```
- Uses @bomb.sh/tab library for cross-shell compatibility
- Completions are dynamically generated from experimental_getWranglerCommands() API
#11893 f9e8a45 Thanks @NuroDev! - wrangler types now generates per-environment TypeScript interfaces when named environments exist in your configuration.

When your configuration has named environments (an env object), wrangler types now generates both:
- Per-environment interfaces (e.g., StagingEnv, ProductionEnv) containing only the bindings explicitly declared in each environment, plus inherited secrets
- An aggregated Env interface with all bindings from all environments (top-level + named environments), where:
  - Bindings present in all environments are required
  - Bindings not present in all environments are optional
  - Secrets are always required (since they're inherited everywhere)
  - Conflicting binding types across environments produce union types (e.g., KVNamespace | R2Bucket)
However, if your config does not contain any environments, or you manually specify an environment via --env, wrangler types will continue to generate a single interface as before.

Example:

Given the following wrangler.jsonc:
```
{
	"name": "my-worker",
	"kv_namespaces": [
		{
			"binding": "SHARED_KV",
			"id": "abc123",
		},
	],
	"env": {
		"staging": {
			"kv_namespaces": [
				{ "binding": "SHARED_KV", "id": "staging-kv" },
				{ "binding": "STAGING_CACHE", "id": "staging-cache" },
			],
		},
	},
}
```
Running wrangler types will generate:
```
declare namespace Cloudflare {
	interface StagingEnv {
		SHARED_KV: KVNamespace;
		STAGING_CACHE: KVNamespace;
	}
	interface Env {
		SHARED_KV: KVNamespace; // Required: in all environments
		STAGING_CACHE?: KVNamespace; // Optional: only in staging
	}
}
interface Env extends Cloudflare.Env {}
```

Patch Changes

#12030 614bbd7 Thanks @jbwcloudflare! - Fix wrangler pages project validate to respect file count limits from CF_PAGES_UPLOAD_JWT
#11993 788bf78 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260116.0 1.20260120.0
#12039 1375577 Thanks @dimitropoulos! - Fixed the flag casing for the time period flag for the d1 insights command.
#12026 c3407ad Thanks @dario-piotrowicz! - Fix wrangler setup not automatically selecting workers as the target for new SvelteKit apps

The Sveltekit adapter:cloudflare adapter now accepts two different targets workers or pages. Since the wrangler auto configuration only targets workers, wrangler should instruct the adapter to use the workers variant. (The auto configuration process would in any case not work if the user were to target pages.)
Updated dependencies [788bf78, ae108f0]:
- miniflare@4.20260120.0
- @cloudflare/unenv-preset@2.11.0
- @cloudflare/kv-asset-handler@0.4.2

`v4.59.3`

Compare Source

Patch Changes

#9396 75386b1 Thanks @gnekich! - Fix wrangler login with custom callback-host/callback-port

The Cloudflare OAuth API always requires the redirect_uri to be localhost:8976. However, sometimes the Wrangler OAuth server needed to listen on a different host/port, for example when running from inside a container. We were previously incorrectly setting the redirect_uri to the configured callback host/port, but it needs to be up to the user to map localhost:8976 to the Wrangler OAuth server in the container.

Example:

You might run Wrangler inside a docker container like this: docker run -p 8989:8976 <image>, which forwards port 8976 on your host to 8989 inside the container.

Then inside the container, run wrangler login --callback-host=0.0.0.0 --callback-port=8989

The OAuth link still has a redirect_uri set tolocalhost:8976. For example https://dash.cloudflare.com/oauth2/auth?...&redirect_uri=http%3A%2F%2Flocalhost%3A8976%2Foauth%2Fcallback&...

However the redirect to localhost:8976 is then forwarded to the Wrangler OAuth server inside your container, allowing the login to complete.
#11925 8e4a0e5 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260114.0 1.20260115.0
#11942 133bf95 Thanks @penalosa! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260115.0 1.20260116.0
#11922 93d8d78 Thanks @dario-piotrowicz! - Improve telemetry errors being sent to Sentry by wrangler init when it delegates to C3 by ensuring that they contain the output of the C3 execution.
#11940 69ff962 Thanks @penalosa! - Show helpful messages for file not found errors (ENOENT)

When users encounter file not found errors, Wrangler now displays a helpful message with the missing file path and common causes, instead of reporting to Sentry.
#11904 22727c2 Thanks @danielrs! - Fix false positive infinite loop detection for exact path redirects

Fixed an issue where the redirect validation incorrectly flagged exact path redirects like / /index.html 200 as infinite loops. This was particularly problematic when html_handling is set to "none", where such redirects are valid.

The fix makes the validation more specific to only block wildcard patterns (like /* /index.html) that would actually cause infinite loops, while allowing exact path matches that are valid in certain configurations.

Fixes: #11824
#11946 fa39a73 Thanks @MattieTK! - Fix configFileName returning wrong filename for .jsonc config files

Previously, users with a wrangler.jsonc config file would see error messages and hints referring to wrangler.json instead of wrangler.jsonc. This was because the configFormat function collapsed both .json and .jsonc files into a single "jsonc" value, losing the distinction between them.

Now configFormat returns "json" for .json files and "jsonc" for .jsonc files, allowing configFileName to return the correct filename for each format.
#11968 4ac7c82 Thanks @MattieTK! - fix: include version components in command event metrics

Adds wranglerMajorVersion, wranglerMinorVersion, and wranglerPatchVersion to command events (wrangler command started, wrangler command completed, wrangler command errored). These properties were previously only included in adhoc events.
#11940 69ff962 Thanks @penalosa! - Improve error message when creating duplicate KV namespace

When attempting to create a KV namespace with a title that already exists, Wrangler now provides a clear, user-friendly error message instead of the generic API error. The new message explains that the namespace already exists and suggests running wrangler kv namespace list to see existing namespaces with their IDs, or choosing a different namespace name.
#11962 029531a Thanks @dario-piotrowicz! - Cache chosen account in memory to avoid repeated prompts

When users have multiple accounts and no node_modules directory exists for file caching, Wrangler (run via npx and equivalent commands) would prompt for account selection multiple times during a single command. Now the selected account is also stored in process memory, preventing duplicate prompts and potential issues from inconsistent account choices.
#11964 d58fbd1 Thanks @dario-piotrowicz! - Make name the positional argument for wrangler delete instead of script

The script argument was meaningless for the delete command since it deletes by worker name, not by entry point path. The name argument is now accepted as a positional argument, allowing users to run wrangler delete my-worker instead of wrangler delete --name my-worker. The script argument is now hidden but still accepted for backwards compatibility.
#11967 202c59e Thanks @emily-shen! - chore: update undici

The following dependency versions have been updated:

Dependency From To

undici 7.14.0 7.18.2
#11940 69ff962 Thanks @penalosa! - Improve error handling for Vite config transformations

Replace assertions with proper error handling when transforming Vite configs. When Wrangler encounters a Vite config that uses a function or lacks a plugins array, it now provides clear, actionable error messages instead of crashing with assertion failures. The check function gracefully skips incompatible configs with debug logging.
Updated dependencies [8e4a0e5, 133bf95, 202c59e, 133bf95, 25e2c60]:
- miniflare@4.20260116.0

`v4.59.2`

Compare Source

Patch Changes

#11908 e78186d Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260111.0 1.20260114.0
#11880 fe4faa3 Thanks @penalosa! - Show helpful messages for errors outside of Wrangler's control. This prevents unnecessary Sentry reports.

Errors now handled with user-friendly messages:
- Connection timeouts to Cloudflare's API (UND_ERR_CONNECT_TIMEOUT) - typically due to slow networks or connectivity issues
- File system permission errors (EPERM, EACCES) - caused by insufficient permissions, locked files, or antivirus software
- DNS resolution failures (ENOTFOUND) - caused by network connectivity issues or DNS configuration problems
#11882 695b043 Thanks @GregBrimble! - Improve the error message for wrangler secret put when using Worker versions or gradual deployments. wrangler versions secret put should be used instead, or ensure to deploy the latest version before using wrangler secret put. wrangler secret put alone will add the new secret to the latest version (possibly undeployed) and immediately deploy that which is usually not intended.
Updated dependencies [e78186d, fec8f5b, d39777f, 4714ca1, [c17e971](https://redirect.github.com/cloudflare/workers-sdk/commit/c17e971af01a9bcead0aca409666e294

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

cloudflare-workers-and-pages · 2025-03-13T14:51:24Z

Deploying clock with Cloudflare Pages

Latest commit:	`10da0a3`
Status:	🚫 Build failed.

View logs

renovate bot force-pushed the renovate/wrangler-4.x branch 10 times, most recently from f95ddfa to bc2545f Compare March 20, 2025 02:16

renovate bot force-pushed the renovate/wrangler-4.x branch 9 times, most recently from 127df67 to a7f82e0 Compare March 28, 2025 03:24

renovate bot force-pushed the renovate/wrangler-4.x branch 10 times, most recently from 8e9b8f5 to 5542081 Compare April 4, 2025 21:44

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 2208a0e to b020d32 Compare November 26, 2025 15:47

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 079f161 to d0c5581 Compare December 5, 2025 03:02

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 49e7f4d to 1359727 Compare December 16, 2025 13:06

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from c4f82ff to 40ad82a Compare December 24, 2025 16:31

renovate bot force-pushed the renovate/wrangler-4.x branch 10 times, most recently from 43fbcaf to 0931c6f Compare January 7, 2026 13:10

renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 9bce742 to 198709a Compare January 13, 2026 17:50

renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from d0ef9c8 to 81aacaa Compare January 22, 2026 12:37

renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 3d9e29a to 6633343 Compare February 3, 2026 12:45

renovate bot force-pushed the renovate/wrangler-4.x branch from 6633343 to e036333 Compare February 5, 2026 13:29

chore(deps): update dependency wrangler to v4

10da0a3

renovate bot force-pushed the renovate/wrangler-4.x branch from e036333 to 10da0a3 Compare February 10, 2026 10:26

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency wrangler to v4 #201

chore(deps): update dependency wrangler to v4 #201

Uh oh!

renovate bot commented Mar 13, 2025 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages bot commented Mar 13, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

chore(deps): update dependency wrangler to v4 #201

Are you sure you want to change the base?

chore(deps): update dependency wrangler to v4 #201

Uh oh!

Conversation

renovate bot commented Mar 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

cloudflare-workers-and-pages bot commented Mar 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Deploying clock with Cloudflare Pages

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Mar 13, 2025 •

edited

Loading

cloudflare-workers-and-pages bot commented Mar 13, 2025 •

edited

Loading