Version Packages

[workers-devprod]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

miniflare@5.20260801.1-alpha

Major Changes

• #15040 99eb50c Thanks @edmundhung! - Add per-worker control over dev registry registration

  Miniflare workers must now opt in to the dev registry with unsafeRegisterWorker. Wrangler and the Cloudflare Vite plugin use this option to advertise user workers without exposing internal or external workers.

Patch Changes

• #15037 b4f0c97 Thanks @petebacondarwin! - Stop deleting and recreating every dev registry entry on each config update

  Applying options rewrote this instance's dev registry entries by removing them and putting them straight back. Other dev sessions find Workers by watching that directory, so each update briefly looked to them like every Worker in the session had gone away — and a session that had already resolved one of those Workers could be left acting on that, up to and including tearing down a binding to a Worker that never actually stopped running.

  Entries are now reconciled instead: Workers that are still present are updated in place, and only the ones that have genuinely gone are removed. Switching to a different registry path still clears the entries from the directory being left behind.

• #15015 a60ff4d Thanks @nickpatt! - Cut the per-request cost of local observability capture

  Every tail event was written to the trace store as its own Durable Object call, so a request paid two or three round-trips per span. On a module-heavy app under the Vite plugin that dominated dev request latency. Rows are now buffered and written in batches, taking a request from roughly thirty calls to three.

  Work in progress still shows up as it happens: the root span is written immediately, console logs and exceptions as they arrive, and a span's completion is written on the next event once 100ms has passed. An invocation that goes completely quiet writes nothing further until it ends, since the flush is driven by tail events rather than a timer.

  The Vite plugin's own router, asset and proxy workers are also no longer captured. Their traces were noise the Observability views already hid, and skipping them cuts the spans recorded per request — a side benefit being that a trace's root is now your Worker rather than __router-worker__.

wrangler@4.120.0

Minor Changes

• #15008 35c87e9 Thanks @skepticfx! - Adds the ability to find container instances by exact ID or name

  wrangler containers instances <application_id> --search <instance_id_or_name> now searches every page and returns exact matches in human-readable or JSON output. JSON returns a top-level array, including an empty array when there is no match, while human-readable output prints a no-match message. If multiple instances have the same exact name, every matching instance is returned.

• #15008 35c87e9 Thanks @skepticfx! - Add explicit pagination to container instance JSON output

  Use wrangler containers instances <application_id> --json --per-page <size> to return one page with machine-readable result_info, then pass its next_page_token to --page-token to retrieve the next page. Plain --json remains backward-compatible: it requests the complete list and returns the existing top-level array.

Patch Changes

• #15015 a60ff4d Thanks @nickpatt! - Cut the per-request cost of local observability capture

  Every tail event was written to the trace store as its own Durable Object call, so a request paid two or three round-trips per span. On a module-heavy app under the Vite plugin that dominated dev request latency. Rows are now buffered and written in batches, taking a request from roughly thirty calls to three.

  Work in progress still shows up as it happens: the root span is written immediately, console logs and exceptions as they arrive, and a span's completion is written on the next event once 100ms has passed. An invocation that goes completely quiet writes nothing further until it ends, since the flush is driven by tail events rather than a timer.

  The Vite plugin's own router, asset and proxy workers are also no longer captured. Their traces were noise the Observability views already hid, and skipping them cuts the spans recorded per request — a side benefit being that a trace's root is now your Worker rather than __router-worker__.

• Updated dependencies [b4f0c97, a60ff4d, 99eb50c]:

  • miniflare@5.20260801.1-alpha

@cloudflare/autoconfig@0.2.5

Patch Changes

• Updated dependencies [6946da1]:
  • @cloudflare/workers-utils@0.31.2
  • @cloudflare/cli-shared-helpers@0.1.21

@cloudflare/cli-shared-helpers@0.1.21

Patch Changes

• Updated dependencies [6946da1]:
  • @cloudflare/workers-utils@0.31.2

@cloudflare/deploy-helpers@0.6.6

Patch Changes

• Updated dependencies [b4f0c97, a60ff4d, 6946da1, 99eb50c]:
  • miniflare@5.20260801.1-alpha
  • @cloudflare/workers-utils@0.31.2
  • @cloudflare/cli-shared-helpers@0.1.21

@cloudflare/pages-shared@0.13.165

Patch Changes

• Updated dependencies [b4f0c97, a60ff4d, 99eb50c]:
  • miniflare@5.20260801.1-alpha

@cloudflare/vite-plugin@1.51.1

Patch Changes

• #15015 a60ff4d Thanks @nickpatt! - Cut the per-request cost of local observability capture

  Every tail event was written to the trace store as its own Durable Object call, so a request paid two or three round-trips per span. On a module-heavy app under the Vite plugin that dominated dev request latency. Rows are now buffered and written in batches, taking a request from roughly thirty calls to three.

  Work in progress still shows up as it happens: the root span is written immediately, console logs and exceptions as they arrive, and a span's completion is written on the next event once 100ms has passed. An invocation that goes completely quiet writes nothing further until it ends, since the flush is driven by tail events rather than a timer.

  The Vite plugin's own router, asset and proxy workers are also no longer captured. Their traces were noise the Observability views already hid, and skipping them cuts the spans recorded per request — a side benefit being that a trace's root is now your Worker rather than __router-worker__.

• Updated dependencies [35c87e9, b4f0c97, a60ff4d, 99eb50c, 35c87e9]:

  • wrangler@4.120.0
  • miniflare@5.20260801.1-alpha

@cloudflare/vitest-pool-workers@0.20.3

Patch Changes

• Updated dependencies [35c87e9, b4f0c97, a60ff4d, 99eb50c, 35c87e9]:
  • wrangler@4.120.0
  • miniflare@5.20260801.1-alpha

@cloudflare/workers-auth@0.6.1

Patch Changes

• Updated dependencies [6946da1]:
  • @cloudflare/workers-utils@0.31.2

@cloudflare/workers-utils@0.31.2

Patch Changes

• #15011 6946da1 Thanks @LeSingh1! - Validate observability.logs.head_sampling_rate and observability.traces.head_sampling_rate are between 0 and 1

  The 0–1 range check was only applied to the top level observability.head_sampling_rate. The two nested fields were type-checked as numbers but never bounds-checked, so a value such as 10 (a common mix-up with a percentage) was accepted locally and sent to the API.

  {
    "observability": {
      "logs": { "enabled": true, "head_sampling_rate": 10 }
    }
  }

  All three fields now report must be a value between 0 and 1. consistently.

@cloudflare/remote-bindings@0.0.8

Patch Changes

• Updated dependencies [b4f0c97, a60ff4d, 6946da1, 99eb50c]:
  • miniflare@5.20260801.1-alpha
  • @cloudflare/workers-utils@0.31.2
  • @cloudflare/deploy-helpers@0.6.6
  • @cloudflare/cli-shared-helpers@0.1.21
  • @cloudflare/workers-auth@0.6.1

@cloudflare/runtime-types@0.0.10

Patch Changes

• Updated dependencies [b4f0c97, a60ff4d, 99eb50c]:
  • miniflare@5.20260801.1-alpha

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[github-actions]

✅ All changesets look good

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15036

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15036

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15036

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@15036

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15036

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@15036

miniflare

npm i https://pkg.pr.new/miniflare@15036

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15036

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@15036

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@15036

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@15036

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@15036

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15036

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@15036

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@15036

wrangler

npm i https://pkg.pr.new/wrangler@15036

commit: 53fd375