Skip to content

chore(cloudflare-runtime): bump internal isolate compatibility dates - #1380

Open
sam-goodwin wants to merge 4 commits into
mainfrom
chore/cloudflare-runtime-compat-date
Open

chore(cloudflare-runtime): bump internal isolate compatibility dates#1380
sam-goodwin wants to merge 4 commits into
mainfrom
chore/cloudflare-runtime-compat-date

Conversation

@sam-goodwin

Copy link
Copy Markdown
Contributor

Pin every internal workerd isolate and the Vite/platform-proxy defaults to 2026-07-04, the newest date catalog workerd 1.20260704.1 supports.

export const INTERNAL_WORKER_COMPATIBILITY_DATE = "2026-07-04";

That constant now drives the queue broker, workflows engine, assets/router, KV, R2, D1, cache, secrets store, browser, send-email, images, stream, loopback, entry, worker proxy, registry proxy, and remote-binding isolates.

enable_ctx_exports is omitted on the asset/router workers — it is default-on as of 2025-11-17.

Pin every local isolate and the Vite/platform-proxy defaults to 2026-07-04, the newest date catalog workerd 1.20260704.1 supports.
…-open

The Vite plugin bundle imports the shared compatibility date via a
package subpath that was not exported. Browser CDP proxying also needs
half-open sockets now that auto-reply-to-close is default-on.
CDP proxying still needs the pre-2026-04-07 close handshake. allowHalfOpen
alone did not stop reconnect/session-lifecycle tests from hanging.
Reconnect and Browser.close session cleanup hang after 2026-04-07.
Keep this isolate on 2025-01-01 until the CDP proxy can take the new handshake.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant