Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 v3-maintenance, this PR will be updated.
Releases
[email protected]
Patch Changes
#8681
7a57c14Thanks @workers-devprod! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests#9250
b2b5ee8Thanks @workers-devprod! - fix: stripCF-Connecting-IPheader withinfetchIn v4.15.0, Miniflare began stripping the
CF-Connecting-IPheader via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches thefetchAPI to strip the header during localwrangler devsessions as a temporary workaround until the underlying issue is resolved.#9211
56a0d6eThanks @petebacondarwin! - fix: ensure the fetch proxy message port is startedWhile Node.js will start the message port automatically when a
messageevent listener is added,this diverges from the standard Web API for message ports, which require you to explicitly start
listening on the port.
[email protected]
Patch Changes
#9262
2c3d8ddThanks @workers-devprod! - fix: add no-oppropstoctxingetPlatformProxyto fix type mismatch#8681
7a57c14Thanks @workers-devprod! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests#9128
c535845Thanks @dario-piotrowicz! - fix: remove outdated js-doc comment forunstable_startDevWorker'sentrypoint#9259
b742171Thanks @workers-devprod! - Relax R2 bucket validation forpages devcommands#9172
4e943b1Thanks @vicb! - validate r2 bucket names#9250
b2b5ee8Thanks @workers-devprod! - fix: stripCF-Connecting-IPheader withinfetchIn v4.15.0, Miniflare began stripping the
CF-Connecting-IPheader via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches thefetchAPI to strip the header during localwrangler devsessions as a temporary workaround until the underlying issue is resolved.#9267
8b4f24aThanks @workers-devprod! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules#9163
d67cd0dThanks @petebacondarwin! - Do not report "d1 execute" command file missing error to Sentry#8957
9d4ff5bThanks @workers-devprod! - Make sure custom build logging output is more clearly signposted, and make sure it doesn't interfere with the interactive dev session output.#9166
9b4c91dThanks @lambrospetrou! - Fix d1 info command showing read_replication: [object Object]Updated dependencies [
7a57c14,b2b5ee8,56a0d6e]:@cloudflare/[email protected]
Patch Changes
7a57c14,b2b5ee8,56a0d6e]: