Patch Changes
-
#15923
60ccdbdThanks @petebacondarwin! - Upgrade the bundled capnweb implementation to 0.12.0This updates the RPC implementation shipped in Miniflare and remote-binding proxy workers to the latest capnweb release.
-
#15938
62fd03aThanks @dieub! - Resolve the affected Undici dependency in new Wrangler and Vite plugin installsUndici 7.29.1 fixes GHSA-3wwx-pv8p-q78v. Update the shared dependency catalog and matching types used by Miniflare and Wrangler so downstream installs can resolve the patched runtime without an application-level override. A published release is still required for consumers; this changeset does not alter already published package metadata.
-
#15902
c2bb4c8Thanks @michealroberts! - Fix passing anR2ObjectBody#bodyback toR2Bucket#put()viaMiniflare#getR2Bucket()Previously, a body returned by
get()lost its length on the way back through the binding proxy, soput()rejected it with "Provided readable stream must have a known length", even though the same call works in a Worker. The proxy now forwards the stream's length and the body streams straight through without buffering. -
#15906
eb1efe0Thanks @michealroberts! - Preserve the request body length inMiniflare#dispatchFetch()Previously, a request with a known-length body (e.g. a string) was sent to the Worker chunked, without a
Content-Length. Passing itsrequest.bodytoR2Bucket#put()then failed with "Provided readable stream must have a known length", even though the same request works in production. The body's length is now preserved. -
#15910
485cfb3Thanks @james-elicx! - Raise the local R2 custom metadata limit to 8 KiBR2
put()now accepts up to 8,192 bytes of custom metadata, matching the documented R2 limit. Previously, Miniflare rejected metadata larger than 2 KiB.Multipart upload creation now enforces the same limit through both R2 bindings and the local S3 API. Oversized metadata is rejected with error 10012 through R2 bindings, or HTTP 400
MetadataTooLargefor S3 uploads, copies, and multipart initiation.