chore(deps): Bump the npm-deps group with 3 updates

[dependabot]

Bumps the npm-deps group with 3 updates: hono, @cloudflare/workers-types and wrangler.

Updates hono from 4.8.3 to 4.8.4

Release notes

Sourced from hono's releases.

v4.8.4

What's Changed

• test: correct usages of Proxy to support Node.js 24 by @​yusukebe in honojs/hono#4260
• fix(cookie): remove not used signingSecret option by @​yusukebe in honojs/hono#4263
• fix(jsx): cloneElement didn't copy children by @​yayugu in honojs/hono#4257
• fix(client): remove index string when calling $url() by @​yusukebe in honojs/hono#4267
• fix(ssg): invoke callback when it's only a dynamic route by @​yusukebe in honojs/hono#4249
• fix(request): req.json() keeps the content as is by @​yusukebe in honojs/hono#4269

Full Changelog: honojs/hono@v4.8.3...v4.8.4

Commits

• 530ab09 4.8.4
• 993d808 fix(request): req.json() keeps the content as is (#4269)
• ed9d72f fix(ssg): invoke callback when it's only a dynamic route (#4249)
• 0432f81 fix(client): remove index string when calling $url() (#4267)
• 09a81e4 fix(jsx): cloneElement didn't copy children (#4257)
• 407d1bd fix(cookie): remove not used signingSecret option (#4263)
• 108e35b test: correct usages of Proxy to support Node.js 24 (#4260)
• See full diff in compare view

Updates @cloudflare/workers-types from 4.20250628.0 to 4.20250705.0

Commits

• See full diff in compare view

Updates wrangler from 4.22.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

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

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)
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions