chore(deps): update dependency wrangler to v3.114.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wrangler (source)	3.95.0 -> 3.114.3

---

Release Notes

cloudflare/workers-sdk (wrangler)

v3.114.3

Compare Source

Patch Changes

• #​8662 5e57717 Thanks @​workers-devprod! - Amend pages dev error message when an environment is requested

• #​8535 6f8e892 Thanks @​workers-devprod! - improve the error messaging when the user provides neither an entry point nor an asset directory

v3.114.2

Compare Source

Patch Changes

• #​8453 f90a669 Thanks @​workers-devprod! - trigger dummy v3 maintenance release for testing

• #​8500 80bbee3 Thanks @​workers-devprod! - Support no_bundle config in Pages for both dev and deploy.

  This was already supported via a command line arg (--no-bundle).

• #​8521 5cd32b1 Thanks @​emily-shen! - fix: throw explicit error for unknown mimetype during wrangler check startup

• #​8504 0192aae Thanks @​workers-devprod! - Fix Workers Assets metafiles (_headers and _redirects) resolution when running Wrangler from a different directory

• Updated dependencies [f90a669]:

  • miniflare@3.20250310.1

v3.114.1

Compare Source

Patch Changes

• #​8383 8d6d722 Thanks @​matthewdavidrodgers! - Make kv bulk put --local respect base64:true

  The bulk put api has an optional "base64" boolean property for each key.
  Before storing the key, the value should be decoded from base64.

  For real (remote) kv, this is handled by the rest api. For local kv, it
  seems the base64 field was ignored, meaning encoded base64 content was
  stored locally rather than the raw values.

  To fix, we need to decode each value before putting to the local
  miniflare namespace when base64 is true.

• #​8273 e3efd68 Thanks @​penalosa! - Support AI, Vectorize, and Images bindings when using @cloudflare/vite-plugin

• #​8427 a352798 Thanks @​vicb! - update unenv-preset dependency to fix bug with Performance global

  Fixes #​8407
  Fixes #​8409
  Fixes #​8411

• #​8390 53e6323 Thanks @​GregBrimble! - Parse and apply metafiles (_headers and _redirects) in wrangler dev for Workers Assets

• #​8392 4d9d9e6 Thanks @​jahands! - fix: retry zone and route lookup API calls

  In rare cases, looking up Zone or Route API calls may fail due to transient errors. This change improves the reliability of wrangler deploy when these errors occur.

  Also fixes a rare issue where concurrent API requests may fail without correctly throwing an error which may cause a deployment to incorrectly appear successful.

• Updated dependencies [8242e07, 53e6323]:

  • miniflare@3.20250310.0

v3.114.0

Compare Source

Minor Changes

• #​8367 7b6b0c2 Thanks @​jonesphillip! - Deprecated --id parameter in favor of --name for both the wrangler r2 bucket lifecycle and wrangler r2 bucket lock commands

v3.113.0

Compare Source

Minor Changes

• #​8300 bca1fb5 Thanks @​vicb! - Use the unenv preset for Cloudflare from @cloudflare/unenv-preset

Patch Changes

• #​8338 2d40989 Thanks @​GregBrimble! - feat: Upload _headers and _redirects if present with Workers Assets as part of wrangler deploy and wrangler versions upload.

• #​8288 cf14e17 Thanks @​CarmenPopoviciu! - feat: Add assets Proxy Worker skeleton in miniflare

  This commit implements a very basic Proxy Worker skeleton, and wires it in the "pipeline" miniflare creates for assets. This Worker will be incrementally worked on, but for now, the current implementation will forward all incoming requests to the Router Worker, thus leaving the current assets behaviour in local dev, the same.

  This is an experimental feature available under the --x-assets-rpc flag: wrangler dev --x-assets-rpc.

• #​8216 af9a57a Thanks @​ns476! - Support Images binding in wrangler types

• #​8304 fbba583 Thanks @​jahands! - chore: add concurrency and caching for Zone IDs and Workers routes lookups

  Workers with many routes can result in duplicate Zone lookups during deployments, making deployments unnecessarily slow. This compounded by the lack of concurrency when making these API requests.

  This change deduplicates these requests and adds concurrency to help speed up deployments.

• Updated dependencies [2d40989, da568e5, cf14e17, 79c7810]:

  • miniflare@3.20250224.0

v3.112.0

Compare Source

Minor Changes

