chore(deps): update dependency wrangler to v4.19.1 #1841

renovate · 2025-03-23T14:40:08Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wrangler (source)	`3.78.7` -> `4.19.1`
wrangler (source)	`4.1.0` -> `4.19.1`

Release Notes

cloudflare/workers-sdk (wrangler)

`v4.19.1`

Compare Source

Patch Changes

#9456 db2cdc6 Thanks @WillTaylorDev! - Fix bug causing preview alias to always be generated.

`v4.19.0`

Compare Source

Minor Changes

#9401 03b8c1c Thanks @WillTaylorDev! - Provide ability for Wrangler to upload preview aliases during version upload.

Patch Changes

#9390 80e75f4 Thanks @penalosa! - Support additional Mixed Mode resources in Wrangler:
- AI
- Browser
- Images
- Vectorize
- Dispatch Namespaces
#9395 b3be057 Thanks @Maximo-Guk! - Add WRANGLER_CI_OVERRIDE_NETWORK_MODE_HOST for Workers CI
#9410 87f3843 Thanks @dario-piotrowicz! - enable consumers of unstable_readConfig to silence remote warnings
Updated dependencies [8c7ce77, 80e75f4, 80e75f4, fac2f9d, 92719a5]:
- [email protected]

`v4.18.0`

Compare Source

Minor Changes

#9393 34b6174 Thanks @jamesopstad! - Hard fail on Node.js < 20. Wrangler no longer supports Node.js 18.x as it reached end-of-life on 2025-04-30. See https://github.com/nodejs/release?tab=readme-ov-file#end-of-life-releases.

Patch Changes

#9308 d3a6eb3 Thanks @dario-piotrowicz! - expose new utilities and types to aid consumers of the programmatic mixed-mode API

Specifically the exports have been added:
- Experimental_MixedModeSession: type representing a mixed-mode session
- Experimental_ConfigBindingsOptions: type representing config-bindings
- experimental_pickRemoteBindings: utility for picking only the remote bindings from a record of start-worker bindings.
- unstable_convertConfigBindingsToStartWorkerBindings: utility for converting config-bindings into start-worker bindings (that can be passed to startMixedModeSession)
#9347 b8f058c Thanks @penalosa! - Improve binding display on narrower terminals
Updated dependencies [d9d937a, e39a45f, fdae3f7]:
- [email protected]

`v4.17.0`

Compare Source

Minor Changes

#9321 6c03bde Thanks @petebacondarwin! - Add support for FedRAMP High compliance region

Now it is possible to target Wrangler at the FedRAMP High compliance region.
There are two ways to signal to Wrangler to run in this mode:
- set "compliance_region": "fedramp_high" in a Wrangler configuration
- set CLOUDFLARE_COMPLIANCE_REGION=fedramp_high environment variable when running Wrangler
If both are provided and the values do not match then Wrangler will exit with an error.

When in this mode OAuth authentication is not supported.
It is necessary to authenticate using a Cloudflare API Token acquired from the Cloudflare FedRAMP High dashboard.

Most bindings and commands are supported in this mode.
- Unsupported commands may result in API requests that are not supported - possibly 422 Unprocessable Entity responses.
- Unsupported bindings may work in local dev, as there is no local validation, but will fail at Worker deployment time.
Resolves DEVX-1921.
#9330 34c71ce Thanks @edmundhung! - Updated internal configuration to use Miniflare’s new defaultPersistRoot instead of per-plugin persist flags
#8973 cc7fae4 Thanks @Caio-Nogueira! - Show latest instance by default on workflows instances describe command

Patch Changes

#9335 6479fc5 Thanks @penalosa! - Redesign wrangler dev to more clearly present information and have a bit of a glow up ✨
#9329 410d985 Thanks @penalosa! - Hide logs in the startMixedModeSession() API
#9325 c2678d1 Thanks @edmundhung! - refactor: fallbacks to local image binding from miniflare when local mode is enabled
Updated dependencies [34c71ce, f7c82a4, 7ddd865, 6479fc5, e5ae13a]:
- [email protected]

`v4.16.1`

Compare Source

Patch Changes

#9268 7344344 Thanks @gabivlj! - wrangler containers delete handles API errors correctly

`v4.16.0`

Compare Source

Minor Changes

#9288 3b8f7f1 Thanks @petebacondarwin! - allow --name and --env args on wrangler deploy

Previously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
Now specifying --name is supported and will override any names set in the Wrangler config:

wrangler.json

{
	"name": "config-worker"
	"env": {
		"staging": { "name": "config-worker-env" }
	}
}

Command	Previous (Worker name)	Proposed (Worker name)	Comment
wrangler deploy --name=args-worker	"args-worker"	"args-worker"	CLI arg used
wrangler deploy --name=args-worker --env=staging	Error	"args-worker"	CLI arg used
wrangler deploy --name=args-worker --env=prod	Error	"args-worker"	CLI arg used
wrangler deploy	"config-worker"	"config-worker"	Top-level config used
wrangler deploy --env=staging	"config-worker-env"	"config-worker-env"	Named env config used
wrangler deploy --env=prod	"config-worker-prod"	"config-worker-prod"	CLI arg and top-level config combined

#9265 16de0d5 Thanks @edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config file

Patch Changes

#9234 2fe6219 Thanks @emily-shen! - fix: add no-op props to ctx in getPlatformProxy to fix type mismatch
#9269 66d975e Thanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-worker wrangler dev

Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a multi-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

Also include the ai binding since the bindings is already remote by default anyways.
#9151 5ab035d Thanks @gabivlj! - wrangler containers can be configured with the kind of application rollout on apply
#9231 02d40ed Thanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker) wrangler dev

Under the --x-mixed-mode flag, make sure that bindings configurations with remote: true actually generate bindings to remote resources during a single-worker wrangler dev session, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.

Also include the ai binding since the bindings is already remote by default anyways.
#9221 2ef31a9 Thanks @vicb! - bump @cloudflare/unenv-preset
#9277 db5ea8f Thanks @penalosa! - Support Mixed Mode for more binding types
#9266 f2a16f1 Thanks @petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules
#9245 b87b472 Thanks @penalosa! - Support Mixed Mode Dispatch Namespaces
Updated dependencies [db5ea8f, b87b472]:
- [email protected]

`v4.15.2`

Compare Source

Patch Changes

#9257 33daa09 Thanks @penalosa! - Relax R2 bucket validation for pages dev commands
#9256 3b384e2 Thanks @penalosa! - Move the Analytics Engine simulator implementation from JSRPC to a Wrapped binding. This fixes a regression introduced in https://github.com/cloudflare/workers-sdk/pull/8935 that preventing Analytics Engine bindings working in local dev for Workers with a compatibility date prior to JSRPC being enabled.
Updated dependencies [3b384e2]:
- [email protected]
- @cloudflare/unenv-preset @2.3.2

`v4.15.1`

Compare Source

Patch Changes

#9248 07f4010 Thanks @vicb! - fix unenv version mismatch
#9219 ea71df3 Thanks @vicb! - bump unenv to 2.0.0-rc.17
#9246 d033a7d Thanks @edmundhung! - fix: strip CF-Connecting-IP header within fetch

In v4.15.0, Miniflare began stripping the CF-Connecting-IP header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches the fetch API to strip the header during local wrangler dev sessions as a temporary workaround until the underlying issue is resolved.
Updated dependencies [f61a08e, ea71df3, d033a7d]:
- @cloudflare/unenv-preset @2.3.2
- [email protected]

`v4.15.0`

Compare Source

Minor Changes

