release: v4.0.1 #114
No reviewers
Labels
No labels
area:defold
area:docs
area:infra
area:protocol
area:testing
kind:bug
kind:chore
phase:breadth
phase:core
phase:hardening
phase:slice
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
yuris/spacetimedb-defold!114
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "release/v4.0.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bumps
game.projectand the README install URL to v4.0.1.Ships #113: frames issued before the socket opens are held and flushed in order, so a call on the line after
connectno longer dies inside extension-websocket withConnection isn't connected— an error from a native module the caller did not write, naming neither this SDK nor readiness.A patch, not a minor. No API, option, or protocol-visible behaviour changed, and nothing in the repo asserted or relied on the old raise: no
docs/, README silent, and both examples already subscribed from inside the"connected"handler. The one observable change is that a too-early call's error now arrives on the handle or callback it already returns rather than raising at the callsite; the outcome still lands, per the invariant atconnection.lua:876.Reviewed over four passes; three found blocking issues, all fixed on #113 before merge. The historical "as of 4.0.0" notes in
stdb/protocol_v2.luaanddev/test/crosscheck_v1.luadescribe the v1 wire's removal and are left alone.