• #​8256 f59d95b Thanks @​jbwcloudflare! - Add two new Queues commands: pause-delivery and resume-delivery

  These new commands allow users to pause and resume the delivery of messages to Queue Consumers

Patch Changes

• #​8274 fce642d Thanks @​emily-shen! - fix bindings to entrypoints on the same worker in workers with assets

• #​8201 2cad136 Thanks @​ichernetsky-cf! - fix: interactively list Cloudchamber deployments using labels

• #​8289 a4909cb Thanks @​penalosa! - Add the experimental --x-assets-rpc flag to gate feature work to support JSRPC with Workers + Assets projects.

• Updated dependencies [fce642d, a4909cb]:

  • miniflare@3.20250214.2

v3.111.0

Compare Source

Minor Changes

• #​7977 36ef9c6 Thanks @​jkoe-cf! - Added wrangler r2 commands for bucket lock configuration

Patch Changes

• #​8248 1cb2d34 Thanks @​GregBrimble! - feat: Omits Content-Type header for files of an unknown extension in Workers Assets

• #​7977 36ef9c6 Thanks @​jkoe-cf! - fixing the format of the R2 lifecycle rule date input to be parsed as string instead of number

v3.110.0

Compare Source

Minor Changes

• #​8253 6dd1e23 Thanks @​CarmenPopoviciu! - Add --cwd global argument to the wrangler CLI to allow changing the current working directory before running any command.

Patch Changes

• #​8191 968c3d9 Thanks @​vicb! - Optimize global injection in node compat mode

• #​8247 a9a4c33 Thanks @​GregBrimble! - feat: Omits Content-Type header for files of an unknown extension in Workers Assets

• Updated dependencies [a9a4c33, 6cae13a]:

  • miniflare@3.20250214.1

v3.109.3

Compare Source

Patch Changes

• #​8175 eb46f98 Thanks @​edmundhung! - fix: unstable_splitSqlQuery should ignore comments when splitting sql into statements

v3.109.2

Compare Source

Patch Changes

• #​7687 cc853cf Thanks @​emily-shen! - fix: bug where Pages deployments that create new projects were failing with a new repo

• #​8131 efd7f97 Thanks @​lambrospetrou! - D1 export will now show an error when the presigned URL is invalid

• Updated dependencies [5e06177]:

  • miniflare@3.20250214.0

v3.109.1

Compare Source

Patch Changes

• #​8021 28b1dc7 Thanks @​0xD34DC0DE! - fix: prevent __cf_cjs name collision in the hybrid Nodejs compat plugin

v3.109.0

Compare Source

Minor Changes

• #​8120 3fb801f Thanks @​sdnts! - Add a new update subcommand for Queues to allow updating Queue settings

• #​8120 3fb801f Thanks @​sdnts! - Allow overriding message retention duration when creating Queues

• #​8026 542c6ea Thanks @​penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

  This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API

• #​8026 542c6ea Thanks @​penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

  This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

  Advanced usage:

  • --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
  • --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/

Patch Changes

• #​8112 fff677e Thanks @​penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata

• #​8120 3fb801f Thanks @​sdnts! - Check bounds when overriding delivery delay when creating Queues

• #​7950 4db1fb5 Thanks @​cmackenzie1! - Add local binding support for Worker Pipelines

• #​8119 1bc60d7 Thanks @​penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format

• #​8130 1aa2a91 Thanks @​emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

  User provided strings are still left redacted as always.

• #​8061 35710e5 Thanks @​emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

  Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.

• Updated dependencies [4db1fb5]:

  • miniflare@3.20250204.1

v3.108.1

Compare Source

Patch Changes

• #​8103 a025ad2 Thanks @​emily-shen! - fix: fix bug where wrangler secret list --format=json was printing the wrangler banner.

• Updated dependencies []:

  • miniflare@3.20250204.0

v3.108.0

Compare Source

Minor Changes

• #​7990 b1966df Thanks @​cmsparks! - Add WRANGLER_CI_OVERRIDE_NAME for Workers CI

• #​8028 b2dca9a Thanks @​emily-shen! - feat: Also log when no bindings are found.

  We currently print a worker's bindings during dev, versions upload and deploy. This just also prints something when there's no bindings found, in case you were expecting bindings.

• #​8037 71fd250 Thanks @​WillTaylorDev! - Provides unsafe.metadata configurations when using wrangler versions secret put.

Patch Changes

• #​8058 1f80d69 Thanks @​WillTaylorDev! - Bugfix: Modified versions secret put to inherit all known bindings, which circumvents a limitation in the API which does not return all fields for all bindings.

