chore(deps): update dependency miniflare to v3.20250718.0 #3388
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 contains the following updates:
3.20250408.0
->3.20250718.0
Release Notes
cloudflare/workers-sdk (miniflare)
v3.20250718.0
Compare Source
Patch Changes
#10019
cce7f6f
Thanks @dario-piotrowicz! - chore: update workerd dependency to latest#10035
028f689
Thanks @petebacondarwin! - Fix D1 SQL dump generation: escape identifiers and handle SQLite's dynamic typingEscape column and table names to prevent SQL syntax errors.
Escape values based on their runtime type to support SQLite's flexible typing.
v3.20250408.2
Compare Source
Patch Changes
#8681
7a57c14
Thanks @workers-devprod! - fix(miniflare): strip CF-Connecting-IP header from all outbound requests#9250
b2b5ee8
Thanks @workers-devprod! - fix: stripCF-Connecting-IP
header withinfetch
In v4.15.0, Miniflare began stripping the
CF-Connecting-IP
header via a global outbound service, which led to a TCP connection regression due to a bug in Workerd. This PR patches thefetch
API to strip the header during localwrangler dev
sessions as a temporary workaround until the underlying issue is resolved.#9211
56a0d6e
Thanks @petebacondarwin! - fix: ensure the fetch proxy message port is startedWhile Node.js will start the message port automatically when a
message
event listener is added,this diverges from the standard Web API for message ports, which require you to explicitly start
listening on the port.
v3.20250408.1
Compare Source
Patch Changes
#9055
fc04292
Thanks @CarmenPopoviciu! - chore: convert wrangler.toml files into wrangler.jsonc ones#9117
a01adca
Thanks @edmundhung! - fix: skip comment lines when parsingNODE_EXTRA_CA_CERTS
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.