chore(deps): update cloudflare worker toolchain

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/vitest-pool-workers (source)	^0.19.0 → ^0.20.0
wrangler (source)	4.115.0 → 4.118.0

After merging, regenerate the worker types: pnpm --filter @fmw/preview-worker exec wrangler types && pnpm vp check --fix. The formatter pass is not optional.

---

Release Notes

cloudflare/workers-sdk (@​cloudflare/vitest-pool-workers)

v0.20.1

Compare Source

Patch Changes

• Updated dependencies [cc63aae, f92d1fc, a249591, f92d1fc, f92d1fc, cec9d88, e0bbf55]:
  • wrangler@​4.118.0

v0.20.0

Compare Source

Minor Changes

• #​14586 5a56dda Thanks @​emily-shen! - Breaking change: Remove several options from the miniflare override options

  The following options have been removed from the miniflare override options, as they were not intended to be exposed, were not functional, or have been superseded by other options:

  • wrappedBindings
  • cacheWarnUsage
  • fetchMock: you should use outboundService instead
  • containerEngine: containers were not supported in vitest-pool-workers. Consider using createTestHarness() instead if you want to test against actual containers.

  Additionally, cache has been deprecated and renamed to cacheAPI, but cache remains functional.

Patch Changes

• #​14586 5a56dda Thanks @​emily-shen! - Preserve the deprecated Miniflare cache option

  Vitest configurations using cache continue to work after the internal Miniflare v5 upgrade. The option is translated to cacheAPI; new configurations should use cacheAPI directly.

• #​14586 5a56dda Thanks @​emily-shen! - Stop enabling Miniflare's removed unsafeStickyBlobs option

  The pool no longer sets the unsafeStickyBlobs Miniflare option, which has been removed. This option was only needed for the Durable Object isolated storage feature that was dropped in 0.13.0, so there is no change in behaviour.

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

  • miniflare@5.20260730.0-alpha
  • wrangler@​4.117.0

v0.19.1

Compare Source

Patch Changes

• Updated dependencies [01d7020, beec0fb, 48f0c6c, 8049ca4, d7f38c3, 1394867, cc54478, 5c25cfe, b21eac2, bb09f1b, 1f61001, 01d7020, e31ab0f]:
  • miniflare@​4.20260730.0
  • wrangler@​4.116.0

cloudflare/workers-sdk (wrangler)

v4.118.0

Compare Source

Minor Changes

• #​14057 cc63aae Thanks @​matingathani! - Add --json flag to wrangler containers info for consistent JSON output with sibling commands list and instances

• #​14944 a249591 Thanks @​nickpatt! - Enable local observability capture by default in dev

  wrangler dev and the Vite plugin now capture request traces and console logs into the Local Explorer's Observability tab out of the box — previously this was opt-in behind X_LOCAL_OBSERVABILITY=true. Set X_LOCAL_OBSERVABILITY=false to opt out (for example if the extra per-worker collector/streaming-tail services cause trouble in a multi-process dev-registry setup).

• #​14919 e0bbf55 Thanks @​avenceslau! - Add additional triggers to Workflows

  Workers can now declaratively start a locally defined Workflow. Configure event subscriptions under triggers.events; Wrangler validates each target and updates the script's event triggers during deployment.

  {
    "triggers": {
      "events": [
        {
          "type": "cf.artifacts.repo.pushed",
          "filter": {
            "namespace": "my-namespace",
            "repo_name": "my-repo"
          },
          "targets": [
            {
              "type": "workflow",
              "workflow_name": "my-workflow"
            }
          ]
        }
      ]
    }
  }

Patch Changes

• #​14936 f92d1fc Thanks @​petebacondarwin! - Fix jsx_fragment being ignored when wrangler dev runs a custom build

  If your project uses a custom build and sets both jsx_factory and jsx_fragment, wrangler dev used your jsx_factory value for JSX fragments as well, so fragments compiled incorrectly. Your jsx_fragment value is now used.

