Update dependency wrangler to 4.65.x #12

renovate · 2025-07-03T11:44:39Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	`4.22.x` → `4.65.x`

Release Notes

cloudflare/workers-sdk (wrangler)

`v4.65.0`

Compare Source

Minor Changes

#12473 b900c5a Thanks @petebacondarwin! - Add CF_PAGES environment variables to wrangler pages dev

wrangler pages dev now automatically injects Pages-specific environment variables (CF_PAGES, CF_PAGES_BRANCH, CF_PAGES_COMMIT_SHA, CF_PAGES_URL) for improved dev/prod parity. This enables frameworks like SvelteKit to auto-detect the Pages environment during local development.
- CF_PAGES is set to "1" to indicate the Pages environment
- CF_PAGES_BRANCH defaults to the current git branch (or "local" if not in a git repo)
- CF_PAGES_COMMIT_SHA defaults to the current git commit SHA (or a placeholder if not in a git repo)
- CF_PAGES_URL is set to a simulated commit preview URL (e.g., https://<sha>.<project-name>.pages.dev)
These variables are displayed with their actual values in the bindings table during startup, making it easy to verify what branch and commit SHA were detected.

These variables can be overridden by user-defined vars in the Wrangler configuration, .env, .dev.vars, or via CLI flags.
#12464 10a1c4a Thanks @petebacondarwin! - Allow deleting KV namespaces by name

You can now delete a KV namespace by providing its name as a positional argument:
```
wrangler kv namespace delete my-namespace
```
This aligns the delete command with the create command, which also accepts a namespace name.
The existing --namespace-id and --binding flags continue to work as before.
#12382 d7b492c Thanks @dario-piotrowicz! - Add Pages detection to autoconfig flows

When running the autoconfig logic (via wrangler setup, wrangler deploy --x-autoconfig, or the programmatic autoconfig API), Wrangler now detects when a project appears to be a Pages project and handles it appropriately:
- For wrangler deploy, it warns the user but still allows them to proceed
- For wrangler setup and the programmatic autoconfig API, it throws a fatal error
#12461 8809411 Thanks @penalosa! - Support type: inherit bindings when using startWorker()

This is an internal binding type that should not be used by external users of the API
#12515 1a9eddd Thanks @ascorbic! - Add --json flag to wrangler whoami for machine-readable output

wrangler whoami --json now outputs structured JSON containing authentication status, auth type, email, accounts, and token permissions. When the user is not authenticated, the command exits with a non-zero status code and outputs {"loggedIn":false}, making it easy to check auth status in shell scripts without parsing text output.
```
# Parse the JSON output
wrangler whoami --json | jq '.accounts'

# Check if authenticated in a script. Returns 0 if authenticated, non-zero if not.
if wrangler whoami --json > /dev/null 2>&1; then
  echo "Authenticated"
else
  echo "Not authenticated"
fi
```

Patch Changes

#12437 ad817dd Thanks @MattieTK! - fix: use project's package manager in wranger autoconfig

wrangler setup now correctly detects and uses the project's package manager based on lockfiles (pnpm-lock.yaml, yarn.lock, bun.lockb, package-lock.json) and the packageManager field in package.json. Previously, it would fall back to the package manager used to execute the command when run directly from the terminal, causing failures in pnpm and yarn workspace projects if the wrong manager was used in this step due to the workspace: protocol not being supported by npm.

This change leverages the package manager detection already performed by @netlify/build-info during framework detection, ensuring consistent behaviour across the autoconfig process.
#12541 f7fa326 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

Dependency From To

workerd 1.20260210.0 1.20260212.0
#12498 734792a Thanks @dario-piotrowicz! - Fix: make sure that remote proxy sessions's logs can be silenced when the wrangler log level is set to "none"
#12135 cc5ac22 Thanks @edmundhung! - Fix spurious config diffs when bindings from local and remote config are shown in different order

When comparing local and remote Worker configurations, binding arrays like kv_namespaces would incorrectly show additions and removals if the elements were in a different order. The diff now correctly recognizes these as equivalent by reordering remote arrays to match the local config's order before comparison.
#12476 62a8d48 Thanks @MattieTK! - fix: use unscoped binary name for OpenNext autoconfig command overrides

The build, deploy, and version command overrides in the Next.js (OpenNext) autoconfig handler used the scoped package name @opennextjs/cloudflare, which pnpm interprets as a workspace filter rather than a binary name. This caused wrangler deploy --x-autoconfig to fail for pnpm-based Next.js projects with ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL. Changed to use the unscoped binary name opennextjs-cloudflare, which resolves correctly across all package managers.
#12516 84252b7 Thanks @edmundhung! - Stop proxying localhost requests when proxy environment variables are set

When HTTP_PROXY or HTTPS_PROXY is configured, all fetch requests including ones to localhost were routed through the proxy. This caused wrangler dev and the Vite plugin to fail with "TypeError: fetch failed" because the proxy can't reach local addresses.

This switches from ProxyAgent to undici's EnvHttpProxyAgent, which supports the NO_PROXY environment variable. When NO_PROXY is not set, it defaults to localhost,127.0.0.1,::1 so local requests are never proxied.

The NO_PROXY config only applies to the request destination, not the proxy server address. So a proxy running on localhost (e.g. HTTP_PROXY=http://127.0.0.1:11451) still works for outbound API calls.
#12506 e5efa5d Thanks @sesteves! - Fix wrangler r2 sql query displaying [object Object] for nested values

SQL functions that return complex types such as arrays of objects (e.g. approx_top_k) were rendered as [object Object] in the table output because String() was called directly on non-primitive values. These values are now serialized with JSON.stringify so they display as readable JSON strings.
#11725 be9745f Thanks @dario-piotrowicz! - Fix incorrect logic during autoconfiguration (when running wrangler setup or wrangler deploy --x-autoconfig) that caused parts of the project's package.json file, removed during the process, to incorrectly be added back
#12458 122791d Thanks @jkoe-cf! - Remove default values for delivery delay and message retention and update messaging on limits

Fixes the issue of the default maximum message retention (365400 seconds) being longer than the maximum allowed retention period for free tier users (86400 seconds).

Previous:
- Wrangler set a default value of 365400 seconds max message retention if the setting was not explicitly provided in the Wrangler configuration.
- The maximum retention period was documented as 1209600 seconds for all queues users because it was required to be on paid tier.
- Wrangler also set a default value of 0 seconds for delivery delay if the setting was not explicitly provided in the Wrangler configuration.
Updated:
- Wrangler no longer sets a default value for max message retention so that the default can be applied at the API.
- The maximum retention period is now documented as 86400 seconds for free tier queues and 1209600 seconds for paid tier queues
- Wrangler also no longer sets a default value for delivery delay so that the default can be applied at the API.
#12513 41e18aa Thanks @pombosilva! - Add confirmation prompt when deploying workflows with names that belong to different workers.

When deploying a workflow with a name that already exists and is currently associated with a different worker script, Wrangler will now display a warning and prompt for confirmation before proceeding. This helps prevent accidentally overriding workflows.

In non-interactive environments this check is skipped by default. Use the --strict flag to enable the check in non-interactive environments, which will cause the deployment to fail if workflow conflicts are detected.
Updated dependencies [f7fa326, 7aaa2a5, d06ad09]:
- miniflare@4.20260212.0

`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
- [@&

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.

This change is

coderabbitai · 2025-07-03T11:44:46Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🔍 Trigger a full review

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

cloudflare-workers-and-pages · 2025-07-03T11:44:56Z

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	web4	`20f7065`	Feb 12 2026, 05:02 PM

guardrails · 2025-07-03T11:45:09Z

⚠️ We detected 1 security issue in this pull request:

Vulnerable Libraries (1)

Severity	Details
High	pkg:npm/wrangler@4.22.0 (t) upgrade to: 3.114.17,4.59.1

More info on how to fix Vulnerable Libraries in JavaScript.

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

openzeppelin-code · 2025-07-03T11:45:58Z

Update dependency wrangler to 4.57.x

Generated at commit: 83249a8876e35c5238d8f2b17fa6dc4bad4ee53e

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	0 0 0 0 0 0
Dependencies	Critical High Medium Low Note Total	0 0 0 0 0 0

For more details view the full report in OpenZeppelin Code Inspector

package-lock.json

          "optional": true
        }
      }
    },


sonarqubecloud · 2026-02-12T16:58:39Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

renovate bot force-pushed the renovate/wrangler-4.x branch from 261ec83 to e4dcc0b Compare July 8, 2025 17:59

renovate bot changed the title ~~Update dependency wrangler to 4.23.x~~ Update dependency wrangler to 4.24.x Jul 8, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from e4dcc0b to 1596a40 Compare July 17, 2025 12:36

renovate bot changed the title ~~Update dependency wrangler to 4.24.x~~ Update dependency wrangler to 4.25.x Jul 17, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from c9e1fc1 to 10ed3af Compare July 24, 2025 13:53

renovate bot changed the title ~~Update dependency wrangler to 4.25.x~~ Update dependency wrangler to 4.26.x Jul 24, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from e1a02df to 9375a68 Compare July 31, 2025 17:52

renovate bot changed the title ~~Update dependency wrangler to 4.26.x~~ Update dependency wrangler to 4.27.x Jul 31, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 9375a68 to a550bb8 Compare August 5, 2025 10:10

renovate bot changed the title ~~Update dependency wrangler to 4.27.x~~ Update dependency wrangler to 4.28.x Aug 5, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 87cd22c to c2650d1 Compare August 12, 2025 19:31

renovate bot changed the title ~~Update dependency wrangler to 4.28.x~~ Update dependency wrangler to 4.29.x Aug 12, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 503ab4a to 81a9a33 Compare August 14, 2025 18:47

renovate bot changed the title ~~Update dependency wrangler to 4.29.x~~ Update dependency wrangler to 4.30.x Aug 14, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 81a9a33 to bc98d71 Compare August 18, 2025 19:31

renovate bot changed the title ~~Update dependency wrangler to 4.30.x~~ Update dependency wrangler to 4.31.x Aug 18, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from bc98d71 to 1697e9e Compare August 21, 2025 19:23

renovate bot changed the title ~~Update dependency wrangler to 4.31.x~~ Update dependency wrangler to 4.32.x Aug 21, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 1697e9e to 02ef45e Compare August 26, 2025 18:15

renovate bot changed the title ~~Update dependency wrangler to 4.32.x~~ Update dependency wrangler to 4.33.x Aug 26, 2025

renovate bot changed the title ~~Update dependency wrangler to 4.54.x~~ Update dependency wrangler to 4.55.x Dec 16, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 9fe542e to 951d31b Compare December 18, 2025 14:07

renovate bot changed the title ~~Update dependency wrangler to 4.55.x~~ Update dependency wrangler to 4.56.x Dec 18, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 951d31b to 70594da Compare December 24, 2025 17:42

renovate bot changed the title ~~Update dependency wrangler to 4.56.x~~ Update dependency wrangler to 4.54.x Dec 24, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 70594da to 4215fe9 Compare December 31, 2025 13:36

renovate bot force-pushed the renovate/wrangler-4.x branch from 4215fe9 to 0c5d211 Compare January 7, 2026 14:11

renovate bot changed the title ~~Update dependency wrangler to 4.54.x~~ Update dependency wrangler to 4.57.x Jan 7, 2026

sentry bot reviewed Jan 7, 2026

View reviewed changes

package-lock.json

"optional": true

}

}

},

This comment was marked as outdated.

Sign in to view

renovate bot force-pushed the renovate/wrangler-4.x branch from 0c5d211 to 83249a8 Compare January 8, 2026 13:54

renovate bot changed the title ~~Update dependency wrangler to 4.57.x~~ Update dependency wrangler to 4.58.x Jan 8, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 83249a8 to b99a917 Compare January 13, 2026 16:53

renovate bot changed the title ~~Update dependency wrangler to 4.58.x~~ Update dependency wrangler to 4.59.x Jan 13, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch 3 times, most recently from 8b9cabb to 735ddc9 Compare January 22, 2026 13:47

renovate bot changed the title ~~Update dependency wrangler to 4.59.x~~ Update dependency wrangler to 4.60.x Jan 22, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 735ddc9 to 8fc8707 Compare January 27, 2026 13:08

renovate bot changed the title ~~Update dependency wrangler to 4.60.x~~ Update dependency wrangler to 4.61.x Jan 27, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 1d9b508 to 3bcda36 Compare February 3, 2026 14:30

renovate bot changed the title ~~Update dependency wrangler to 4.61.x~~ Update dependency wrangler to 4.62.x Feb 3, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 3bcda36 to 88e2a61 Compare February 5, 2026 15:03

renovate bot changed the title ~~Update dependency wrangler to 4.62.x~~ Update dependency wrangler to 4.63.x Feb 5, 2026

renovate bot force-pushed the renovate/wrangler-4.x branch from 88e2a61 to bb8100e Compare February 10, 2026 13:09

renovate bot changed the title ~~Update dependency wrangler to 4.63.x~~ Update dependency wrangler to 4.64.x Feb 10, 2026

Update dependency wrangler to 4.65.x

20f7065

renovate bot force-pushed the renovate/wrangler-4.x branch from bb8100e to 20f7065 Compare February 12, 2026 16:58

renovate bot changed the title ~~Update dependency wrangler to 4.64.x~~ Update dependency wrangler to 4.65.x Feb 12, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency wrangler to 4.65.x #12

Update dependency wrangler to 4.65.x #12

Uh oh!

renovate bot commented Jul 3, 2025 •

edited by BoomchainLabs

Loading

Uh oh!

coderabbitai bot commented Jul 3, 2025 •

edited

Loading

Review skipped

Uh oh!

cloudflare-workers-and-pages bot commented Jul 3, 2025 •

edited

Loading

Uh oh!

guardrails bot commented Jul 3, 2025 •

edited

Loading

Uh oh!

openzeppelin-code bot commented Jul 3, 2025 •

edited

Loading

Uh oh!

This comment was marked as outdated.

Uh oh!

sonarqubecloud bot commented Feb 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Update dependency wrangler to 4.65.x #12

Are you sure you want to change the base?

Update dependency wrangler to 4.65.x #12

Uh oh!

Conversation

renovate bot commented Jul 3, 2025 • edited by BoomchainLabs Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v4.65.0

Minor Changes

Patch Changes

v4.64.0

Minor Changes

Patch Changes

v4.63.0

Minor Changes

Patch Changes

v4.62.0

Minor Changes

Patch Changes

v4.61.1

Patch Changes

v4.61.0

Minor Changes

Patch Changes

v4.60.0

Minor Changes

Patch Changes

Configuration

Uh oh!

coderabbitai bot commented Jul 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

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

Uh oh!

Deploying with Cloudflare Workers

Uh oh!

guardrails bot commented Jul 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openzeppelin-code bot commented Jul 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Update dependency wrangler to 4.57.x

🚨 Report Summary

Uh oh!

This comment was marked as outdated.

Uh oh!

sonarqubecloud bot commented Feb 12, 2026

Quality Gate passed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Jul 3, 2025 •

edited by BoomchainLabs

Loading

`v4.65.0`

`v4.64.0`

`v4.63.0`

`v4.62.0`

`v4.61.1`

`v4.61.0`

`v4.60.0`

coderabbitai bot commented Jul 3, 2025 •

edited

Loading

cloudflare-workers-and-pages bot commented Jul 3, 2025 •

edited

Loading

guardrails bot commented Jul 3, 2025 •

edited

Loading

openzeppelin-code bot commented Jul 3, 2025 •

edited

Loading