Repository navigation
feat(void): use SQLite migrations for WebSockets - #314
Closed
TheAlexLichter wants to merge 1 commit into
Closed
TheAlexLichter wants to merge 1 commit into
TheAlexLichter wants to merge 1 commit into
Conversation
TheAlexLichter
force-pushed
the
feat/cloudflare-sqlite-websockets
branch
from
September 14, 2026 07:25
b87ce13 to
002a193
Compare
TheAlexLichter
force-pushed
the
feat/cloudflare-sqlite-websockets
branch
from
September 15, 2026 13:46
002a193 to
ef106b1
Compare
TheAlexLichter
marked this pull request as ready for review
September 15, 2026 20:53
Member
|
Thanks, I'm rebasing on main and cherry-picking. |
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
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.
This PR enables typed WebSocket routes on fresh and Workers Free accounts by using SQLite-backed Durable Objects.
It stores WebSocket migration history in wrangler.jsonc so Cloudflare remembers which routes were already deployed. When new routes are added later, Void creates a new migration instead of rewriting an old one.
Note: Existing legacy Durable Objects and user configuration remain unchanged.