• #​14936 f92d1fc Thanks @​petebacondarwin! - Stop wrangler dev starting new work after you stop it or it reloads

  Stopping wrangler dev, or having it reload after a configuration change, could still leave it starting work for the state it had just left behind: your custom build command could run once more after dev had stopped, a change to a file in your assets directory could be reported against configuration that had already been replaced, and in some cases the process could stay alive instead of exiting.

  That work is now discarded, so stopping or reloading wrangler dev leaves nothing running behind it.

• #​14936 f92d1fc Thanks @​petebacondarwin! - Stop wrangler dev from running custom builds concurrently

  When several watched files changed at once — for example during a git pull or a "save all" — wrangler dev started a custom build for every file that changed, so multiple copies of your build command ran at the same time and fought over the same output files.

  A burst of file changes now results in a single build, and a build only starts once the previous one has finished.

• #​13746 cec9d88 Thanks @​edmundhung! - Report a clear error for account IDs that can't be used in a Cloudflare API request

  Account IDs are substituted straight into Cloudflare API URL paths, so a value containing non-ASCII characters previously failed deep inside the request layer with an opaque Cannot convert argument to a ByteString error that gave no hint about which setting was at fault. Account IDs read from CLOUDFLARE_ACCOUNT_ID and from the account_id configuration field are now validated up front, and an invalid value fails with a message naming both the offending value and where it came from.

v4.117.0

Compare Source

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

v4.116.0

Compare Source

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>",
      "Subject: Test email",
      "",
      "Hello from the test harness",
    ].join("\r\n"),
  });
  
  expect(result).toMatchObject({
    outcome: "ok",
    forwards: [{ recipient: "archive@example.com" }],
    replies: [
      {
        sender: "inbox@example.com",
        raw: expect.stringContaining("Thanks for your email"),
      },
    ],
  });

Patch Changes

• #​14929 48f0c6c Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20260722.1	^5.20260730.1
  workerd	1.20260722.1	1.20260730.1

• #​14838 8049ca4 Thanks @​TheSaiEaranti! - Fix ctrl+c not being able to interrupt wrangler while waiting for Cloudflare Access authorization

  When a domain is behind Cloudflare Access (for example during remote bindings startup), wrangler runs cloudflared access login, which only returns once the user completes the authorization flow in the browser. This was invoked synchronously, blocking Node's event loop, so wrangler could not react to ctrl+c (or anything else) until the authorization completed — abandoning the browser flow left a hung wrangler process that had to be killed externally. cloudflared is now spawned asynchronously, keeping wrangler responsive while it waits. The remote runtime passes its abort signal through to the spawn, so tearing down the session kills a still-pending cloudflared immediately, with process exit as a last-resort cleanup.

• #​14871 1394867 Thanks @​nickpatt! - Include the local observability query endpoint in the agent-facing Local Explorer hint

  The hint wrangler dev prints for AI-agent sessions now lists POST /cdn-cgi/explorer/api/local/observability/query, so agents can discover the read-only SQL endpoint for captured request traces and console logs (the spans and logs tables) alongside the existing binding and storage routes.

• #​14918 cc54478 Thanks @​nickpatt! - Improve the agent-facing Local Explorer hint for the observability query endpoint

  When a wrangler dev session is detected as running inside an AI agent, the hint for POST /local/observability/query now explains that the endpoint takes a read-only SQL query (SELECT/WITH only) over the captured spans and logs tables, notes that attributes is JSON (read via json(attributes)), and includes a copy-pasteable curl example. The full OpenAPI schema is demoted to a last-resort footer so agents reach for the small, actionable example first instead of fetching the large schema.

• #​14897 e31ab0f Thanks @​ericclemmons! - Fix wrangler triggers deploy to use Vite-generated redirected configuration

  The command now reads .wrangler/deploy/config.json, matching wrangler deploy and wrangler versions upload, so generated Worker names and trigger settings are applied.

• Updated dependencies [01d7020, 48f0c6c, d7f38c3, 5c25cfe, 1f61001]:

  • miniflare@​4.20260730.0

---

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

• Branch creation
  • "before 6am on monday"
• 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.