[petebacondarwin]

Backport the useful v1 runtime and fallback compatibility-date changes from #16403 and #16437. V1 calls getLocalWorkerdCompatibilityDate() and fills in a missing Worker compatibility date from the bundled workers-utils DEFAULT_COMPAT_DATE; it also runs development and preview through Miniflare. Moving the fallback from 2026-10-19 to 2026-10-23 therefore needs the matching runtime, rather than copying the removed workers-utils or workerd source.

Pin Miniflare 5.20261023.0-beta in all three retained consumers, Wrangler 4.153.0 in the plugin and its peer minimum, and Workers types 5.20261023.1 in the plugin and catalog. Align workers-utils 0.48.1 in all five direct consumers, plus containers-shared 0.23.3, deploy-helpers 0.23.1, and workers-auth 0.15.1. This keeps the bundled compatibility defaults and Wrangler's external helper types aligned; the preceding runtime backport already demonstrated a type-identity failure when retained helpers used an older workers-utils version. Preserve every private workspace:* reference. One plugin patch changeset describes the user-facing runtime/default-date update.

Stacked on the existing Hyperdrive backport #16407. Its useful proxy/session-cleanup changes remain in that parent, while the older runtime upgrades from merged #16379 remain earlier in history. This PR's independently remaining diff is six manifests, the types catalog and one plugin changeset. It does not change the plugin version, restore public SDK source/tests/fixtures, add a direct workerd dependency, or duplicate dependency tests.

Publication blocker: the exact intended versions above come from the current manifests in open release PR #16429. Miniflare, Wrangler and all four required helpers return npm HTTP 404. A real pnpm install --lockfile-only --ignore-scripts fails with ERR_PNPM_NO_MATCHING_VERSION for Miniflare 5.20261023.0-beta. Release #16429 now folds both original runtime/date changes into October 23; October 22 Miniflare was never published. Reuse this supplying backport for both originals, without a separate PR, test or changeset. The parent lockfile is preserved byte-for-byte, with no invented resolutions or integrity hashes. This draft cannot be installed with its intended dependencies yet and must not merge in this state.

Validation: the published parent dependencies were installed with a frozen offline install. Metadata checks and the genuine intended-version resolution attempt use the required Node 22.22.1 / pnpm 10.33.0. Draft formatting, changeset validation, exact-pin validation, whitespace checks and a full manifest audit pass: 72 manifests, 71 private statuses and 103 workspace references preserved; all three Miniflare pins and all five workers-utils pins agree. Build, types and runtime tests against the intended versions are blocked by publication; no successful runtime validation is claimed. After publication, regenerate the real lockfile, run pnpm build, pnpm check, pnpm test:ci, retained fixture suites and relevant plugin dev/preview checks before marking ready. The parent separately awaits live PostgreSQL/MySQL query validation.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows: verified release manifests and npm 404 responses, reproduced the pnpm resolution blocker, and passed draft metadata/workspace checks. Build, types and existing suites require published dependencies and remain pending.
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: this updates existing v1 runtime/default-date behavior; the plugin changeset describes the effect.

Note

This is a contribution from an AI agent: Codex, preparing maintainer-requested v1 backports.

[changeset-bot]

🦋 Changeset detected

Latest commit: 08d01f9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@cloudflare/vite-plugin	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[petebacondarwin]

@dependabot[bot] (recorded bot author of #16403) and @petebacondarwin (verified human ant-core approver), please check this Vite plugin v1 backport and approve it once it is ready and looks good.

V1 uses the bundled workers-utils fallback compatibility date and Miniflare for dev/preview. This adapts the original to intended pinned npm dependencies: Miniflare 5.20261022.0-beta, matching Wrangler/helpers and Workers types, with one plugin patch changeset. Earlier merged #16379 supplies the previous runtime; #16407 supplies the separate retained Hyperdrive changes. Private workspace references and intentional public-package removals are preserved.

This remains draft: the runtime/helper versions from pending release #16429 are unpublished (npm HTTP 404), so real pnpm lockfile regeneration and build/type/test validation must follow publication. Static checks pass; no runtime validation against the intended versions is claimed.

[petebacondarwin]

@dependabot[bot] (recorded bot author of #16437) and @edmundhung (verified human ant-core approver), please check this Vite plugin v1 backport and approve it once it is ready and looks good.

V1 uses the bundled workers-utils fallback compatibility date and Miniflare in dev/preview. Pending release #16429 now combines #16403 and #16437 into the October 23 runtime. This existing supplying backport advances to intended Miniflare 5.20261023.0-beta, Wrangler 4.153.0, Workers types 5.20261023.1, and fallback date 2026-10-23, keeping the coupled helper pins and one plugin patch changeset together. Earlier merged #16379 already supplies the previous published runtime, and parent #16407 supplies the separate retained Hyperdrive changes.

This remains draft: all six required runtime/helper releases return npm HTTP 404, and a real pnpm resolution attempt fails for the intended Miniflare version. Metadata checks pass; genuine lockfile regeneration and build/type/test validation must follow publication. Private workspace references and intentional public-source removals are preserved.