• #​7986 88514c8 Thanks @​andyjessop! - docs: clarifies that local resources are "simulated locally" or "connected to remote resource", and adds console messages to help explain local dev

• #​8008 9d08af8 Thanks @​ns476! - Add support for Images bindings (in private beta for now), with optional local support for platforms where Sharp is available.

• #​7769 6abe69c Thanks @​cmackenzie1! - Adds the following new option for wrangler pipelines create and wrangler pipelines update commands:

  --cors-origins           CORS origin allowlist for HTTP endpoint (use * for any origin)  [array]
  

• #​7290 0c0374c Thanks @​emily-shen! - fix: add support for workers with assets when running multiple workers in one wrangler dev instance

  https://github.com/cloudflare/workers-sdk/pull/7251 added support for running multiple Workers in one wrangler dev/miniflare session. e.g. wrangler dev -c wrangler.toml -c ../worker2/wrangler.toml, which among other things, allowed cross-service RPC to Durable Objects.

  However this did not work in the same way as production when there was a Worker with assets - this PR should fix that.

• #​7769 6abe69c Thanks @​cmackenzie1! - Rename wrangler pipelines <create|update> flags

  The following parameters have been renamed:

  Previous Name	New Name
  access-key-id	r2-access-key-id
  secret-access-key	r2-secret-access-key
  transform	transform-worker
  r2	r2-bucket
  prefix	r2-prefix
  binding	enable-worker-binding
  http	enable-http
  authentication	require-http-auth
  filename	file-template
  filepath	partition-template

• #​8012 c412a31 Thanks @​mtlemilio! - Use fetchPagedListResult when listing Hyperdrive configs from the API

  This fixes an issue where only 20 configs were being listed.

• #​8077 60310cd Thanks @​emily-shen! - feat: add telemetry to experimental auto-provisioning

• Updated dependencies [c80dbd8, 0c0374c]:

  • miniflare@3.20250204.0

v3.107.3

Compare Source

Patch Changes

• #​7378 59c7c8e Thanks @​IRCody! - Add build and push helper sub-commands under the cloudchamber command.

• Updated dependencies []:

  • miniflare@3.20250129.0

v3.107.2

Compare Source

Patch Changes

• #​7988 444a630 Thanks @​edmundhung! - Fix #​7985.

  This reverts the changes on #​7945 that caused compatibility issues with Node 16 due to the introduction of sharp.

v3.107.1

Compare Source

Patch Changes

• #​7981 e2b3306 Thanks @​WalshyDev! - Fixes a regression introduced in Wrangler 3.107.0 in which [assets] was not being inherited from the top-level environment.

• Updated dependencies [ab49886]:

  • miniflare@3.20250129.0

v3.107.0

Compare Source

Minor Changes

• #​7897 34f9797 Thanks @​WillTaylorDev! - chore: provides run_worker_first for Worker-script-first configuration. Deprecates experimental_serve_directly.

Patch Changes

• #​7945 d758215 Thanks @​ns476! - Add Images binding (in private beta for the time being)

• #​7947 f57bc4e Thanks @​dario-piotrowicz! - fix: avoid getPlatformProxy logging twice that it is using vars defined in .dev.vars files

  when getPlatformProxy is called and it retrieves values from .dev.vars files, it logs twice
  a message like: Using vars defined in .dev.vars, the changes here make sure that in such cases
  this log only appears once

• #​7889 38db4ed Thanks @​emily-shen! - feat: add experimental resource auto-provisioning to versions upload

• #​7864 de6fa18 Thanks @​dario-piotrowicz! - Update the unstable_getMiniflareWorkerOptions types to always include an env parameter.

  The unstable_getMiniflareWorkerOptions types, when accepting a config object as the first argument,
  didn't accept a second env argument. The changes here make sure they do, since the env is still
  relevant for picking up variables from .dev.vars files.

• #​7964 bc4d6c8 Thanks @​LuisDuarte1! - Fix scripts binding to a workflow in a different script overriding workflow config

• Updated dependencies [cf4f47a]:

  • miniflare@3.20250124.1

v3.106.0

Compare Source

Minor Changes

• #​7856 2b6f149 Thanks @​emily-shen! - feat: add sanitised error messages to Wrangler telemetry

  Error messages that have been audited for potential inclusion of personal information, and explicitly opted-in, are now included in Wrangler's telemetry collection. Collected error messages will not include any filepaths, user input or any other potentially private content.

• #​7900 bd9228e Thanks @​vicb! - chore(wrangler): update unenv dependency version

  unenv@2.0.0-rc.1 allows using the workerd implementation for
  the Node modules net, timers, and timers/promises.
  See unjs/unenv#396.

Patch Changes

• #​7904 50b13f6 Thanks @​WalshyDev! - fix: validation for R2 bucket names, the regex was wrongly rejecting buckets starting with a number and the message wasn't as clear as it could be on what was going wrong.

• #​7895 134d61d Thanks @​jahands! - Fix regression in retryOnAPIFailure preventing any requests from being retried

  Also fixes a regression in pipelines that prevented 401 errors from being retried when waiting for an API token to become active.

• #​7879 5c02e46 Thanks @​andyjessop! - Fix to not require local connection string when using Hyperdrive and wrangler dev --remote

• #​7860 13ab591 Thanks @​vicb! - refactor(wrangler): make JSON parsing independent of Node

  Switch jsonc-parser to parse json:

  • JSON.parse() exception messages are not stable across Node versions
  • While jsonc-parser is used, JSONC specific syntax is disabled

• Updated dependencies []:

  • miniflare@3.20250124.0

v3.105.1

Compare Source

Patch Changes

• #​7884 fd5a455 Thanks @​emily-shen! - feat: make experiemntal auto-provisioning non-interactive by default.

• #​7811 7d138d9 Thanks @​joshthoward! - Fix RPC method invocations showing up as unknown events

• Updated dependencies [40f89a9]:

  • miniflare@3.20250124.0

v3.105.0

Compare Source

Minor Changes

• #​7466 e5ebdb1 Thanks @​Ltadrian! - feat: implement the wrangler cert upload command

  This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

  For uploading mTLS certificate, run:

  • wrangler cert upload mtls-certificate --cert cert.pem --key key.pem --name MY_CERT

  For uploading CA certificate chain, run:

  • wrangler cert upload certificate-authority --ca-cert server-ca.pem --name SERVER_CA

Patch Changes

• #​7867 bdc7958 Thanks @​penalosa! - Revert https://github.com/cloudflare/workers-sdk/pull/7816. This feature added support for the ASSETS bindings to the getPlatformProxy() API, but caused a regression when running npm run preview in newly generated Workers Assets projects.

• #​7868 78a9a2d Thanks @​penalosa! - Revert "Hyperdrive dev remote fix". This PR includes e2e tests that were not run before merging, and are currently failing.

• Updated dependencies []:

  • miniflare@3.20241230.2

v3.104.0

Compare Source

Minor Changes

• #​7715 26fa9e8 Thanks @​penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

• #​7816 f6cc029 Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

  this change makes sure that that getPlatformProxy, when the input configuration
  file contains an assets field, correctly returns the appropriate asset binding proxy

  example:

  // wrangler.json
  {
  	"name": "my-worker",
  	"assets": {
  		"directory": "./public/",
  		"binding": "ASSETS"
  	},
  	"vars": {
  		"MY_VAR": "my-var"
  	}
  }

  import { getPlatformProxy } from "wrangler";
  
  const { env, dispose } = await getPlatformProxy();
  
  if (env.ASSETS) {
  	const text = await (
  		await env.ASSETS.fetch("http://0.0.0.0/file.txt")
  	).text();
  	console.log(text); // logs the content of file.txt
  }
  
  await dispose();

Patch Changes

• #​7785 cccfe51 Thanks @​joshthoward! - Fix Durable Objects transfer migration validation

• #​7821 fcaa02c Thanks @​vicb! - fix(wrangler): fix wrangler config schema defaults

• #​7832 97d2a1b Thanks @​petebacondarwin! - Relax the messaging when Wrangler uses redirected configuration

  Previously the messaging was rendered as a warning, which implied that the user
  had done something wrong. Now it is just a regular info message.

• #​7806 d7adb50 Thanks @​vicb! - chore: update unenv to 2.0.0-rc.0

  Pull a couple changes in node:timers

  • unjs/unenv#384 fix function bindings in node:timer
  • unjs/unenv#385 implement active and _unrefActive in node:timer

  The unenv update also includes #unjs/unenv/381 which implements
  stdout, stderr and stdin of node:process with node:tty

• #​7828 9077a67 Thanks @​edmundhung! - improve multi account error message in non-interactive mode

• Updated dependencies []:

  • miniflare@3.20241230.2

v3.103.2

Compare Source

Patch Changes

• #​7804 16a9460 Thanks @​vicb! - fix(wrangler): use require.resolve to resolve unenv path

v3.103.1

Compare Source

Patch Changes

• #​7798 a1ff045 Thanks @​CarmenPopoviciu! - Reverts #​7720 as it introduced breakage in some of the C3 templates (eg. Nuxt)

v3.103.0

Compare Source

Minor Changes

• #​5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

  add a new --strict-vars option to wrangler types that developers can (by setting the
  flag to false) use to disable the default strict/literal types generation for their variables

  opting out of strict variables can be useful when developers change often their vars values,
  even more so when multiple environments are involved

v3.102.0

Compare Source

Minor Changes

• #​7592 f613276 Thanks @​garrettgu10! - New filter validation logic supporting set and range queries in Vectorize CLI

Patch Changes

• #​7750 df0e5be Thanks @​andyjessop! - bug: Removes the (local) tag on Vectorize bindings in the console output of wrangler dev, and adds-in the same tag for Durable Objects (which are emulated locally in wrangler dev).

• #​7732 d102b60 Thanks @​Ankcorn! - fix pages secret bulk copy

• #​7706 c63f1b0 Thanks @​penalosa! - Remove the server-based dev registry in favour of the more stable file-based dev registry. There should be no user-facing impact.

• Updated dependencies [8e9aa40]:

  • miniflare@3.20241230.2

v3.101.0

Compare Source

Minor Changes

• #​7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

• #​7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

  Run wrangler secret bulk .dev.vars to add the env file

  //.dev.vars
  KEY=VALUE
  KEY_2=VALUE

  This will upload the secrets KEY and KEY_2 to your worker

• #​7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

  This new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
  which Wrangler can use instead of user configuration when running deploy-related commands.
  It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:

• wrangler deploy
• wrangler dev
• wrangler versions upload
• wrangler versions deploy
• wrangler pages deploy
• wrangler pages build
• wrangler pages build-env

Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

{ "configPath": "../../path/to/wrangler.json" }

When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.

• The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.

  name = "my-worker"
  main = "src/index.ts"
  [[kv_namespaces]]
  binding = "<BINDING_NAME1>"
  id = "<NAMESPACE_ID1>"

  Note that this configuration points main at user code entry-point.

• The user runs a custom build, which might read the wrangler.toml to find the entry-point:

  > my-tool build

• This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:

  - dist
    - index.js
  	- wrangler.json
  - .wrangler
    - deploy
  	  - config.json
  

  The dist/wrangler.json will contain:

  {
  	"name": "my-worker",
  	"main": "./index.js",
  	"kv_namespaces": [
  		{ "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
  	]
  }

  And the .wrangler/deploy/config.json will contain:

  {
  	"configPath": "../../dist/wrangler.json"
  }

• #​7685 9d2740a Thanks @​vicb! - allow overriding the unenv preset.

  By default wrangler uses the bundled unenv preset.

  Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
  Those paths are used when resolving the unenv module identifiers to absolute paths.
  This can be used to test a development version.

• #​7694 f3c2f69 Thanks @​joshthoward! - Default wrangler d1 export to --local rather than failing

Patch Changes

• #​7456 ff4e77e Thanks @​andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.

• #​7712 6439347 Thanks @​penalosa! - Remove CF-Connecting-IP for requests to the edge preview

• #​7703 e771fe9 Thanks @​petebacondarwin! - include the top level Worker name in the parsed config structure

• #​7576 773bda8 Thanks @​cmackenzie1! - Remove defaults for batch-max-* pipeline parameters and define value ranges

• Updated dependencies [2c76887, 78bdec5]:

  • miniflare@3.20241230.1

v3.100.0

Compare Source

Minor Changes

• #​7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

  We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

  These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

  N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

• #​7581 cac7fa6 Thanks @​vicb! - chore(wrangler): update unenv dependency version

  unenv now uses the workerd implementation on node:dns
  See the unjs/unenv#376

• #​7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

  Moving away from require.resolve() to handle unenv aliased packages.
  Using the unenv builtin resolution will allow us to drop the .cjs file from the preset
  and to override the base path so that we can test the dev version of the preset.

• #​7533 755a27c Thanks @​danielgek! - Add warning about the browser rendering not available on local

• #​7614 [8abb43f](https://redirect.github.com/cloudflare/workers-sdk/commit/8abb43fcdf0c506fa6268a7f07aa31

---

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.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 559d987

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR