chore(deps): update dependency wrangler to v4.53.0 #39

renovate · 2025-07-08T15:41:49Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
wrangler (source)	`4.23.0` -> `4.53.0`

Release Notes

cloudflare/workers-sdk (wrangler)

`v4.53.0`

Compare Source

Minor Changes

#11500 af54c63 Thanks @dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

Note: the field is experimental and could change while autoconfig is not GA
#11477 9988cc9 Thanks @ascorbic! - Support Nuxt in autoconfig
#11472 ce295bf Thanks @dario-piotrowicz! - Support Qwik projects in autoconfig
#10937 9514c9a Thanks @ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:
- region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
- host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
- hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource
These fields are mutually exclusive - only one can be specified at a time.

Example configuration:
```
[placement]
host = "example.com:8123"
```
#11498 ac861f8 Thanks @penalosa! - Add React Router support in autoconfig
#11506 79d30d4 Thanks @vicb! - Set the target JS version to ES2024

Patch Changes

#11393 45480b1 Thanks @alsuren! - improved --help text for wrangler d1 subcommands
#11523 94c67e8 Thanks @jamesopstad! - fix: types from @cloudflare/workers-utils not being exported correctly from Wrangler
#11483 f550b62 Thanks @edmundhung! - stop running npm install with --legacy-peer-deps flag when setting up a project
Updated dependencies [819e287, 56e78c8, 0aa959a]:
- @cloudflare/unenv-preset@2.7.13
- miniflare@4.20251202.1

`v4.52.1`

Compare Source

Patch Changes

#11504 7e80340 Thanks @dario-piotrowicz! - Fix wrangler deploy failing for new workers containing environment variables or bindings
Updated dependencies [59534ba]:
- miniflare@4.20251202.0

`v4.52.0`

Compare Source

Minor Changes

#11416 abe49d8 Thanks @dario-piotrowicz! - Remove the wrangler deploy's --x-remote-diff-check experimental flag

The remote diffing feature has been enabled by default for a while and its functionality is stable, as a result the experimental flag (only available for option-out of the feature right now) has been removed.
#11408 f29e699 Thanks @ascorbic! - Export unstable helpers useful for generating wrangler config
#11389 2342d2f Thanks @dario-piotrowicz! - Improve the wrangler deploy flow to also check for potential overrides of secrets.

Now when you run wrangler deploy Wrangler will check the remote secrets for your workers for conflicts with the names of the bindings you're about to deploy. If there are conflicts, Wrangler will warn you and ask you for your permission before proceeding.
#11375 9a1de61 Thanks @penalosa! - Support TanStack Start in autoconfig
#11360 6b38532 Thanks @emily-shen! - Containers: Allow users to directly authenticate external image registries in local dev

Previously, we always queried the API for stored registry credentials and used those to pull images. This means that if you are using an external registry (ECR, dockerhub) then you have to configure registry credentials remotely before running local dev.

Now you can directly authenticate with your external registry provider (using docker login etc.), and Wrangler or Vite will be able to pull the image specified in the containers.image field in your config file.

The Cloudflare-managed registry (registry.cloudflare.com) currently still does not work with the Vite plugin.
#11009 e4ddbc2 Thanks @dario-piotrowicz! - Allow users to provide an account_id as part of the WorkerConfigObject they pass to maybeStartOrUpdateRemoteProxySession
#11478 2aec2b4 Thanks @dario-piotrowicz! - Support SolidStart in autoconfig
#11330 5a873bb Thanks @dario-piotrowicz! - Support Angular projects in autoconfig
#11449 e7b690b Thanks @penalosa! - Delegate generation of HTTPS certificates to Miniflare
#11448 2b4813b Thanks @edmundhung! - Bumps esbuild version to 0.27.0
#11335 c47ad11 Thanks @dario-piotrowicz! - Support internal-only undocumented cross_account_grant service binding property
#11346 a977701 Thanks @penalosa! - We're soon going to make backend changes that mean that wrangler dev --remote sessions will no longer have an associated inspector connection. In advance of these backend changes, we've enabled a new wrangler tail-based logging strategy for wrangler dev --remote. For now, you can revert to the previous logging strategy with wrangler dev --remote --no-x-tail-logs, but in future it will not be possible to revert.

