Minor Changes
-
#15998
b75421fThanks @dario-piotrowicz! - Addassets.base_pathsupport to Workers AssetsServe an asset directory from a public URL prefix without changing its on-disk layout:
Wrangler, preview, Miniflare, and generated build configuration preserve the explicitly selected value, while the Asset Worker normalizes it and strips the prefix only for asset lookup. Requests passed to a user Worker, request-facing headers, and redirects retain the public path. Relative pathname inputs are interpreted as root-relative prefixes, URL-shaped values are rejected, and omitting the option preserves existing root-path behavior.
Authored
_headersand_redirectsrules continue to match full public paths. In particular, both the source and destination of an authored200asset rewrite must include the configured public prefix; Asset Worker-generated redirects are prefixed automatically. -
#15330
f8cdcb9Thanks @akshitsinha! - Manage local Flagship flags in Local ExplorerBound Flagship apps now appear in Local Explorer. You can create, edit, toggle, delete, and evaluate flags against the same local store used by your Worker, including targeting conditions and percentage rollouts.
Explorer requests are routed to the development process that owns each app, so Flagship management also works across multiple local Workers.
Patch Changes
-
#16081
0ec13b7Thanks @petebacondarwin! - Authenticate dev registry updates and internal loopback requestsRequire per-instance credentials for dev registry updates and internal loopback requests, including WebSocket upgrades. Authenticate callers before parsing registry updates or dispatching privileged loopback operations, while preserving legitimate shared-storage peers.
-
#16014
c492d63Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Dependency From To @cloudflare/workers-types ^5.20261001.1 ^5.20261005.1 workerd 1.20261001.1 1.20261005.1 -
#16079
ba52118Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
Dependency From To @cloudflare/workers-types ^5.20261005.1 ^5.20261006.1 workerd 1.20261005.1 1.20261006.1 -
#14921
946aaa7Thanks @Mohith26! - Prevent local D1 session bookmark errors from crashing the development serverSession bookmark lookup failures, including SQLite errors when another connection holds the database write lock, now reach the Worker as catchable
D1_ERRORs. SQL execution and bookmark retrieval share a transaction, so a failed lookup rolls back the queries and retrying cannot duplicate their writes. This applies to local D1 through Miniflare, Wrangler, the Vite plugin, and the Vitest plugin.Fixes #14916
-
#15781
48f3c04Thanks @Wichtowski! - ReducedispatchFetch()connection exhaustion under sustained local and CI workloadsRepeated dispatches now reuse runtime connections for all HTTP methods, including
POST,PUT,DELETE, andPATCH, instead of creating a new connection for every request. This prevents read-heavy and write-heavy Miniflare test suites from exhausting the host's available ephemeral ports. Transport failures are surfaced without automatically replaying requests, since Worker handlers can have side effects even forGETandHEAD. Idle runtime connections now close after one second, before workerd's five-second idle timeout can race with reuse. -
#16033
5606a74Thanks @Pduhard! - Remove a 40 ms delay from Hyperdrive queries in local devMiniflare's local Hyperdrive proxy left Nagle's algorithm on for its sockets. A Postgres driver that sends one query in several small writes, such as
pgfor every query with parameters, had the later writes held back until the database acknowledged the first, which took about 40 ms per query. Large results were held back the same way on the way back to the Worker.The proxy now turns on
noDelayfor the connection from the Worker and for the connection to the database. Connection strings usingsslmode=disableare unaffected, since that mode connects directly and skips the proxy. -
#16050
e44cf6bThanks @acchou! - Serve each Worker's own static assets when several Workers with assets run togetherWhen several Workers with static assets ran in one Miniflare instance, such as
wrangler devwith multiple-cconfigs or the test harness, every Worker read its assets from the same Worker's directory. Other Workers got 404s or that Worker's file at the same path. Each Worker now reads its own assets directory. -
#16063
0b51fecThanks @Cherry! - Start the synchronous proxy worker before returning proxiesgetBindings(),getDurableObjectNamespace()and the other proxy getters now wait for the worker that serves synchronous proxy calls to start, instead of the first synchronous call blocking Node's main thread while it boots. That block also stalled every other Miniflare instance served from the same process, such as Vitest pool workers running test files in parallel.
{ "assets": { "directory": "./public", "base_path": "/docs" } }