build(deps-dev): bump wrangler from 3.112.0 to 4.23.0

[dependabot]

Bumps wrangler from 3.112.0 to 4.23.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.23.0

Minor Changes

• #9535 56dc5c4 Thanks @​penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

• #9810 8acaf43 Thanks @​WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.

Patch Changes

• #9775 4309bb3 Thanks @​vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

• #9799 d11288a Thanks @​penalosa! - Better messaging for account owned tokens in wrangler whoami

• Updated dependencies [56dc5c4]:

  • miniflare@4.20250617.5

wrangler@4.22.0

Minor Changes

• #7871 f2a8d4a 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.jsonc
  {
  	"name": "my-worker",
  	"assets": {
  		"directory": "./public/",
  		"binding": "ASSETS",
  	},
  }

  import { getPlatformProxy } from "wrangler";
  const { env, dispose } = await getPlatformProxy();
  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();

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.23.0

Minor Changes

• #9535 56dc5c4 Thanks @​penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

• #9810 8acaf43 Thanks @​WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.

Patch Changes

• #9775 4309bb3 Thanks @​vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

• #9799 d11288a Thanks @​penalosa! - Better messaging for account owned tokens in wrangler whoami

• Updated dependencies [56dc5c4]:

  • miniflare@4.20250617.5

4.22.0

Minor Changes

• #7871 f2a8d4a 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.jsonc
  {
  	"name": "my-worker",
  	"assets": {
  		"directory": "./public/",
  		"binding": "ASSETS",
  	},
  }

  import { getPlatformProxy } from "wrangler";
  const { env, dispose } = await getPlatformProxy();
  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();

... (truncated)

Commits

• 148597d Version Packages (#9805)
• 56dc5c4 Initial support for VSCode Javascript Debug Terminals (#9535)
• 81bd41c clarify and ensure that for local e2e any account can be used (#9762)
• d11288a Better messaging for account owned tokens (#9799)
• 4309bb3 Cap the number of errors and warnings for bulk KV put (#9775)
• 8acaf43 WC-3626 Use branch name provided from WCI (#9810)
• aa5424c Version Packages (#9745)
• 2355499 Revert "Bump the workerd-and-workers-types group with 2 updates (#9744)" (#9750)
• 94a340e WC-2965 Prevent selecting in-progress deployments when tailing (#9684)
• f2a8d4a add support for assets bindings to getPlatformProxy (take 2) (#7871)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)