#8794 02f0699 Thanks @eastlondoner! - This adds support for more accurate types for service bindings when running wrangler types. Previously, running wrangler types with a config including a service binding would generate an Env type like this:
```
interface Env {
	SERVICE_BINDING: Fetcher;
}
```
This type was "correct", but didn't capture the possibility of using JSRPC to communicate with the service binding. Now, running wrangler types -c wrangler.json -c ../service/wrangler.json (the first config representing the current Worker, and any additional configs representing service bound Workers) will generate an Env type like this:
```
interface Env {
	SERVICE_BINDING: Service<import("../service/src/index").Entrypoint>;
}
```
#8716 63a6504 Thanks @ItsWendell! - add --metafile flag to generate esbuild metadata file during build
#9122 f17ee08 Thanks @avenceslau! - Unhide wrangler workflows delete command

Patch Changes

#9168 6b42c28 Thanks @dario-piotrowicz! - remove experimental MixedModeConnectionString type

remove the experimental MixedModeConnectionString type which
is now exposed by Miniflare instead
#7914 37af035 Thanks @andyjessop! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests
#9161 53ba97d Thanks @lambrospetrou! - Fix d1 info command showing read_replication: [object Object]
#9165 91d0c40 Thanks @vicb! - validate r2 bucket names
#9183 f6f1a18 Thanks @dario-piotrowicz! - add remote option to initial bindings

add the remote option (initial implementation
gated behind --x-mixed-mode) for the following
bindings: service, kv, r2, d1, queue and workflow
#9149 415520e Thanks @penalosa! - Implement mixed mode proxy server & client
Updated dependencies [37af035, ceeb375, 349cffc, 362cb0b, 2cc8197, 6b42c28]:
- [email protected]

`v4.14.4`

Compare Source

Patch Changes

#9124 d0d62e6 Thanks @dario-piotrowicz! - make that unstable_startWorker can correctly throw configuration errors

make sure that unstable_startWorker can throw configuration related errors when:
- the utility is called
- the worker's setConfig is called with the throwErrors argument set to true
additionally when an error is thrown when unstable_startWorker is called make sure
that the worker is properly disposed (since, given the fact that it is not returned
by the utility the utility's caller wouldn't have any way to dispose it themselves)

`v4.14.3`

Compare Source

Patch Changes

#9158 826c5e8 Thanks @petebacondarwin! - fix CallSite.toString() not to throw
#9159 c6b3f10 Thanks @petebacondarwin! - bump esbuild version to fix regression in 0.25.0
#8985 078c568 Thanks @gabivlj! - wrangler deploy is able to deploy new container versions
#9162 8c3cdc3 Thanks @petebacondarwin! - Do not report "d1 execute" command file missing error to Sentry
Updated dependencies [df5d1f6, 4672bda, c6b3f10]:
- [email protected]

`v4.14.2`

Compare Source

Patch Changes

#9118 1cd30a5 Thanks @dario-piotrowicz! - fix: remove outdated js-doc comment for unstable_startDevWorker's entrypoint
#9120 11aa362 Thanks @dario-piotrowicz! - Add experimental_startMixedModeSession no-op utility

This experimental utility has no effect. More details will be shared as we roll out its functionality.
#7423 2be85d7 Thanks @penalosa! - Make sure custom build logging output is more clearly signposted, and make sure it doesn't interfere with the interactive dev session output.
#9112 3fe85d4 Thanks @penalosa! - Warn if the Node.js version is below Node.js 20

`v4.14.1`

Compare Source

Patch Changes

#9085 cdc88d8 Thanks @petebacondarwin! - Do not include .wrangler and Wrangler config files in additional modules

Previously, if you added modules rules such as **/*.js or **/*.json, specified no_bundle: true, and the entry-point to the Worker was in the project root directory, Wrangler could include files that were not intended, such as .wrangler/tmp/xxx.js or the Wrangler config file itself. Now these files are automatically skipped when trying to find additional modules by searching the file tree.
#9095 508a1a3 Thanks @petebacondarwin! - wrangler login put custom callback host and port into the auth URL
#9113 82e220e Thanks @dario-piotrowicz! - Add x-mixed-mode flag

This experimental flag currently has no effect. More details will be shared as we roll out its functionality.
Updated dependencies [357d42a]:
- [email protected]

`v4.14.0`

Compare Source

Minor Changes

#8981 3b60131 Thanks @Caio-Nogueira! - Adds support for waitForEvent step type
#9083 137d2da Thanks @penalosa! - Support Tail Workers in local dev

Patch Changes

#8975 9bf55aa Thanks @Caio-Nogueira! - Adds missing waiting status on the wrangler workflow instances list command
#9048 0b4d22a Thanks @garvit-gupta! - fix: Validate input file for Vectorize inserts
Updated dependencies [d2ecc76, 137d2da]:
- [email protected]

Patch Changes

#8983 f5ebb33 Thanks @Caio-Nogueira! - Remove open-beta disclaimer from workflows commands
#8990 6291fa1 Thanks @emily-shen! - fix: When generating Env types, set type of version metadata binding to WorkerVersionMetadata. This means it now correctly includes the timestamp field.
#8966 234afae Thanks @penalosa! - Internal refactor to use the createCommand utility
Updated dependencies [fc47c79, 0838f1b]:
- [email protected]

`v4.13.0`

Compare Source

Minor Changes

#8640 5ce70bd Thanks @kentonv! - Add support for defining props on a Service binding.

In your configuration file, you can define a service binding with props:

{
	"services": [
		{
			"binding": "MY_SERVICE",
			"service": "some-worker",
			"props": { "foo": 123, "bar": "value" }
		}
	]
}

These can then be accessed by the callee:

import { WorkerEntrypoint } from "cloudflare:workers";

export default class extends WorkerEntrypoint {
	fetch() {
		return new Response(JSON.stringify(this.ctx.props));
	}
}

#8771 0cfcfe0 Thanks @dario-piotrowicz! - feat: add config.keep_names option

Adds a new option to Wrangler to allow developers to opt out of esbuild's keep_names option (https://esbuild.github.io/api/#keep-names). By default, Wrangler sets this to true

This is something developers should not usually need to care about, but sometimes
keep_names can create issues, and in such cases they will be now able to opt-out.

Example wrangler.jsonc:
```
{
	"name": "my-worker",
	"main": "src/worker.ts",
	"keep_names": false
}
```

Patch Changes

#9024 c409318 Thanks @IRCody! - Correctly handle 0 length responses to wrangler containers list.
Updated dependencies [5ce70bd, 3f0adf3]:
- [email protected]

`v4.12.1`

Compare Source

Patch Changes

#8935 41f095b Thanks @penalosa! - Internal refactor to move local analytics engine support from Wrangler to Miniflare
Updated dependencies [2a7749b, 41f095b]:
- [email protected]

`v4.12.0`

Compare Source

Minor Changes

#8316 69864b4 Thanks @gnekich! - introduce callback-host and callback-port param for wrangler login command

Patch Changes

#8889 eab7ad9 Thanks @penalosa! - When Wrangler encounters an error, if the Bun runtime is detected it will now warn users that Wrangler does not officially support Bun.
#8673 5de2b9a Thanks @IRCody! - Add containers {info, list, delete} subcommands.
Updated dependencies [62c40d7]:
- [email protected]

`v4.11.1`

Compare Source

Patch Changes

#8950 bab1724 Thanks @edmundhung! - fix: include telemetry-related environment variables in release builds
#8903 085a565 Thanks @emily-shen! - disable eslint in generated types file
Updated dependencies [511be3d]:
- [email protected]

`v4.11.0`

Compare Source

Minor Changes

#8890 c912b99 Thanks @edmundhung! - update esbuild version to 0.25
#8711 4cc036d Thanks @CarmenPopoviciu! - Add the Pages deployment id to the JSON output for wrangler pages deployment list
#8244 84ecfe9 Thanks @CarmenPopoviciu! - feat: Add debug logs to capture assets upload status, specifically:
- which asset files were read from the file system
- which files were successfully uploaded

Patch Changes

#8885 f2802f9 Thanks @CarmenPopoviciu! - Disambiguate the "No files to upload. Proceeding with deployment..." message
#8924 d2b44a2 Thanks @dario-piotrowicz! - fix redirected config env validation breaking wrangler pages commands

a validation check has recently been introduced to make wrangler error on
deploy commands when an environment is specified and a redirected configuration
is in use (the reason being that redirected configurations should not include
any environment), this check is problematic with pages commands where the
"production" environment is anyways set by default, to address this the validation
check is being relaxed here on pages commands
Updated dependencies [f5413c5]:
- [email protected]

`v4.10.0`

Compare Source

Minor Changes

#8807 dcce2ec Thanks @LuisDuarte1! - Promote workflows commands to stable

Patch Changes

#8883 5388447 Thanks @penalosa! - fix: Only log requests to the Wrangler dev server once
Updated dependencies [b7ac367, 5388447]:
- [email protected]

`v4.9.1`

Compare Source

Patch Changes

Updated dependencies [d454ad9]:
- [email protected]

`v4.9.0`

Compare Source

Minor Changes

#8375 930ebb2 Thanks @penalosa! - Add support for email local dev and send_email binding

Patch Changes

#8809 09464a6 Thanks @dario-piotrowicz! - improve error message when redirected config contains environments

this change improves that validation error message that users see
when a redirected config file contains environments, by:
- cleaning the message formatting and displaying the
  offending environments in a list
- prompting the user to report the issue to the author
  of the tool which has generated the config
#8829 62df08a Thanks @cmackenzie1! - Add option --cors-origin none to remove CORS settings on a pipeline
Updated dependencies [afd93b9, 930ebb2]:
- [email protected]

`v4.8.0`

Compare Source

Minor Changes

#8394 93267cf Thanks @edmundhung! - Support Secrets Store Secret bindings

Patch Changes

#8780 4e69fb6 Thanks @cmackenzie1! - - Rename wrangler pipelines show to wrangler pipelines get
- Replace --enable-worker-binding and --enable-http with --source worker and --source http (or
  --source http worker for both)
- Remove --file-template and --partition-template flags from wrangler pipelines create|update
- Add pretty output for wrangler pipelines get <pipeline>. Existing output is available using --format=json.
- Clarify the minimums, maximums, and defaults (if unset) for wrangler pipelines create commands.
#8596 75b454c Thanks @dario-piotrowicz! - add validation to redirected configs in regards to environments

add the following validation behaviors to wrangler deploy commands, that relate
to redirected configs (i.e. config files specified by .wrangler/deploy/config.json files):
- redirected configs are supposed to be already flattened configurations without any
  environment (i.e. a build tool should generate redirected configs already targeting specific
  environments), so if wrangler encounters a redirected config with some environments defined
  it should error
- given the point above, specifying an environment (--env=my-env) when using redirected
  configs is incorrect, so these environments should be ignored and a warning should be
  presented to the user
#8795 d4c1171 Thanks @GregBrimble! - feat: Unhide wrangler pages functions build command.

This is already documented for Pages Plugins and by officially documenting it, we can ease the transition to Workers Assets for users of Pages Functions.
Updated dependencies [93267cf, ec7e621]:
- [email protected]

`v4.7.2`

Compare Source

Patch Changes

#8763 2650fd3 Thanks @garrettgu10! - R2 data catalog URIs now separate account ID and warehouse name with a slash rather than an underscore
#8341 196f51d Thanks @kotkoroid! - Improve error message when request to obtain membership info fails

Wrangler now informs user that specific permission might be not granted when fails to obtain membership info. The same information is provided when Wrangler is unable to fetch user's email.
Updated dependencies [e0efb6f, 0a401d0]:
- [email protected]

