@urun-sh/core 0.1.32 → 0.1.34

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.33
+
+- Stale-`ws_url` reconnect fix: after a bounded number of consecutive failures dialing the cached `ws_url`, the transport re-resolves the current connect handle from the control plane and dials the fresh host (resolve-then-dial, with backoff, bounded) — sessions re-allocated to a new GameServer now reattach instead of spinning on the dead host forever.
+- Reconnect retries are bounded: the budget resets only after a connection stays up, and failed redials schedule the next bounded episode instead of dying silently.
+- New typed `reconnecting` member on `TransportState` plus a `stateChange` transport event for rendering the connection lifecycle.
+- `ChannelMultiplexer` ignores binary doc-sync (yjs) frames instead of warning "Failed to parse WebSocket message as JSON" on every frame.
+- Argument purity: invocation args can no longer influence allocation (`gpus` in the create body is a constant wire-compat filler of `1`, required by the deployed control-plane validator; dropped in 0.2.0).
+
 ## 0.1.32
 
 - Control-doc sync now speaks the Yjs sync protocol (raw binary update frames) over the signaling WebSocket — the same protocol/doc engine the session server shares with the runtime on `/internal/docs/{sessionId}` — replacing the bespoke JSON `doc_update` fallback, which the server rejected as "malformed message" (control updates were silently lost whenever that path was used). `session.doc("control")` is now a Yjs doc mirroring the server's control doc (root map `session`); reads/writes/`change` events keep the exact same JSON API. Requires a session server with binary doc-sync support on the signaling WS (the SDK opts in by sending a binary hello; servers without support simply reject it as malformed and the SDK behaves no worse than before).