The impact of this will be that logs that were previously available via devtools will now be provided directly to the Wrangler console and it will no longer be possible to interact with the remote Worker via the devtools console.

Patch Changes

#11397 b154de2 Thanks @vicb! - Use more workerd native modules

Node modules punycode, trace_events, cluster, wasi, and domains will be used when enabled
via a compatibility flag or by default when the compatibility date is greater or equal to 2025-12-04.
#11452 76f0540 Thanks @penalosa! - Remove uses of eval() from the Wrangler bundle
#11284 695fa25 Thanks @dom96! - Removes duplicate module warnings when vendoring Python packages
#11249 504e258 Thanks @dario-piotrowicz! - fix: Generalize autoconfig wording

Generalize the autoconfig wording so that when it doesn't specifically mention "deployment" (since it can be run via wrangler setup or the autoconfig programmatic API)

#11455 d25f7e2 Thanks @dario-piotrowicz! - Fix autoconfig using absolute paths for static projects

Running the experimental autoconfig logic through wrangler setup and wrangler deploy --x-autoconfig on a static project results in absolute paths being used. This is incorrect, especially when such paths are being included in the generated wrangler.jsonc. The changes here fix the autoconfig logic to use paths relative to the project's root instead.

For example given a project located in /Users/usr/projects/sites/my-static-site, before:

// wrangler.jsonc at /Users/usr/projects/sites/my-static-site
  {
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "static",
    "compatibility_date": "2025-11-27",
    "observability": {
      "enabled": true
    },
    "assets": {
      "directory": "/Users/usr/projects/sites/my-static-site/public"
    }
  }

and after:

// wrangler.jsonc at /Users/usr/projects/sites/my-static-site
  {
    "$schema": "node_modules/wrangler/config-schema.json",
    "name": "static",
    "compatibility_date": "2025-11-27",
    "observability": {
      "enabled": true
    },
    "assets": {
      "directory": "public"
    }
  }

#11484 1cfae2d Thanks @edmundhung! - Explicitly close FileHandle in wrangler d1 execute to support Node 25
#11383 1d685cb Thanks @dario-piotrowicz! - Fix: ensure that when a remote proxy session creation fails a hard error is surfaced to the user (both in wrangler dev and in the programmatic API).

When using remote bindings, either with wrangler dev or via startRemoteProxySession/maybeStartOrUpdateRemoteProxySession the remote proxy session necessary to connect to the remote resources can fail to be created, this might happen if for example you try to set a binding with some invalid values such as:
```
MY_R2: {
	type: "r2_bucket",
	bucket_name: "non-existent", // No bucket called "non-existent" exists
	remote: true,
},
```
Before this could go undetected and cause unwanted behaviors such as requests handling hanging indefinitely, now wrangler will instead crash (or throw a hard error ion the programmatic API), clearly indicating that something went wrong during the remote session's creation.
#11366 edf896d Thanks @ascorbic! - Use correctly-formatted names when displaying detected framework details
#11461 9eaa9e2 Thanks @dario-piotrowicz! - Update the structure of the configure method of autoconfig frameworks