`v4.7.1`

Compare Source

Patch Changes

#8746 7427004 Thanks @emily-shen! - Log whether a command is operating on a remote or local resource
#8757 199caa4 Thanks @emily-shen! - fix: return actual error on wrangler secret bulk
#8750 80ef13c Thanks @emily-shen! - fix: include documentation_url in API Errors if provided
#8759 55b336f Thanks @garvit-gupta! - fix: Minor refactor for the r2 data catalog commands
#8753 245cfbd Thanks @cmackenzie1! - - Hide --transform-worker flag on wrangler pipelines <create|update> during private beta.
- Add --shard-count option for wrangler pipelines <create|update> for more control over Pipeline throughput or file
  size
Updated dependencies [007f322]:
- [email protected]

`v4.7.0`

Compare Source

Minor Changes

#8727 3993374 Thanks @Ltadrian! - add sslmode to hyperdrive and update mtls flags

Patch Changes

#8720 8df60b5 Thanks @lukevalenta! - Fix logic to derive resource name from binding by replacing all underscores with dashes
#8697 ec1f813 Thanks @emily-shen! - fix: stop getPlatformProxy crashing when internal DOs are present

Internal DOs still do not work with getPlatformProxy, but warn instead of crashing.
#8737 624882e Thanks @garvit-gupta! - fix: General improvements for the R2 catalog commands

`v4.6.0`

Compare Source

Minor Changes

#8548 24c2c8f Thanks @garvit-gupta! - feat: Add wrangler commands for R2 Data Catalog

Patch Changes

#8583 ecbab5d Thanks @knickish! - Improve formatting of cache options for hyperdrive list command

`v4.5.1`

Compare Source

Patch Changes

#8666 f29f018 Thanks @penalosa! - Remove NodeJSCompatModule. This was never fully supported, and never worked for deploying Workers from Wrangler.
Updated dependencies [cad99dc, [f29f018](https://redirect.github.com/cloudflare/workers-sdk/co

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 these updates again.

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

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

github-actions · 2025-03-23T14:43:26Z

💻 Website Preview

The latest changes are available as preview in: https://pr-1841.guild-dev-website.pages.dev

renovate bot added the dependencies Pull requests that update a dependency file label Mar 23, 2025

github-actions bot deployed to preview March 23, 2025 14:43 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from a9bb443 to 0ebefc0 Compare March 26, 2025 11:34

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.4.0~~ chore(deps): update dependency wrangler to v4.4.1 Mar 26, 2025

github-actions bot deployed to preview March 26, 2025 11:37 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 0ebefc0 to 28f031b Compare March 26, 2025 23:03

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.4.1~~ chore(deps): update dependency wrangler to v4.5.0 Mar 26, 2025

github-actions bot deployed to preview March 26, 2025 23:06 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 28f031b to d8bae5b Compare March 27, 2025 20:27

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.5.0~~ chore(deps): update dependency wrangler to v4.5.1 Mar 27, 2025

github-actions bot deployed to preview March 27, 2025 20:29 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from d8bae5b to f54bf56 Compare March 28, 2025 18:39

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.5.1~~ chore(deps): update dependency wrangler to v4.6.0 Mar 28, 2025

github-actions bot deployed to preview March 28, 2025 18:41 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from f54bf56 to ec667db Compare April 2, 2025 22:05

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.6.0~~ chore(deps): update dependency wrangler to v4.7.0 Apr 2, 2025

github-actions bot deployed to preview April 2, 2025 22:07 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from ec667db to a8d8ba3 Compare April 4, 2025 11:40

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.7.0~~ chore(deps): update dependency wrangler to v4.7.1 Apr 4, 2025

github-actions bot deployed to preview April 4, 2025 11:42 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from a8d8ba3 to 868ddce Compare April 4, 2025 19:36

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.7.1~~ chore(deps): update dependency wrangler to v4.7.2 Apr 4, 2025

github-actions bot deployed to preview April 4, 2025 19:38 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 868ddce to 24e0cc5 Compare April 7, 2025 16:28

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.7.2~~ chore(deps): update dependency wrangler to v4.8.0 Apr 7, 2025

github-actions bot deployed to preview April 7, 2025 16:30 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 24e0cc5 to 9463c7c Compare April 8, 2025 19:02

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.8.0~~ chore(deps): update dependency wrangler to v4.9.0 Apr 8, 2025

github-actions bot deployed to preview April 8, 2025 19:04 View deployment

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.14.4~~ chore(deps): update dependency wrangler to v4.15.0 May 13, 2025

github-actions bot deployed to preview May 13, 2025 19:05 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 9b1bb6f to 42b0f6f Compare May 13, 2025 23:23

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.15.0~~ chore(deps): update dependency wrangler to v4.14.4 May 13, 2025

github-actions bot deployed to preview May 13, 2025 23:26 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 42b0f6f to 8d6fad8 Compare May 15, 2025 11:37

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.14.4~~ chore(deps): update dependency wrangler to v4.15.1 May 15, 2025

github-actions bot deployed to preview May 15, 2025 11:39 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 8d6fad8 to 9a0d3fb Compare May 15, 2025 23:53

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.15.1~~ chore(deps): update dependency wrangler to v4.15.2 May 15, 2025

github-actions bot deployed to preview May 15, 2025 23:55 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 9a0d3fb to 375ece4 Compare May 20, 2025 12:11

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.15.2~~ chore(deps): update dependency wrangler to v4.16.0 May 20, 2025

github-actions bot deployed to preview May 20, 2025 12:13 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 375ece4 to 6fdb1ae Compare May 22, 2025 11:59

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.16.0~~ chore(deps): update dependency wrangler to v4.16.1 May 22, 2025

github-actions bot deployed to preview May 22, 2025 12:01 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 6fdb1ae to fd762bb Compare May 31, 2025 12:06

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.16.1~~ chore(deps): update dependency wrangler to v4.18.0 May 31, 2025

github-actions bot deployed to preview May 31, 2025 12:09 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from fd762bb to 75ed8d8 Compare June 3, 2025 14:27

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.18.0~~ chore(deps): update dependency wrangler to v4.19.0 Jun 3, 2025

github-actions bot deployed to preview June 3, 2025 14:29 View deployment

renovate bot force-pushed the renovate/wrangler-4.x branch from 75ed8d8 to fde352e Compare June 3, 2025 18:06

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.19.0~~ chore(deps): update dependency wrangler to v4.18.0 Jun 3, 2025

github-actions bot deployed to preview June 3, 2025 18:08 View deployment

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

e81063e

renovate bot force-pushed the renovate/wrangler-4.x branch from fde352e to e81063e Compare June 3, 2025 21:38

renovate bot changed the title ~~chore(deps): update dependency wrangler to v4.18.0~~ chore(deps): update dependency wrangler to v4.19.1 Jun 3, 2025

github-actions bot deployed to preview June 3, 2025 21:40 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency wrangler to v4.19.1 #1841

chore(deps): update dependency wrangler to v4.19.1 #1841

Uh oh!

renovate bot commented Mar 23, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Mar 23, 2025 •

edited

Loading

Uh oh!

Uh oh!

chore(deps): update dependency wrangler to v4.19.1 #1841

Are you sure you want to change the base?

chore(deps): update dependency wrangler to v4.19.1 #1841

Uh oh!

Conversation

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

Uh oh!

Release Notes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch 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

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

github-actions bot commented Mar 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💻 Website Preview

Uh oh!

Uh oh!

renovate bot commented Mar 23, 2025 •

edited

Loading

github-actions bot commented Mar 23, 2025 •

edited

Loading