@voltro/runtime 0.62.3 → 0.63.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -39,6 +39,20 @@ _Changes staged for the next release accumulate here (rolled up from
39
39
 
40
40
  ---
41
41
 
42
+ ## [0.63.0] — 2026-09-03
43
+
44
+ ### ⚠ BREAKING
45
+
46
+ - **@voltro/client, @voltro/runtime, @voltro/cli, @voltro/web, @voltro/react-native** — Short transport gaps now have one bounded recovery contract. Raw diagnostics remain immediate, while `useConnectionStatus` exposes `recovering` during a configurable grace window and `useOnRpcError` emits exactly one visible transport failure only if the gap remains open. Same-subject runtime swaps keep subscription bases, revisions and optimistic patches; subject changes discard them. Interrupted mutations report `outcome: unknown` and replay once with the same key only after the deployed API proves that server idempotency is active. The codemod explains the new status member and the raw versus presentation error channels.
47
+
48
+ **`voltro update` carries you across this** — codemod `0.63.0/01_recovery-presentation`. If you pin versions by hand and never run it, print the notes without changing anything: `voltro update --codemods-only --from <your current version> --dry-run` (this one ships in 0.63.0).
49
+
50
+ ### Fixed
51
+
52
+ - **@voltro/database, @voltro/sql-turso, @voltro/sql-sqlite, @voltro/sql-mssql** — Framework-table evolution now converges under real SQLite and both local Turso transports, and has a live MSSQL fixture. The new Turso runs also fixed internal table protection, boolean/number introspection normalization, and case-insensitive SQLite-family index-name comparison. The MSSQL fixture exposed and fixes a second convergence bug: unbounded text that MSSQL auto-bounds for an index is now rendered and compared with the same indexed-column rule, so a second plan no longer tries to widen an indexed `NVARCHAR(450)` to `NVARCHAR(MAX)`.
53
+
54
+ ---
55
+
42
56
  ## [0.62.3] — 2026-09-03
43
57
 
44
58
  ### Added
package/dist/index.d.ts CHANGED
@@ -8798,6 +8798,10 @@ export declare interface RpcServerOptions<Rpcs extends Rpc.Any> {
8798
8798
  */
8799
8799
  readonly host?: string;
8800
8800
  readonly path?: `/${string}`;
8801
+ /** Whether WS mutations are durably idempotent. Exposed as a non-secret
8802
+ * runtime capability so clients replay only when the deployed server proves
8803
+ * the same key will be deduplicated. */
8804
+ readonly mutationReplay?: boolean;
8801
8805
  /** Non-sensitive fleet identity written on the rpc WebSocket open/close
8802
8806
  * records. Defaults to the process identity resolver (POD_NAME/HOSTNAME).
8803
8807
  * Embedders may state it explicitly when they own process identity. */