Version Packages - #15036
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
|
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
8c84c9a to
8d9cff1
Compare
8d9cff1 to
53fd375
Compare
1 participant
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
99eb50cThanks @edmundhung! - Add per-worker control over dev registry registrationMiniflare 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
b4f0c97Thanks @petebacondarwin! - Stop deleting and recreating every dev registry entry on each config updateApplying 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
a60ff4dThanks @nickpatt! - Cut the per-request cost of local observability captureEvery 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__.@cloudflare/autoconfig@0.2.5
Patch Changes
6946da1]:@cloudflare/cli-shared-helpers@0.1.21
Patch Changes
6946da1]:@cloudflare/deploy-helpers@0.6.6
Patch Changes
b4f0c97,a60ff4d,6946da1,99eb50c]:@cloudflare/pages-shared@0.13.165
Patch Changes
b4f0c97,a60ff4d,99eb50c]:@cloudflare/vite-plugin@1.51.1
Patch Changes
#15015
a60ff4dThanks @nickpatt! - Cut the per-request cost of local observability captureEvery 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]:@cloudflare/vitest-pool-workers@0.20.3
Patch Changes
b4f0c97,a60ff4d,99eb50c]:@cloudflare/workers-auth@0.6.1
Patch Changes
6946da1]:@cloudflare/workers-utils@0.31.2
Patch Changes
#15011
6946da1Thanks @LeSingh1! - Validateobservability.logs.head_sampling_rateandobservability.traces.head_sampling_rateare between 0 and 1The 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 as10(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.wrangler@4.119.1
Patch Changes
#15015
a60ff4dThanks @nickpatt! - Cut the per-request cost of local observability captureEvery 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]:@cloudflare/remote-bindings@0.0.8
Patch Changes
b4f0c97,a60ff4d,6946da1,99eb50c]:@cloudflare/runtime-types@0.0.10
Patch Changes
b4f0c97,a60ff4d,99eb50c]: