chore: bump effect to 4.0.0-beta.99, alchemy to 2.0.0-beta.63#30
Merged
Conversation
- effect 4.0.0-beta.78 -> 4.0.0-beta.99 (root + all workspace packages) - alchemy 2.0.0-beta.52 -> 2.0.0-beta.63 (root + worker) - @effect/platform-node, @effect/platform-bun, @effect/vitest -> 4.0.0-beta.99 - Alchemy API renames: Cloudflare.DurableObjectNamespace -> Cloudflare.DurableObject, Cloudflare.DurableWebSocket -> Cloudflare.WebSocket - Re-create the @distilled.cloud/core empty-2xx-body guard (alchemy-run/distilled#344, still unmerged) against 0.29.1 (was 0.23.1); patched both src/client.ts (bun condition) and lib/client.js (default condition). 0.29.1 reclassifies the empty-body decode failure as a retryable TransportError, but the retry re-issues the DELETE and can still abort a deploy/destroy, so the guard is still needed. - Fix a pre-existing integration-test expectation: a plain GET /api/ws hits the 426 upgrade-check branch before the session-id check (broken since PR #6; CI does not run test:integration) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UnK7wXkmdGSShX5AA1TevY
|
🚀 Preview deployed: https://preview-30.tablo.run |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Dependency bump across the workspace, verified locally (typecheck, unit tests, integration suite on local workerd, build, verify:pwa).
API renames (alchemy beta.52 → beta.63)
Cloudflare.DurableObjectNamespace<X>()→Cloudflare.DurableObject<X>()(both DOs)Cloudflare.DurableWebSocket→Cloudflare.WebSocket(session handlers)Patch re-created against @distilled.cloud/core 0.29.1
alchemy@2.0.0-beta.63 pins @distilled.cloud/*@0.29.1, so the empty-2xx-body guard (alchemy-run/distilled#344, still unmerged as of 2026-07-19) is re-created against 0.29.1. Verified the bug is still present: 0.29.1 now turns the empty-body decode failure into a retryable TransportError, but the retry re-issues the DELETE and the operation can still fail — the guard (mirroring the 204 branch) remains the durable fix. Patched both
src/client.ts(bun export condition, whatbunx alchemyruns) andlib/client.js(default condition).Drive-by test fix
packages/worker/test-integration/stack.test.ts: the plain-GET/api/wstest expected 400, but the 426 upgrade-check branch (added in #6) runs before the session-id check, so the test could never pass — broken on main unnoticed because CI doesn't runtest:integration. Now expects 426; suite is 3/3 green locally.🤖 Generated with Claude Code
https://claude.ai/code/session_01UnK7wXkmdGSShX5AA1TevY