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

[renovate]

This PR contains the following updates:

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

---

Release Notes

cloudflare/workers-sdk (wrangler)

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]:

  • [email protected]

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]:

  • [email protected]

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

  [email protected] 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 []:

  • [email protected]

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]:

  • [email protected]

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 []:

  • [email protected]

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 []:

  • [email protected]

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]:

  • [email protected]

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]:

  • [email protected]

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 Thanks @​vicb! - chore(wrangler): update unenv dependency version

  The updated unenv contains a fix for the module resolution,
  see unjs/unenv#378.
  That bug prevented us from using unenv module resolution,
  see #​7583.

• Updated dependencies [b4e0af1]:

  • [email protected]

v3.99.0

Compare Source

Minor Changes

• #​7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

  Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

  1. check for asset files changes
  2. upload the changed assets, if any

  This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

• #​7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

• #​7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

• #​7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

  experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

• Updated dependencies [1488e11, 7216835]:

  • [email protected]

v3.98.0

Compare Source

Minor Changes

• #​7476 5124b5d Thanks @​WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets.
  These assets will be served as though the assets directly were mounted to the root.
  For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.

• #​7380 72935f9 Thanks @​CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

• #​7573 fb819f9 Thanks @​emily-shen! - feat: add experimental_readRawConfig()

  Adds a Wrangler API to find and read a config file

• #​7549 42b9429 Thanks @​penalosa! - Expand metrics collection to:

  • Detect Pages & Workers CI
  • Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv

• #​7583 8def8c9 Thanks @​penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

v3.97.0

Compare Source

Minor Changes

• #​7522 6403e41 Thanks @​vicb! - feat(wrangler): 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.

• #​7479 2780849 Thanks @​penalosa! - Accept a JSON file of the format { name: string }[] in wrangler kv bulk delete, as well as the current string[] format.

Patch Changes

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

• #​7345 15aa936 Thanks @​edmundhung! - fix(wrangler): keypress event name is optional

v3.96.0

Compare Source

Minor Changes

• #​7510 004af53 Thanks @​oliy! - Add file prefix option to wrangler pipelines commands

• #​7383 8af3365 Thanks @​jonesphillip! - Added wrangler r2 domain get command

Patch Changes

• #​7542 f13c897 Thanks @​CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commands

  Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.

• #​6754 0356d0a Thanks @​bluwy! - refactor: move @cloudflare/workers-shared as dev dependency

• #​7478 2e90efc Thanks @​petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environment

  It is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration.
  But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment.
  Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration.
  Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.

• #​7524 11f95f7 Thanks @​gpanders! - Include response body in Cloudchamber API errors

• #​7427 3bc0f28 Thanks @​edmundhung! - The x-provision experimental flag now identifies draft and inherit bindings by looking up the current binding settings.

  Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during wrangler deploy.

• Updated dependencies []:

  • [email protected]

---

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 is behind base branch, 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.

[github-actions]

Package Changes Through 9398fcf

No changes.

Add a change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector

[socket-security]

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected] 🔁 npm/[email protected]	Transitive: environment, filesystem, network, shell, unsafe	+47	23.3 MB	wrangler-publisher

View full report↗︎