chore(deps-dev): bump wrangler from 4.114.0 to 4.117.0 in /worker

[dependabot]

Bumps wrangler from 4.114.0 to 4.117.0.

Release notes

Sourced from wrangler's releases.

wrangler@4.117.0

Minor Changes

• #14586 5a56dda Thanks @​emily-shen! - Remove containerEngine from the worker options returned by unstable_getMiniflareWorkerOptions

  unstable_getMiniflareWorkerOptions no longer includes containerEngine in the returned workerOptions, since the container engine is a Miniflare instance-wide setting rather than a per-worker one. Callers that build a Miniflare instance from these options should set containerEngine at the top level instead.

Patch Changes

• #14586 5a56dda Thanks @​emily-shen! - Rewrite local testing paths (/cdn-cgi/*)

  Miniflare v5 moved its internal local testing endpoints to /cdn-cgi/local/* (and /__cf_local/* for endpoints that must remain reachable over tunnels) to prevent any potential collision with production routes. wrangler dev and the Vite plugin now transparently rewrite the old paths to the new ones, meaning you can continue to use the old paths without issue.

  These are the new paths:

  • /cdn-cgi/handler/scheduled → /cdn-cgi/local/scheduled
  • /cdn-cgi/handler/email → /cdn-cgi/local/email
  • /cdn-cgi/explorer/* → /cdn-cgi/local/explorer/*
  • /cdn-cgi/mf/scheduled → /cdn-cgi/local/scheduled (Note /cdn-cgi/mf/scheduled is already deprecated)
  • /cdn-cgi/mf/stream/* → /__cf_local/stream/*
  • /cdn-cgi/mf/imagedelivery/* → /__cf_local/imagedelivery/*

• Updated dependencies [5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda]:

  • miniflare@5.20260730.0-alpha

wrangler@4.116.0

Minor Changes

• #14907 beec0fb Thanks @​NuroDev! - Avoid Worker and workers.dev naming prompts in agent-driven deploys

  Wrangler now derives the Worker name from the project and automatically registers the same project-derived workers.dev account subdomain on a first deploy when running in a detected agent environment. The deploy output explains how to change both names.

• #14905 b21eac2 Thanks @​jamesopstad! - The experimental build output directory now includes the Worker's configuration at .cloudflare/output/v0/workers/default/config.json instead of .cloudflare/output/v0/workers/<worker-name>/worker.config.json

• #14893 bb09f1b Thanks @​apeacock1991! - Graduate wrangler check startup from alpha and show bundle size and a local timing summary

  The command no longer prints an alpha warning. It now reports its local profile window, sampled active, garbage collection, and idle time alongside the raw and compressed bundle sizes. The existing measurement warning continues to distinguish these local measurements from startup time measured on Cloudflare.

• #14685 01d7020 Thanks @​edmundhung! - Add support for dispatching email handlers with createTestHarness

  You can now call server.getWorker().email({ from, to, raw }) to dispatch directly to a Worker's email() handler and inspect its outcome, rejection reason, forwarded messages, and replies.

  const result = await server.getWorker().email({
    from: "sender@example.com",
    to: "inbox@example.com",
    raw: [
      "From: Sender <sender@example.com>",
      "To: Inbox <inbox@example.com>",
      "Message-ID: <test@example.com>",

... (truncated)

Commits

• fcb5402 Version Packages (#14939)
• 5a56dda Miniflare v5 alpha (#14586)
• 96fd16f Version Packages (#14898)
• cc54478 [wrangler] Add SQL example to the agent-facing observability query hint (#14918)
• b21eac2 New @cloudflare/build-output-utils package (#14905)
• f05a0de Improve asset directory error messages in Pages Functions builds (#14928)
• bb09f1b feat(wrangler): report startup profile summary (#14893)
• 5e6556a extract Pages Functions compiler into a standalone package (#14785)
• e31ab0f [wrangler] useConfigRedirectIfAvailable for "wrangler triggers deploy" (#14...
• beec0fb feat(wrangler): automate names for agent-driven deploys (#14907)
• 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 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)