release: v4.0.1 #114

Merged
yuris merged 1 commit from release/v4.0.1 into main 2026-08-22 11:41:29 +00:00
Owner

Bumps game.project and 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 connect no longer dies inside extension-websocket with Connection 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 at connection.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.lua and dev/test/crosscheck_v1.lua describe the v1 wire's removal and are left alone.

Bumps `game.project` and 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 `connect` no longer dies inside extension-websocket with `Connection 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 at `connection.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.lua` and `dev/test/crosscheck_v1.lua` describe the v1 wire's removal and are left alone.
release: v4.0.1
All checks were successful
ci / ci (pull_request) Successful in 1m28s
conformance / conformance (pull_request) Successful in 2m25s
7ed79c14e8
Holds frames issued before the socket opens (#113), so a call on the line
after `connect` no longer dies inside extension-websocket with
"Connection isn't connected" — an error 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.
Both examples already subscribed from inside the "connected" handler.

The historical "as of 4.0.0" notes in stdb/protocol_v2.lua and
dev/test/crosscheck_v1.lua are about the v1 wire's removal and stay as
they are.
yuris merged commit 8cdf78dcd5 into main 2026-08-22 11:41:29 +00:00
yuris referenced this pull request from a commit 2026-08-22 11:41:30 +00:00
Sign in to join this conversation.
No description provided.