Update the signature of the configure function of autoconfig frameworks (AutoconfigDetails#Framework), before they would return a RawConfig object to use to update the project's wrangler config file, now they return an object that includes the RawConfig and that can potentially also hold additional data relevant to the configuration.
Updated dependencies [2b4813b, b154de2, 5ee3780, 6e63b57, 71ab562, 5e937c1]:
- miniflare@4.20251128.0
- @cloudflare/unenv-preset@2.7.12

`v4.51.0`

Compare Source

Minor Changes

#11345 d524e55 Thanks @penalosa! - Enable experimental support for autoconfig-powered Astro projects
#11228 43903a3 Thanks @petebacondarwin! - Support CLOUDFLARE_ENV environment variable for selecting the active environment

This change enables users to select the environment for commands such as CLOUDFLARE_ENV=prod wrangler versions upload. The --env command line argument takes precedence.

The CLOUDFLARE_ENV environment variable is mostly used with the @cloudflare/vite-plugin to select the environment for building the Worker to be deployed. This build also generates a "redirected deploy config" that is flattened to only contain the active environment.
To avoid accidentally deploying a version that is built for one environment to a different environment, there is an additional check to ensure that if the user specifies an environment in Wrangler it matches the original selected environment from the build.

Patch Changes

#11367 e496280 Thanks @vicb! - Rate limit r2 bulk put
Updated dependencies [4d61fae, 69f4dc3, 1133c4d, 4d61fae]:
- @cloudflare/kv-asset-handler@0.4.1
- miniflare@4.20251125.0

`v4.50.0`

Compare Source

Minor Changes

#11219 524a6e5 Thanks @Ltadrian! - Implement Hyperdrive binding TLS miniflare proxy. This will allow for wrangler dev hyperdrive bindings to connect to external
databases that require TLS.
#11233 c922a81 Thanks @emily-shen! - Add containers.unsafe to allow internal users to use additional container features

Patch Changes

#11353 0cf696d Thanks @vicb! - Use the native node:domain module when available

It is enabled when the enable_nodejs_domain_module compatibility flag is set.
#11328 bb44120 Thanks @ascorbic! - Fixes a bug that caused wrangler deploy to hang when deploying SvelteKit sites with experimental autoconfig
#11025 4a158e9 Thanks @devin-ai-integration! - Use the native node:wasi module when available

It is enabled when the enable_nodejs_wasi_module compatibility flag is set.
Updated dependencies [0cf696d, 524a6e5, 4a158e9]:
- @cloudflare/unenv-preset@2.7.11
- miniflare@4.20251118.1

`v4.49.1`

Compare Source

Patch Changes

#11344 c758809 Thanks @dario-piotrowicz! - Fix: mark the r2 bulk command as hidden and experimental
#11339 dfba912 Thanks @dario-piotrowicz! - Fix wrangler deploy erroring when it pulls down remote configs of workers containing an assets binding
Updated dependencies [e5ec8cf]:
- miniflare@4.20251118.0

`v4.49.0`

Compare Source

Minor Changes

#10703 c5c4ee5 Thanks @danlapid! - Add support for streaming tail consumers in local dev. This is an experimental new feature that allows you to register a tailStream() handler (compared to the existing tail() handler), which will receive streamed tail events from your Worker (compared to the tail() handler, which only receives batched events after your Worker has finished processing).

#11251 7035804 Thanks @penalosa! - When the WRANGLER_HIDE_BANNER environment variable is provided, Wrangler will no longer display a version banner. This applies to all commands.

For instance, previously running wrangler docs would give the following output:

> wrangler docs
 ⛅️ wrangler 4.47.0
───────────────────
Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/

With WRANGLER_HIDE_BANNER, this is now:

> WRANGLER_HIDE_BANNER=true wrangler docs
Opening a link in your default browser: https://developers.cloudflare.com/workers/wrangler/commands/

#11285 d014fa7 Thanks @vicb! - Implement the wrangler r2 bulk put bucket-name --filename list.json command.

The command uploads multiple objects to an R2 bucket.

The list of object is provided as a JSON encoded file via --filename. It is a list of key and file (respectively the name and the content for the object).
```
[
  { "key": "/path/to/obj", "file": "/path/to/file_1"},
  { "key": "/path/to/other/obj", "file": "/path/to/file_2"},
  // ...
]
```
Uploads are executed concurrently and the level of concurrency can be set via --concurrency.

The command supports the same options as wrangler r2 object put, minus --file, and --pipe and plus --concurrency
#11268 15b8460 Thanks @penalosa! - Support SvelteKit projects in autoconfig
#11258 2011b6a Thanks @dario-piotrowicz! - Add --dry-run flag to wrangler setup and also a dryRun option to runAutoConfig

Patch Changes

#11261 a352c7f Thanks @petebacondarwin! - Avoid using object lookup for OAuth Error classes
#11286 8e99766 Thanks @dario-piotrowicz! - fix: make sure that experimental_patchConfig doesn't throw if it encounters a null value
#11279 d0d3fe6 Thanks @vicb! - bump p-queue to ^9.0.0
#11278 92afbba Thanks @ascorbic! - Fixes a bug that caused .dev.vars to be ignored in OpenNext
#11244 65b4afe Thanks @petebacondarwin! - Internal refactoring to improve error traceability in wrangler dev
#11238 da8442f Thanks @jamesopstad! - Add unstable_getDurableObjectClassNameToUseSQLiteMap export. This is an internal function for use in the Vite plugin.
#11266 09cb720 Thanks @penalosa! - Use the smol-toml library for parsing TOML instead of @iarna/toml
#11236 793e2b4 Thanks @ascorbic! - Refresh expired preview tokens when running in remote dev mode
#11286 8e99766 Thanks @dario-piotrowicz! - fix: wrangler deploy failing to patch local wrangler.jsonc files if the remote tail_consumers value is null
#11275 9cbf126 Thanks @dario-piotrowicz! - Ensure that wrangler deploy run with a positional argument or with --assets does not trigger the autoconfig process (even with --experimental-autoconfig)
#11242 dd1e560 Thanks @dario-piotrowicz! - Fix: make sure that remote proxy sessions's debug logs are enabled when the wrangler log level is set to "debug"
Updated dependencies [c5c4ee5, d0041e2, 827d017]:
- miniflare@4.20251113.0

`v4.48.0`

Compare Source

Minor Changes

#11212 3908162 Thanks @dario-piotrowicz! - Add autoconfig changes summary for wrangler deploy --x-autoconfig with the option for users to cancel the operation
#11229 14d79f2 Thanks @dario-piotrowicz! - Enables experimental-deploy-remote-diff-check flag by default (the flag is still present for now so that users can turn it off if needed) and improves the remote config diffing logic (to include less noise in the diff presented to the user)
#11245 dfc6513 Thanks @vicb! - Change how Wrangler selects default ports for dev sessions.

If no port is specified, Wrangler now probes the default port and the 10 consecutive ports after it before falling back to a random port.
This will help getting a stable port number across dev sessions.
Both the http server and inspector ports are affected.

Patch Changes

#11177 43fe9f3 Thanks @MattieTK! - Added bun detection to package manager analytics
Updated dependencies [305ffb3, 46ccf0e]:
- miniflare@4.20251109.1

`v4.47.0`

Compare Source

Minor Changes

#11201 5286309 Thanks @avenceslau! - Add wrangler workflows instances restart command
#11214 5cf8a39 Thanks @penalosa! - Add the experimental wrangler setup command to run autoconfig outside of the deploy flow.
#11187 8abc789 Thanks @dario-piotrowicz! - Add possibility for users to edit their project settings during autoconfig

When running wrangler deploy --experimental-autoconfig, after the automatic project settings detection Wrangler will now present users the opportunity to customize the auto-detected project's settings

Patch Changes

#11143 2d16610 Thanks @FlorentCollin! - Improve the formatting of the D1 execute command to always show the duration in milliseconds with two decimal places.
#11178 63defa2 Thanks @ascorbic! - Log a more helpful error when attempting to "r2 object put" a non-existent file
#11199 70d3d4a Thanks @penalosa! - Add telemetry to autoconfig
#11186 38396ed Thanks @hoodmane! - Removed warning when deploying a Python worker
#11024 cdcecfc Thanks @devin-ai-integration! - Use the native node:trace_events module when available

It is enabled when the enable_nodejs_trace_events_module compatibility flag is set.
#11195 e85f965 Thanks @ascorbic! - Ignores .dev.vars if --env-file has been explicitly passed

Previously, .dev.vars would always be read first, and then any file passed with --env-file would override variables in .dev.vars. This meant there was no way to ignore .dev.vars if you wanted to use a different env file. Now, if --env-file is passed, .dev.vars will be ignored entirely.
#11181 88aa707 Thanks @petebacondarwin! - add more logging around Wrangler authentication to help diagnose issues
Updated dependencies [dd7d584, 4259256, cdcecfc]:
- miniflare@4.20251109.0
- @cloudflare/unenv-preset@2.7.10

`v4.46.0`

Compare Source

Minor Changes

#11183 240ebeb Thanks @dario-piotrowicz! - expose experimental_getDetailsForAutoConfig and experimental_runAutoConfig APIs that provide respectively the autoconfig detection and execution functionalities
#11180 53b0fce Thanks @penalosa! - Detect non-framework static sites
#11162 c3ed531 Thanks @dario-piotrowicz! - add a remoteBindings option to getPlatformProxy to allow the disabling of remote bindings
#11164 305d7bf Thanks @penalosa! - Implement experimental autoconfig flow for static sites
#10605 b55a3c7 Thanks @emily-shen! - Add command to configure credentials for non-Cloudflare container registries

Note this is a closed/experimental command that will not work without the appropriate account-level capabilities.
#11078 5d7c4c2 Thanks @simonha9! - Add jurisdiction support to d1 db creation via command-line argument

Patch Changes

#11160 05440a1 Thanks @dario-piotrowicz! - Allows auto-update of the local Wrangler configuration file to match remote configuration when running wrangler deploy --env <TARGET_ENV>

When running wrangler deploy, with --x-remote-diff-check and after cancelling the deployment due to destructive changes present in the local config file, Wrangler offers to update the Wrangler configuration file to match the remote configuration. This wasn't however enabled when a target environment was specified (via the --env|-e flag). Now this will also apply when an environment is targeted.
#11162 c3ed531 Thanks @dario-piotrowicz! - Update the description of the --local flag for the wrangler dev command to clarify that it disables remote bindings, also un-deprecate and un-hide it
#11162 c3ed531 Thanks @dario-piotrowicz! - Fix bindings with remote: true being logged as remote when run via wrangler dev --local
Updated dependencies [1ae020d]:
- miniflare@4.20251105.0

`v4.45.4`

Compare Source

Patch Changes

#11133 8ffbd17 Thanks @petebacondarwin! - Reduce the amount of arguments being passed in metrics capture.

Now the argument values that are captured come from an allow list,
and can be marked as ALLOW (capture the real value) or REDACT (capture as "").
#11033 77ed7e2 Thanks @dario-piotrowicz! - Offer to update the local Wrangler configuration file to match remote configuration when running wrangler deploy

When running wrangler deploy, with --x-remote-diff-check, Wrangler will display the difference between local and remote configuration.
If there would be a destructive change to the remote configuration, the user is given the option to cancel the deployment.
In the case where the user does cancel deployment, Wrangler will now also offer to update the local Wrangler configuration file to match the remote configuration.
#11139 bb00f9d Thanks @devin-ai-integration! - Updated cron trigger documentation links and improved error message to include instructions for testing cron triggers locally
#11135 ed666a1 Thanks @penalosa! - Implement tail-based logging for wrangler dev remote mode, behind the --x-tail-tags flag. This will become the default in the future.
#11149 22f25fd Thanks @penalosa! - Add no-op autoconfig logic behind an experimental flag
Updated dependencies [90a2566, 14f60e8]:
- @cloudflare/unenv-preset@2.7.9
- miniflare@4.20251011.2

`v4.45.3`

Patch Changes

#11117 6822aaf Thanks @emily-shen! - fix: show local/remote status before D1 command confirmations

D1 commands (execute, export, migrations apply, migrations list, delete, time-travel) now display whether they're running against local or remote databases before showing confirmation prompts. This prevents confusion about which database will be affected by the operation.
#11077 bce8142 Thanks @petebacondarwin! - Ensure that process.env is case-insensitive on Windows

The object that holds the environment variables in process.env does not care about the case of its keys
in Windows. For example, process.env.SystemRoot and process.env.SYSTEMROOT will refer to the same value.

Previously, when merging fields from .env files we were replacing this native object with a vanilla
JavaScript object, that is case-insensitive, and so sometimes environment variables appeared to be missing
when in reality they just had different casing.

`v4.45.2`

Patch Changes

#11097 55657eb Thanks @penalosa! - Extract internal APIs into a new @cloudflare/workers-utils package
#11118 d47f166 Thanks @zebp! - Fix validation of the persist field of observability logs and traces configuration

`v4.45.1`

Compare Source

Patch Changes

#10959 d0208fe Thanks @devin-ai-integration! - Fixed conflict between --env and --expires flags in wrangler r2 object put.

--e now aliases --env only, and NOT --expires.
#10915 dbe51c1 Thanks @devin-ai-integration! - Fixed self-bindings (service bindings to the same worker) showing as [not connected] in wrangler dev. Self-bindings now correctly show as [connected] since a worker is always available to itself.
#10913 d4f2daf Thanks @devin-ai-integration! - Fixed duplicate warning messages appearing during wrangler dev when configuration changes or state transitions occur

`v4.45.0`

Compare Source

Minor Changes

#11030 1a8088a Thanks @penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the --no-x-provision flag. It currently works for R2, D1, and KV bindings.

To use this feature, add a binding to your config file without a resource ID:
```
{
	"kv_namespaces": [{ "binding": "MY_KV" }],
	"d1_databases": [{ "binding": "MY_DB" }],
	"r2_buckets": [{ "binding": "MY_R2" }],
}
```
wrangler dev will automatically create these resources for you locally, and when you next run wrangler deploy Wrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.

Patch Changes

#11037 4bd4c29 Thanks @danielrs! - Better Wrangler subdomain defaults warning.

Improves the warnings that we show users when either worker_dev or preview_urls are missing.
#10927 31e1330 Thanks @dom96! - Implements python_modules.excludes wrangler config field
```
[python_modules]
excludes = ["**/*.pyc", "**/__pycache__"]
```
#10741 2f57345 Thanks @penalosa! - Remove obsolete --x-remote-bindings flag
Updated dependencies [ca6c010]:
- miniflare@4.20251011.1

`v4.44.0`

Compare Source

Minor Changes

#10939 d4b4c90 Thanks @danielrs! - Config preview_urls defaults to workers_dev value.

Originally, we were defaulting config.preview_urls to true, but we
were accidentally enabling Preview URLs for users that only had
config.workers_dev=false.

Then, we set the default value of config.preview_urls to false, but we
were accidentally disabling Preview URLs for users that only had
config.workers_dev=true.

Rather than defaulting config.preview_urls to true or false, we
default to the resolved value of config.workers_dev. Should result in a
clearer user experience.
#11027 1a2bbf8 Thanks @jamesopstad! - Statically replace the value of process.env.NODE_ENV with development for development builds and production for production builds if it is not set. Else, use the given value. This ensures that libraries, such as React, that branch code based on process.env.NODE_ENV can be properly tree shaken.

#9705 0ee1a68 Thanks @hiendv! - Add params type to Workflow type generation. E.g.

interface Env {
	MY_WORKFLOW: Workflow<
		Parameters<import("./src/index").MyWorkflow["run"]>[0]["payload"]
	>;
}

#10867 dd5f769 Thanks @austin-mc! - Add media binding support

Patch Changes

#11018 5124818 Thanks @dario-piotrowicz! - Improve potential errors thrown by startRemoteProxySession by including more information
#11019 [6643bd4](https://redirect.github.com/cloudflare/workers-sdk/commit/6643bd41a082f04778739b93a

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.

renovate bot force-pushed the renovate/wrangler-4.x branch from d955607 to 1538694 Compare July 10, 2025 21:45

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.24.0~~ chore(deps): update dependency wrangler to v4.24.3 Jul 10, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 4 times, most recently from 37844ac to 69ca6b9 Compare July 16, 2025 18:28

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.24.3~~ chore(deps): update dependency wrangler to v4.24.4 Jul 16, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 69ca6b9 to a7ed893 Compare July 17, 2025 10:29

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.24.4~~ chore(deps): update dependency wrangler to v4.25.0 Jul 17, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from a7ed893 to b47832e Compare July 22, 2025 15:59

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.25.0~~ chore(deps): update dependency wrangler to v4.25.1 Jul 22, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from b47832e to 2fa0943 Compare July 24, 2025 15:54

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.25.1~~ chore(deps): update dependency wrangler to v4.26.0 Jul 24, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 2fa0943 to caf7cef Compare July 29, 2025 12:50

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.26.0~~ chore(deps): update dependency wrangler to v4.26.1 Jul 29, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from caf7cef to 07f3659 Compare July 31, 2025 19:49

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.26.1~~ chore(deps): update dependency wrangler to v4.27.0 Jul 31, 2025

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.27.0~~ chore(deps): update dependency wrangler to v4.28.0 Aug 5, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from ab52ea0 to 5e323f2 Compare August 7, 2025 14:49

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.28.0~~ chore(deps): update dependency wrangler to v4.28.1 Aug 7, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 5e323f2 to 175b49e Compare August 12, 2025 19:47

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.28.1~~ chore(deps): update dependency wrangler to v4.29.0 Aug 12, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 175b49e to 3291083 Compare August 13, 2025 12:35

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.29.0~~ chore(deps): update dependency wrangler to v4.29.1 Aug 13, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 3291083 to 12a2810 Compare August 14, 2025 18:52

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.29.1~~ chore(deps): update dependency wrangler to v4.30.0 Aug 14, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 12a2810 to 30a2674 Compare August 18, 2025 19:51

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.30.0~~ chore(deps): update dependency wrangler to v4.31.0 Aug 18, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 30a2674 to 1cb40a1 Compare August 21, 2025 19:28

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.45.0~~ chore(deps): update dependency wrangler to v4.45.1 Oct 28, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from f3c8f60 to 9a5c13d Compare October 29, 2025 22:49

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.45.1~~ chore(deps): update dependency wrangler to v4.45.2 Oct 29, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 9a5c13d to 33d7a24 Compare October 31, 2025 05:03

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.45.2~~ chore(deps): update dependency wrangler to v4.45.3 Oct 31, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 33d7a24 to d433665 Compare November 4, 2025 18:52

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.45.3~~ chore(deps): update dependency wrangler to v4.45.4 Nov 4, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from d433665 to 5e82dfc Compare November 6, 2025 19:00

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.45.4~~ chore(deps): update dependency wrangler to v4.46.0 Nov 6, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 5e82dfc to 3e4c7b7 Compare November 11, 2025 21:37

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.46.0~~ chore(deps): update dependency wrangler to v4.47.0 Nov 11, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 3e4c7b7 to f57ecb3 Compare November 13, 2025 17:12

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.47.0~~ chore(deps): update dependency wrangler to v4.48.0 Nov 13, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from f57ecb3 to f5085d5 Compare November 14, 2025 20:57

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.48.0~~ chore(deps): update dependency wrangler to v4.47.0 Nov 14, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from f5085d5 to 24f188f Compare November 18, 2025 23:41

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.47.0~~ chore(deps): update dependency wrangler to v4.49.0 Nov 18, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 24f188f to 593cbe2 Compare November 20, 2025 10:51

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.49.0~~ chore(deps): update dependency wrangler to v4.49.1 Nov 20, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch from 593cbe2 to 9053d6c Compare November 20, 2025 22:56

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.49.1~~ chore(deps): update dependency wrangler to v4.50.0 Nov 20, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from ca4cb17 to e6cbcd5 Compare November 26, 2025 17:46

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.50.0~~ chore(deps): update dependency wrangler to v4.51.0 Nov 26, 2025

renovate bot force-pushed the renovate/wrangler-4.x branch 2 times, most recently from 4e5eaa7 to eee4ac5 Compare December 3, 2025 20:15

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.51.0~~ chore(deps): update dependency wrangler to v4.52.1 Dec 3, 2025

chore(deps): update dependency wrangler to v4.53.0

12acd64

renovate bot force-pushed the renovate/wrangler-4.x branch from eee4ac5 to 12acd64 Compare December 4, 2025 22:12

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.52.1~~ chore(deps): update dependency wrangler to v4.53.0 Dec 4, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency wrangler to v4.53.0 #39

chore(deps): update dependency wrangler to v4.53.0 #39

Uh oh!

renovate bot commented Jul 8, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps): update dependency wrangler to v4.53.0 #39

Are you sure you want to change the base?

chore(deps): update dependency wrangler to v4.53.0 #39

Uh oh!

Conversation

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

Uh oh!

Release Notes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Jul 8, 2025 •

edited

Loading