---
title: "miniflare 4.20260730.0: release notes, upgrades and advisories"
description: "miniflare 4.20260730.0: release notes, breaking changes by major version and 1 known advisory with their fix."
url: https://inlinr.com/packages/miniflare
lang: en
---

[Packages](https://inlinr.com/packages)

# miniflare

4.20260730.0 · 30 Jul 2026 MIT 57.5M / week [Repository](https://github.com/cloudflare/workers-sdk) [Homepage](https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare#readme) [npm](https://www.npmjs.com/package/miniflare) [Atom feed](https://inlinr.com/packages/feed/miniflare)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/miniflare/upgrade)

LineNewestSecurity

- 4.x 4.20260730.0 No known advisory Latest line
- 3.x 3.20250718.3 Safe from 3.20231030.2 [To 4.20260730.0](https://inlinr.com/packages/miniflare/upgrade/3.20250718.3-4.20260730.0)
- 2.x 2.14.4 No known advisory [To 4.20260730.0](https://inlinr.com/packages/miniflare/upgrade/2.14.4-4.20260730.0)
- 1.x 1.4.1 No known advisory [To 4.20260730.0](https://inlinr.com/packages/miniflare/upgrade/1.4.1-4.20260730.0)
- 0.x 0.20230908.0 No known advisory [To 4.20260730.0](https://inlinr.com/packages/miniflare/upgrade/0.20230908.0-4.20260730.0)

## Latest releases

[All 300 releases](https://inlinr.com/packages/miniflare/releases)

1. ### [4.20260730.0](https://inlinr.com/packages/miniflare/releases/4.20260730.0 "Open this release") [](https://github.com/cloudflare/workers-sdk/releases/tag/miniflare%404.20260730.0 "Read this release where it was published")  
30 Jul 2026

  - Add JSON output to `/cdn-cgi/handler/email`  
  The `/cdn-cgi/handler/email` endpoint now accepts `?format=json` to return the email handler result as JSON, including its outcome, rejection reason, forwarded messages, and replies. Requests without `format=json` still return the existing text outcome for backward compatibility.
  - Fix the local Images binding transform (`env.IMAGES.input(...).transform(...)`) ignoring the `fit`, `gravity`, and `background` options. Previously, local dev always letterboxed transformed images with black bars regardless of the options passed in. Local dev now respects `fit`, `gravity`, and `background`, matching production Images binding behavior.
  - Disable the keep-alive timeout on the loopback server  
  The loopback server (which serves custom service bindings, [@cloudflare/vite-plugin](https://inlinr.com/packages/@cloudflare/vite-plugin)'s module transport, and other workerd → Node callbacks) used Node's default `server.keepAliveTimeout` of 5 seconds. workerd pools and reuses connections to the loopback server, so Node closing an idle pooled socket raced with workerd sending the next request on it, making that request fail with `Network connection lost`. The failure is probabilistic and load-dependent; under [@cloudflare/vite-plugin](https://inlinr.com/packages/@cloudflare/vite-plugin) with a large SSR module graph and a cold optimizer cache (thousands of `fetchModule` calls with multi-second idle gaps between bursts), it broke most dev sessions. Disable the idle keep-alive timeout on the loopback server, mirroring the undici pools used for dispatch in the opposite direction.
2. ### [4.20260722.1](https://inlinr.com/packages/miniflare/releases/4.20260722.1 "Open this release") [](https://github.com/cloudflare/workers-sdk/releases/tag/miniflare%404.20260722.1 "Read this release where it was published")  
28 Jul 2026

  - Support passing V8 flags to `workerd` via the `MINIFLARE_WORKERD_V8_FLAGS` environment variable  
  The generated `workerd` config already supports `v8Flags`, but Miniflare never populated it, so the runtime always ran with V8's default heap limit (\~1.4 GB). Large dev applications (e.g. big SSR module graphs under [@cloudflare/vite-plugin](https://inlinr.com/packages/@cloudflare/vite-plugin), where each server-file edit grows the runner isolate's heap) can reach that limit, at which point `workerd` aborts with `V8 fatal error; location = Reached heap limit` and every subsequent `dispatchFetch()` fails with `fetch failed` until the dev server is manually restarted.  
  Setting e.g. `MINIFLARE_WORKERD_V8_FLAGS="--max-old-space-size=4096"` raises the limit and keeps long dev sessions alive. The variable follows the same space-separated format as `MINIFLARE_WORKERD_AUTOGATES`.
  - Add a local S3-compatible API for R2 buckets at `/cdn-cgi/local/r2/s3/<bucket-id>`, where `<bucket-id>` is the ID the bucket is configured with in the `r2Buckets` option  
  Buckets configured with `s3Credentials: { accessKeyId, secretAccessKey }` in `r2Buckets` are served over an S3-compatible HTTP API, authenticated with AWS Signature Version 4 (both `Authorization` header and presigned URL query authentication). Supported operations: GetObject, HeadObject, PutObject, CopyObject, DeleteObject, DeleteObjects, ListObjects, ListObjectsV2, HeadBucket, ListBuckets, CreateMultipartUpload, UploadPart, UploadPartCopy, CompleteMultipartUpload, and AbortMultipartUpload. Status codes, error responses, and unsupported-header screening mirror R2's S3 endpoint, including its static responses for bucket-configuration reads and its named errors for unimplemented operations.
  - Support `connect()` on remote VPC Network and VPC Service bindings in local development  
  Remote VPC Network and VPC Service bindings previously only supported HTTP and JSRPC, so calling `binding.connect(address)` against a private TCP service (for example a database) failed in local dev with `Incoming CONNECT on a worker not supported`. Raw TCP connections through remote VPC Network and VPC Service bindings now work in local development.  
  This feature is experimental. Existing HTTP and JSRPC usage of remote VPC Network and VPC Service bindings is unaffected, and no new configuration is required.
3. ### [4.20260722.0](https://inlinr.com/packages/miniflare/releases/4.20260722.0 "Open this release") [](https://github.com/cloudflare/workers-sdk/releases/tag/miniflare%404.20260722.0 "Read this release where it was published")  
23 Jul 2026

  - Add local-dev observability  
  `wrangler dev` and the Vite plugin now capture a trace for every local Worker invocation - spans, logs, and `console.*` output, including requests that cross worker or Durable Object boundaries.  
  You can explore this data two ways:  
  While this is in testing it's off by default; set `X_LOCAL_OBSERVABILITY=true` to turn it on. It will be on by default in the public release.
  - Fix incorrect byte limit reported in the local Queues batch-size error  
  When a queue batch exceeded the maximum batch byte size in local dev, the thrown `PayloadTooLargeError` hardcoded the limit as `256000`, even though the value actually enforced is `288000` bytes (`(256 + 32) * 1000`). The message now interpolates the real limit, consistent with the other Queue limit errors in the same file.
  - Recover local development after the Workers runtime crashes  
  Previously, an unexpected workerd crash left Miniflare running but unable to serve subsequent requests. Miniflare now restarts workerd after post-startup crashes, while continuing to surface startup crashes as fatal errors.  
  The Cloudflare Vite plugin also restarts the Vite development server after workerd recovers so its environments, hot channels, and module runners are recreated.

Dependency tracking

## Know when your own dependencies move

miniflare published 75 releases in the last 12 months. inlinr folds the routine ones into a line and keeps the few that need you.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

[Details](https://inlinr.com/packages/miniflare/security)

- [Miniflare vulnerable to Server-Side Request Forgery (SSRF)](https://inlinr.com/advisories/GHSA-fwvg-2739-22v7) High · fixed in 3.20231030.2

## Health of 4.20260730.0

[Details](https://inlinr.com/packages/miniflare/security#signals)

- **Provenance**: Present
- **Publisher**: GitHub Actions
- **Maintainers**: 1
- **Scorecard**: None
- **Size**: 23.1 MB

## Weekly downloads

## Same family

- [wrangler 49.4M/wk](https://inlinr.com/packages/wrangler)
- [@cloudflare/unenv-preset 43.8M/wk](https://inlinr.com/packages/@cloudflare/unenv-preset)
- [@cloudflare/vite-plugin 12.3M/wk](https://inlinr.com/packages/@cloudflare/vite-plugin)
- [@cloudflare/vitest-plugin 3M/wk](https://inlinr.com/packages/@cloudflare/vitest-plugin)
- [@cloudflare/workers-utils 2.7M/wk](https://inlinr.com/packages/@cloudflare/workers-utils)
- [@cloudflare/config 2.2M/wk](https://inlinr.com/packages/@cloudflare/config)
- [@cloudflare/workers-auth 587.6k/wk](https://inlinr.com/packages/@cloudflare/workers-auth)
- [@cloudflare/cli-shared-helpers 16.6k/wk](https://inlinr.com/packages/@cloudflare/cli-shared-helpers)

Registry facts last checked 18 Nov 2026\. Releases and advisories last read 22 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
