[workers-devprod]

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 main, this PR will be updated.

Releases

miniflare@5.20261023.1-beta

Minor Changes

• #16494 0968b08 Thanks @petebacondarwin! - Enable Miniflare's development registry by default and centralize path resolution

  In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH, then the unsafeDevRegistryPath constructor option, then <Cloudflare config directory>/dev-registry/v5. The default is independent of legacy Wrangler directories and is scoped to the Miniflare major version. The Vite v2 beta plugin follows this new default, while current Wrangler and getPlatformProxy() retain Wrangler's legacy default for compatibility with existing Wrangler sessions. Vite v2 and Wrangler therefore require the same CLOUDFLARE_DEV_REGISTRY_PATH to discover each other; set it for both processes when mixing these tools.

  Add enableDevRegistry: false to disable registration and discovery explicitly. Shared storage now uses the resolved default without requiring an explicit path. As before, shared storage requires an enabled registry to elect a storage owner, so combining unsafeEnableSharedStorage: true with enableDevRegistry: false is rejected. Miniflare no longer reads MINIFLARE_REGISTRY_PATH; use CLOUDFLARE_DEV_REGISTRY_PATH instead. Expose resolveDevRegistryPath() for integrations that also read registry files. Wrangler uses the effective path for its runtime configuration, initial bindings display, and Flagship active-session check, so the canonical override cannot bypass that check. An explicitly disabled Wrangler registry remains disabled.

Patch Changes

• #16499 f3c13b3 Thanks @dinasaur404! - Preserve binding error codes and names in local development

  Errors from remote bindings and from Node.js binding proxies (getPlatformProxy() and Miniflare#getBindings()) now keep their machine-readable properties, such as Artifacts' code and numericCode. Previously these properties were dropped and the error name was folded into the message (for example "ArtifactsError: Repository not found"), so code could only branch on error text during local development.

  Node.js callers also keep custom error names such as ArtifactsError. Errors from remote bindings received inside a Worker keep their properties but are still named Error.

@cloudflare/vite-plugin@2.0.0-beta.v.6

Minor Changes

• #16494 0968b08 Thanks @petebacondarwin! - Enable Miniflare's development registry by default and centralize path resolution

  In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH, then the unsafeDevRegistryPath constructor option, then <Cloudflare config directory>/dev-registry/v5. The default is independent of legacy Wrangler directories and is scoped to the Miniflare major version. The Vite v2 beta plugin follows this new default, while current Wrangler and getPlatformProxy() retain Wrangler's legacy default for compatibility with existing Wrangler sessions. Vite v2 and Wrangler therefore require the same CLOUDFLARE_DEV_REGISTRY_PATH to discover each other; set it for both processes when mixing these tools.

  Add enableDevRegistry: false to disable registration and discovery explicitly. Shared storage now uses the resolved default without requiring an explicit path. As before, shared storage requires an enabled registry to elect a storage owner, so combining unsafeEnableSharedStorage: true with enableDevRegistry: false is rejected. Miniflare no longer reads MINIFLARE_REGISTRY_PATH; use CLOUDFLARE_DEV_REGISTRY_PATH instead. Expose resolveDevRegistryPath() for integrations that also read registry files. Wrangler uses the effective path for its runtime configuration, initial bindings display, and Flagship active-session check, so the canonical override cannot bypass that check. An explicitly disabled Wrangler registry remains disabled.

Patch Changes

• #15659 8d98a15 Thanks @dedsec-terminal! - Fix Vite DevTools WebSocket connections closing unexpectedly

  Leave upgrades at /__devtools/__ws to Vite DevTools instead of forwarding them to the Worker. Sandbox preview requests continue to reach the Worker.

• Updated dependencies [0968b08, f3c13b3]:

  • miniflare@5.20261023.1-beta
  • @cloudflare/runtime-types@0.1.17

wrangler@4.154.0

Minor Changes

• #16494 0968b08 Thanks @petebacondarwin! - Enable Miniflare's development registry by default and centralize path resolution

  In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH, then the unsafeDevRegistryPath constructor option, then <Cloudflare config directory>/dev-registry/v5. The default is independent of legacy Wrangler directories and is scoped to the Miniflare major version. The Vite v2 beta plugin follows this new default, while current Wrangler and getPlatformProxy() retain Wrangler's legacy default for compatibility with existing Wrangler sessions. Vite v2 and Wrangler therefore require the same CLOUDFLARE_DEV_REGISTRY_PATH to discover each other; set it for both processes when mixing these tools.

  Add enableDevRegistry: false to disable registration and discovery explicitly. Shared storage now uses the resolved default without requiring an explicit path. As before, shared storage requires an enabled registry to elect a storage owner, so combining unsafeEnableSharedStorage: true with enableDevRegistry: false is rejected. Miniflare no longer reads MINIFLARE_REGISTRY_PATH; use CLOUDFLARE_DEV_REGISTRY_PATH instead. Expose resolveDevRegistryPath() for integrations that also read registry files. Wrangler uses the effective path for its runtime configuration, initial bindings display, and Flagship active-session check, so the canonical override cannot bypass that check. An explicitly disabled Wrangler registry remains disabled.

Patch Changes

• #16499 f3c13b3 Thanks @dinasaur404! - Preserve binding error codes and names in local development

  Errors from remote bindings and from Node.js binding proxies (getPlatformProxy() and Miniflare#getBindings()) now keep their machine-readable properties, such as Artifacts' code and numericCode. Previously these properties were dropped and the error name was folded into the message (for example "ArtifactsError: Repository not found"), so code could only branch on error text during local development.

  Node.js callers also keep custom error names such as ArtifactsError. Errors from remote bindings received inside a Worker keep their properties but are still named Error.

• Updated dependencies [0968b08, f3c13b3]:

  • miniflare@5.20261023.1-beta

@cloudflare/deploy-helpers@0.24.1

Patch Changes

• Updated dependencies [0968b08, f3c13b3]:
  • miniflare@5.20261023.1-beta

@cloudflare/pages-shared@0.13.203

Patch Changes

• Updated dependencies [0968b08, f3c13b3]:
  • miniflare@5.20261023.1-beta

@cloudflare/runtime-types@0.1.17

Patch Changes

• Updated dependencies [0968b08, f3c13b3]:
  • miniflare@5.20261023.1-beta

@cloudflare/vitest-plugin@1.4.9

Patch Changes

• Updated dependencies [0968b08, f3c13b3]:
  • miniflare@5.20261023.1-beta
  • wrangler@4.154.0

@cloudflare/remote-bindings@0.0.54

Patch Changes

• Updated dependencies [0968b08, f3c13b3]:
  • miniflare@5.20261023.1-beta
  • @cloudflare/deploy-helpers@0.24.1

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[clanky-the-clanker]

✅ Approved — This is a mechanical Changesets release. It removes the three consumed changesets, adds CHANGELOG entries, and bumps only the version fields, which match the release notes in the description. No issues found.

_{The decision is advisory: this comment never approves, blocks or requests changes on the pull request.}

---

✅ All checks passed

🚀 Release: ✅ LGTM

Risk: Low. The changesets were consumed cleanly. Dependent packages (deploy-helpers, pages-shared, runtime-types, vitest-plugin, remote-bindings) got patch bumps for the miniflare and wrangler updates.

---

🔒 Security: ✅ LGTM

No security-relevant code changes. The pull request contains only version metadata and changelog text.

---

📖 AGENTS.md: ✅ LGTM

No AGENTS.md changes, and nothing in this release pull request makes the existing guidance stale.

---

📋 Code Quality: ✅ LGTM

The eight package.json changes touch only the version field. Each new version matches the release notes in the pull request description, for example miniflare 5.20261023.0-beta → 5.20261023.1-beta, wrangler 4.153.0 → 4.154.0 and @cloudflare/vite-plugin 2.0.0-beta.v.5 → 2.0.0-beta.v.6.

---

⚡ Performance: ✅ LGTM

No runtime code changes.

---

📝 Documentation: ✅ LGTM

The CHANGELOG entries match the consumed changesets and list the dependency updates.

---

_{Reviewed commit: e5f3b6c1}

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@16500

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@16500

@cloudflare/codemods

npm i https://pkg.pr.new/@cloudflare/codemods@16500

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@16500

@cloudflare/containers-shared

npm i https://pkg.pr.new/@cloudflare/containers-shared@16500

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@16500

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@16500

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@16500

miniflare

npm i https://pkg.pr.new/miniflare@16500

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@16500

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@16500

@cloudflare/runtime-types

npm i https://pkg.pr.new/@cloudflare/runtime-types@16500

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@16500

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@16500

@cloudflare/vitest-plugin

npm i https://pkg.pr.new/@cloudflare/vitest-plugin@16500

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@16500

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@16500

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@16500

wrangler

npm i https://pkg.pr.new/wrangler@16500

commit: e5f3b6c