Minor Changes

• #16363 d3240f2 Thanks @jamesopstad! - Remove the experimental.newConfig option from Vite plugin v1

  Vite plugin v1 now supports Wrangler configuration files only. Projects using cloudflare.config.ts for configuration should upgrade to Vite plugin v2 beta.

Patch Changes

• #16373 8cc5f87 Thanks @petebacondarwin! - Report unsupported remote bindings under Bun instead of hanging

  Starting remote bindings now fails with an actionable error explaining Bun's unsupported request routing. Use Node.js or disable remote bindings to continue local development.

• #16334 9cecd09 Thanks @petebacondarwin! - Fix Container setup guidance in Vite development and preview

  Container registry instructions now show the Wrangler command and the configuration location, including Wrangler files and inline Vite configuration.

• #16333 68d6eec Thanks @petebacondarwin! - Update the local Workers runtime to the October 19 release

  Include the fix for nested asset paths during local development on Windows, together with the compatible Wrangler release.

  The runtime update also disposes Workflow step results and introspection modifiers after use, preventing undisposed RPC warnings and cancelled local Workflow requests.

• #16379 160e655 Thanks @petebacondarwin! - Update the local Workflow runtime to use native storage cleanup

  Consume the Miniflare fix that queues Workflow persistence deletion with instance recreation, including deletion through the local Explorer. This prevents storage cleanup from racing reuse of the same Workflow instance ID.

• #16289 bbe822f Thanks @petebacondarwin! - Retry remote preview token refreshes after transient failures

  Backport the retry fix to the private remote-bindings workspace package and require wrangler@4.151.1 so long-running remote development sessions recover after a network outage.

• #16291 0262f7d Thanks @petebacondarwin! - Use published SDK dependencies for Vite plugin v1 maintenance

  Pin the plugin's published SDK dependencies to their deployed npm versions. Keep private shared packages as workspace dependencies so their implementation and build tools remain available on the v1 maintenance branch.

Patch Changes

• #15611 4508172 Thanks @taylorlee! - Allow wrangler dev to start module Workers without a default export

  Previously, wrangler dev failed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export was added. These Workers now start normally in local development without that workaround.

• #16370 61fc739 Thanks @WalshyDev! - Fetch the remote config diff from the configured compliance region

  When a Worker was last deployed from the dashboard, wrangler deploy and wrangler versions upload download its remote configuration to compare with the local one. These requests ignored the compliance_region field in the Wrangler configuration file and only honoured the CLOUDFLARE_COMPLIANCE_REGION environment variable. A FedRAMP High Worker configured through the config file would send them to api.cloudflare.com instead of api.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.

• #15846 a88cac4 Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun

  Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.

• #16359 262021d Thanks @tw4! - Stop --strict deploys and version uploads from aborting when the API omits optional binding fields

  Previously, wrangler deploy --strict and wrangler versions upload --strict could report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.

• Updated dependencies [3464abc]:

  • miniflare@5.20261019.1-beta

Patch Changes

• #16259 017bf9b Thanks @NuroDev! - Use Vitest 5 in newly generated Workers projects

  Workers templates now install Vitest 5 and require @cloudflare/vitest-plugin 1.4.3 or newer, which supports Vitest's filesystem module cache.

Patch Changes

• #15708 3464abc Thanks @samstarling! - Dispose Workflow step results and introspection modifiers after use

  Release RPC resources deterministically during local Workflow execution and introspection. This prevents undisposed RPC warnings and requests being cancelled after their execution context has ended. Live step results retain their original data shape, including typed-array offsets and backing buffers. Callbacks that finish after a step times out also release their results, cancelling unused streams without delaying retries.

  Disposing an introspector still aborts the instance if modifier acquisition failed, without introducing a teardown error. Non-stream results containing function-valued array properties are rejected according to the serialisable-output contract, instead of silently discarding those properties during storage normalisation.

Patch Changes

• #16259 017bf9b Thanks @NuroDev! - Support Vitest 5 in shared test helpers

  The optional Vitest peer ranges now accept both Vitest 4 and 5, allowing consumers to upgrade without dropping compatibility with Vitest 4.

Patch Changes

• #16323 3fa1e33 Thanks @jamesopstad! - Migrate Workers Playground to use @cloudflare/vite-plugin v2 beta and cf

  A single cloudflare.config.ts file is now used for development and builds. cf is used in place of Wrangler for deployments.

Patch Changes

• #16259 017bf9b Thanks @NuroDev! - Support Vitest 5 in shared test helpers

  The optional Vitest peer ranges now accept both Vitest 4 and 5, allowing consumers to upgrade without dropping compatibility with Vitest 4.

• Updated dependencies [017bf9b]:

  • @cloudflare/workers-utils@0.47.3

Patch Changes

• #15708 3464abc Thanks @samstarling! - Dispose Workflow step results and introspection modifiers after use

  Release RPC resources deterministically during local Workflow execution and introspection. This prevents undisposed RPC warnings and requests being cancelled after their execution context has ended. Live step results retain their original data shape, including typed-array offsets and backing buffers. Callbacks that finish after a step times out also release their results, cancelling unused streams without delaying retries.

  Disposing an introspector still aborts the instance if modifier acquisition failed, without introducing a teardown error. Non-stream results containing function-valued array properties are rejected according to the serialisable-output contract, instead of silently discarding those properties during storage normalisation.

• #15846 a88cac4 Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun

  Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.

• Updated dependencies [4508172, 61fc739, 3464abc, a88cac4, 262021d]:

  • wrangler@4.151.3
  • miniflare@5.20261019.1-beta

Patch Changes

• Updated dependencies [3464abc]:
  • miniflare@5.20261019.1-beta

Patch Changes

• Updated dependencies [61fc739, 3464abc, 262021d, 017bf9b]:
  • @cloudflare/deploy-helpers@0.22.1
  • miniflare@5.20261019.1-beta
  • @cloudflare/workers-auth@0.14.1
  • @cloudflare/workers-utils@0.47.3
  • @cloudflare/cli-shared-helpers@0.2.7