@robota-sdk/agent-transport-ws 3.0.0-beta.99 → 3.0.1

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.
Files changed (2) hide show
  1. package/CHANGELOG.md +393 -0
  2. package/package.json +6 -6
package/CHANGELOG.md CHANGED
@@ -1,5 +1,398 @@
1
1
  # @robota-sdk/agent-transport-ws
2
2
 
3
+ ## 3.0.1
4
+ ### Patch Changes
5
+
6
+ - @robota-sdk/agent-core@3.0.1
7
+ - @robota-sdk/agent-interface-analytics@3.0.1
8
+ - @robota-sdk/agent-interface-session@3.0.1
9
+ - @robota-sdk/agent-interface-transport@3.0.1
10
+ - @robota-sdk/agent-transport@3.0.1
11
+
12
+ ## 3.0.0
13
+ ### Major Changes
14
+
15
+ - e82215f: **ARCH-011: replace the ambiguous transport lifecycle stub with executable conformance.**
16
+
17
+ `ITransportAdapter` now requires a frozen `service | runner` lifecycle descriptor. `start()` resolves
18
+ at the concrete transport's documented readiness boundary; start before attach and repeated active
19
+ start reject a stable lifecycle error, repeated stop is safe, and stopped adapters can reattach and
20
+ restart.
21
+
22
+ Runner adapters launch separately and expose a typed terminal outcome through
23
+ `waitForCompletion()`. The registry accepts base adapters, rejects duplicate names, keeps
24
+ configuration as an optional capability, returns complete ordered records whose pending slots become
25
+ registry-owned `abandoned` outcomes on stop/rollback, and exposes a real-runner-only first-failure
26
+ wait. It serializes startup/stop, rejects active restart before mutation, and reverses partial startup
27
+ from the currently failing adapter with typed safe rollback details. Runtime host and serve mode
28
+ propagate real nonzero runner results without treating normal shutdown abandonment as failure.
29
+
30
+ HTTP, MCP, both WebSocket adapters, WebRTC, and headless invoke one shared public conformance kit.
31
+ The former `TuiTransport` export is removed because it ignored the attached session; use `renderApp`
32
+ or `TuiInteractionChannel`, which honestly own their session lifecycle.
33
+
34
+ ### Minor Changes
35
+
36
+ - 6ae3f28: A served runtime can list its workspace's sessions, start a new one and switch to another without the
37
+ process or any client connection restarting. The GUI shows them in a sessions sidebar.
38
+
39
+ - `agent-interface-session` is **`major`** for two reasons:
40
+ - It adds `ISessionListing`, `ISessionDirectory` and `ISessionSwitchedEvent`.
41
+ - `IInteractiveSessionEvents` gains a required `session_switched` event. An exhaustive map over the
42
+ event names stops compiling until it classifies the new event.
43
+ - `agent-transport` is **`major`** for the same kind of reason:
44
+ - It adds the wire messages `list-sessions` → `sessions`/`sessions_error`, `new-session`,
45
+ `switch-session`, and the broadcast `session_switched`.
46
+ - It adds a `sessionDirectory` handler option. A refusal to switch comes back as a
47
+ `protocol_error` carrying the reason.
48
+ - An exhaustive map over message types must add the new variants.
49
+ - `agent-transport-ws` passes a configured `sessionDirectory` to every connection.
50
+ - `agent-framework` is **`major` because `IRuntimeHostHandle.session` is now a `SessionSlot`**, not the
51
+ `InteractiveSession`, and `bindTransports` receives the slot.
52
+ - The slot is an `IInteractiveSession` that forwards to the current session. Members outside that
53
+ interface are read through `host.session.current`, which changes on a switch.
54
+ - Adds `InteractiveSession.whenInitialized()`.
55
+ - Exports `listUnreadableSessions`.
56
+ - `agent-ui-web` is **`major`**:
57
+ - `IWsSessionState` gains session listing state and actions.
58
+ - It adds a `SessionSidebar`.
59
+ - `/resume` opens the sidebar.
60
+ - `agent-cli`: `robota --serve` provides the session directory, and refuses a switch that would lose
61
+ work in progress. External-event grants belong to the run: a switch reopens them on the new session,
62
+ as the TUI already does.
63
+ - External-event grant history (spent tokens, rate windows, revocations) belongs to the run. The new
64
+ option `externalEventGrantHistory` (from `createExternalEventGrantHistory()`) is shared by every
65
+ session that a served runtime or the TUI builds. A session switch therefore replays no spent token
66
+ and resets no rate limit. The TUI previously had this gap when it switched sessions.
67
+ - 57f57f5: A daemon keeps several sessions live, and each client is bound to its own: one client's switch moves
68
+ only that client.
69
+
70
+ - `agent-interface-session`: `ISessionBinder`/`ISessionBinding`, the session-change refusal codes with
71
+ `isSessionChangeRefusal`, and listing rows that may say `live` and `clients`.
72
+ - `agent-framework`: `SessionPool` and `SessionChangeRefusal`.
73
+ - `agent-transport` (**major**): a new server frame, `session_change_failed`, which an exhaustive
74
+ consumer must handle. A refused `new-session` or `switch-session` now answers with it, carrying a
75
+ `code`, instead of `protocol_error`; both requests take an optional `requestId` that it echoes.
76
+ - `agent-transport-ws`: the `sessionBinder` option binds each connection to its own session and
77
+ releases the binding when the connection closes.
78
+ - `agent-cli`: `robota --serve` and the daemon keep up to four sessions live. Each WebSocket client and
79
+ attached terminal is bound to its own session; leaving a busy session is no longer refused, and only
80
+ the last driver of a session with a pending prompt is kept from leaving it. Grants and the supervised
81
+ name stay on the runtime's first session, and its reported activity covers every live session.
82
+ - `agent-ui-web`: a refused new or switch shows the host's reason as a notice (an older host's
83
+ `protocol_error` still does); the session sidebar marks live sessions and counts the other clients
84
+ on each; after a reconnect to a host that keeps sessions live, the GUI returns to the session it was on.
85
+ - `agent-ui-terminal`: an attached terminal shows why a switch was refused, and the picker's switch
86
+ stays pending until the host answers; the session picker marks live sessions and their clients.
87
+ - 9db63ee: Add named session capability roles and explicit capability-host queries while preserving the legacy
88
+ `IInteractiveSession` interface shape. HTTP, MCP, protocol, WS, WebRTC, and headless transports now
89
+ declare only the session roles they consume, and the direct aggregate-cast floor is zero.
90
+ - 2ebff01: Emit the complete persisted checkpoint and branch lifecycle, forward plan, context-refresh, and
91
+ branch events through protocol transports, and render deterministic bounded notices in the TUI.
92
+ Transport-owned delivery failures now enter the owning carrier cleanup lifecycle without reversing
93
+ an already-committed session operation.
94
+ - 5c5ff23: TRANS-001: payload-agnostic transport — opaque binary frames + consumer-declared event types
95
+
96
+ The WS transport now carries **arbitrary payloads** alongside the text-agent protocol on one
97
+ connection, instead of forcing every app-level payload through the `text_delta`/`submit` wire
98
+ protocol.
99
+
100
+ - `agent-interface-transport` adds the channel contracts (`IBinaryFrame`, `IChannelEventFrame`,
101
+ `IChannelDescriptor`, `IPayloadChannel`, `IPayloadChannelHost`, `TChannelEventMap`,
102
+ `TChannelFrame`, `TChannelReceiveResult`). Content-neutral carrier mechanics — no payload domain.
103
+ - `agent-transport-protocol` adds the pure channel frame codec (`encodeBinaryFrame`,
104
+ `encodeChannelEventFrame`, `decodeChannelFrame`, `isChannelFrame`). `TClientMessage` /
105
+ `TServerMessage` are unchanged.
106
+ - `agent-transport-ws` becomes a carrier that routes by WebSocket frame opcode — TEXT to the
107
+ text-agent protocol profile, BINARY to consumer-declared channels — and `WsTransport` now
108
+ implements `IPayloadChannelHost` (`registerChannel`). `PayloadChannelRegistry` is exported.
109
+
110
+ Additive only: existing transports, consumers, and the agent wire protocol are untouched.
111
+
112
+ ### Patch Changes
113
+
114
+ - 57280bf: Every published package now declares `"engines": { "node": ">=22.12.0" }`. Before, 27 of the 38
115
+ packages declared no floor (`agent-core`, `agent-tools` and every provider among them),
116
+ `agent-session` and `agent-file-authority` declared `>=20.19.0`, and the other nine declared
117
+ `>=22.0.0`, so a consumer on Node 20 saw at most a warning from a transitive dependency.
118
+
119
+ Why 22.12: `agent-cli` and `agent-ui-terminal` need Node 22 through `ink` 7, and the CommonJS entries
120
+ of `agent-tools` and its dependents, `agent-transport`/`node` and its dependents, and
121
+ `agent-ui-terminal` `require()` ESM-only dependencies (`p-limit`, `jose`, `chalk`), which Node 22
122
+ supports unflagged only from 22.12. `engines` is advisory unless the consumer enables `engine-strict`.
123
+
124
+ No code changes: `tsdown` now reads `node22.12.0` as its build target from the field.
125
+ - 18c0d5c: Every published package now exports `./package.json`, so `require('<package>/package.json')` and
126
+ `import('<package>/package.json', { with: { type: 'json' } })` work instead of failing with
127
+ `ERR_PACKAGE_PATH_NOT_EXPORTED`, and each tarball now ships the package's `CHANGELOG.md`.
128
+ - 2c612ba: Release the migrated Robota product with its public SDK namespace, robota command, compatible SDK exports, internal product configuration, and verified CLI startup and delivery corrections.
129
+ - 235da81: **BREAKING — ARCH-030: `createWsHandler` takes the carrier's delivery boundary, not a raw `send`.**
130
+
131
+ `createWsHandler` had two outbound semantics on one connection. The session-event fan-out went through
132
+ a guard that reported carrier failures through `onDeliveryError`; every reply to an inbound frame got
133
+ the raw `send`. Eleven reply families were unguarded — five resolving from a Promise continuation, so a
134
+ reply landing after a disconnect escaped as an **unhandled rejection** while the carrier's cleanup was
135
+ never notified, and six synchronous ones that threw into the carrier's inbound listener instead.
136
+
137
+ `IWsHandlerOptions` now takes a single `deliver: TOutboundDeliver` in place of `send` and
138
+ `onDeliveryError`. **The carrier builds the boundary** from its own sink and its own failure policy and
139
+ passes it down — not the reverse, because a protocol layer handed a raw sink so it can hand a wrapper
140
+ back leaves the raw sink reachable, which is how the twelfth reply family gets added unguarded.
141
+
142
+ ```ts
143
+ // before
144
+ const { onMessage, cleanup } = createWsHandler({
145
+ session,
146
+ send: (msg) => ws.send(JSON.stringify(msg)),
147
+ onDeliveryError: (error) => ws.close(1011, error.message),
148
+ });
149
+
150
+ // after
151
+ const deliver = createOutboundDelivery(
152
+ (msg) => ws.send(JSON.stringify(msg)),
153
+ (error) => ws.close(1011, error.message),
154
+ );
155
+ const { onMessage, cleanup } = createWsHandler({ session, deliver });
156
+ ```
157
+
158
+ `TOutboundDeliver` is branded and `createOutboundDelivery` is its only producer, so a plain
159
+ `(message: TServerMessage) => void` is refused by the compiler wherever a boundary is required.
160
+
161
+ **The boundary latches:** it reports at most one delivery failure per connection, after which frames are
162
+ dropped without a further report. All three carriers already treated a delivery failure as terminal and
163
+ each had grown its own latch; it belongs upstream of all three. `SessionResumeBridge` builds a fresh
164
+ boundary per `attach`, which is what un-latches the session after a reconnect, and buffers a frame
165
+ before the boundary so a dropped one still replays.
166
+
167
+ **`ISubscribeSessionEventsOptions` is no longer exported** from the package barrel. It is the options bag
168
+ of `subscribeSessionEvents`, which is package-internal, and it was already absent from the SPEC's public
169
+ API table. Its `onDeliveryError` member is gone regardless — carrier-failure containment is the
170
+ boundary's job now.
171
+
172
+ `agent-transport-ws` and `agent-transport-webrtc` are `patch`: `WsSessionDelivery` (whose raw `send` is
173
+ now private, with `deliver` the only public sink) and `PairingGate` are not on their packages' barrels,
174
+ and every barrel export of both packages keeps its signature.
175
+ - 4f3c075: Assemble complete, verified package generations before switching build output; preserve the previous generation on build failure and pack only verified regular-file images. Include copied CLI web assets in affected-build ordering and artifact transfer. Preserve the CLI version in managed build paths. Public runtime contracts remain compatible (patch).
176
+ - 94cc355: REMOTE-002 Stage A: extract the transport-neutral session bridge + wire protocol into a new
177
+ `@robota-sdk/agent-transport-protocol` package (`createWsHandler`, `TClientMessage`/`TServerMessage`); repoint
178
+ `agent-transport-ws` and `agent-web-ui` at it (no pass-through re-export). Add a new
179
+ `@robota-sdk/agent-transport-webrtc` package: a `WebRtcTransport` (`IConfigurableTransport`, `defaultEnabled:false`)
180
+ that carries an `IInteractiveSession` over an `RTCDataChannel` reusing the shared handler, with a lazily-loaded
181
+ optional `werift` peer dependency that throws an explicit "WebRTC transport unavailable" error on absence (never a
182
+ silent no-op). No user-facing enable path and no auth in Stage A (that lands in Stage B); the transport is proven
183
+ by an in-process loopback data-channel round-trip only.
184
+
185
+ (Bump target corrected during REL-023 triage: `@robota-sdk/agent-web-ui` was dissolved by GUI-006 (#1141, 2026-07-12) before this work was ever published; its protocol-consumer role now lives in `@robota-sdk/agent-transport-webrtc-web`.)
186
+ - 9c6a8db: The wire protocol gained several request/reply pairs so a GUI never has to scrape command output for
187
+ data it can read directly.
188
+
189
+ `get-settings`/`update-settings` read and write the Settings screen; a patch applies through the same
190
+ function its matching slash command uses, so the two paths cannot drift. `list-models` returns the
191
+ configured models grouped by provider profile, with the current profile and model. `get-agent-definitions`
192
+ returns the agent switcher's roster and current selection. `project-status`, `project-diff` and
193
+ `project-memory` back the Project panel's git status, one file's diff, and project memory; a host
194
+ without this capability answers `protocol_error` instead of hanging. `rename-session` and
195
+ `delete-session` rename or remove a stored session from the list, current or not, each with its own
196
+ success/failure reply.
197
+
198
+ The `messages` frame gained an optional `display` field — the same history projected into display
199
+ segments (text runs and finished tool calls, diffs included) — and the connection's own `driverId`, so
200
+ a reload, reconnect or resume shows tool rows and tells a co-driver's turns from its own. The `error`
201
+ frame gained optional `code`, `provider`, `retryAfterSeconds` and `model` fields so a renderer can say
202
+ what kind of failure happened (`auth`, `rate_limit`, `model_unavailable`, `network`, `provider`) instead
203
+ of showing only raw text; a session error this classification does not recognize is unchanged.
204
+
205
+ `TCommandSurfaceLocality` names whether a `'remote'`-sourced command is provably on this machine. The
206
+ WebRTC/device-mesh transport now forwards `'remote'` for it (it proves no locality, the same rule
207
+ already applied to pairing), and both the WS and WebRTC transports forward it into the Settings
208
+ read/write path, so a command that refuses a remote surface (installing a plugin) refuses identically
209
+ regardless of which transport carried it.
210
+ - Updated dependencies [7b6234c]
211
+ - Updated dependencies [37b4bd7]
212
+ - Updated dependencies [4eea54b]
213
+ - Updated dependencies [50d2c9f]
214
+ - Updated dependencies [3c81769]
215
+ - Updated dependencies [724fabb]
216
+ - Updated dependencies [d877de2]
217
+ - Updated dependencies [d61e159]
218
+ - Updated dependencies [bfe8ed5]
219
+ - Updated dependencies [1698be4]
220
+ - Updated dependencies [a5961c9]
221
+ - Updated dependencies [d4189b9]
222
+ - Updated dependencies [9edae52]
223
+ - Updated dependencies [4078a72]
224
+ - Updated dependencies [4c73a0b]
225
+ - Updated dependencies [196a900]
226
+ - Updated dependencies [f336838]
227
+ - Updated dependencies [34e50f0]
228
+ - Updated dependencies [722e88a]
229
+ - Updated dependencies [d23c848]
230
+ - Updated dependencies [3038eb7]
231
+ - Updated dependencies [02b7452]
232
+ - Updated dependencies [e689c8e]
233
+ - Updated dependencies [ec5e477]
234
+ - Updated dependencies [c7f9203]
235
+ - Updated dependencies [7b72344]
236
+ - Updated dependencies [6ae3f28]
237
+ - Updated dependencies [be0e53c]
238
+ - Updated dependencies [57f57f5]
239
+ - Updated dependencies [ba822c1]
240
+ - Updated dependencies [6e6b06b]
241
+ - Updated dependencies [8bd5fac]
242
+ - Updated dependencies [57280bf]
243
+ - Updated dependencies [5033dd9]
244
+ - Updated dependencies [18c0d5c]
245
+ - Updated dependencies [dbd888d]
246
+ - Updated dependencies [1887e54]
247
+ - Updated dependencies [9f46375]
248
+ - Updated dependencies [41cca13]
249
+ - Updated dependencies [9a01e78]
250
+ - Updated dependencies [ada3841]
251
+ - Updated dependencies [5093a30]
252
+ - Updated dependencies [94b2c87]
253
+ - Updated dependencies [3ab2eca]
254
+ - Updated dependencies [e8d70ac]
255
+ - Updated dependencies [2c612ba]
256
+ - Updated dependencies [66af868]
257
+ - Updated dependencies [3427887]
258
+ - Updated dependencies [c967c57]
259
+ - Updated dependencies [fef3a50]
260
+ - Updated dependencies [60f3965]
261
+ - Updated dependencies [115e104]
262
+ - Updated dependencies [04719a9]
263
+ - Updated dependencies [04a6de4]
264
+ - Updated dependencies [0ba247b]
265
+ - Updated dependencies [6f41c53]
266
+ - Updated dependencies [4c5148e]
267
+ - Updated dependencies [0116a29]
268
+ - Updated dependencies [fec722f]
269
+ - Updated dependencies [e82215f]
270
+ - Updated dependencies [52b7346]
271
+ - Updated dependencies [9db63ee]
272
+ - Updated dependencies [b078afa]
273
+ - Updated dependencies [2ebff01]
274
+ - Updated dependencies [9db63ee]
275
+ - Updated dependencies [2ebff01]
276
+ - Updated dependencies [2d3b2c0]
277
+ - Updated dependencies [4772067]
278
+ - Updated dependencies [0f98419]
279
+ - Updated dependencies [64ba748]
280
+ - Updated dependencies [9fbab1b]
281
+ - Updated dependencies [d312755]
282
+ - Updated dependencies [a009f5b]
283
+ - Updated dependencies [c207a31]
284
+ - Updated dependencies [9b4f63b]
285
+ - Updated dependencies [3244fb8]
286
+ - Updated dependencies [1e3f91a]
287
+ - Updated dependencies [4f3c075]
288
+ - Updated dependencies [475e085]
289
+ - Updated dependencies [e477440]
290
+ - Updated dependencies [9dcb5da]
291
+ - Updated dependencies [a95ca85]
292
+ - Updated dependencies [b6d14ce]
293
+ - Updated dependencies [0382a51]
294
+ - Updated dependencies [93d061d]
295
+ - Updated dependencies [39554a1]
296
+ - Updated dependencies [d28430a]
297
+ - Updated dependencies [7669851]
298
+ - Updated dependencies [7d9cc66]
299
+ - Updated dependencies [7d9cc66]
300
+ - Updated dependencies [7d9cc66]
301
+ - Updated dependencies [df02568]
302
+ - Updated dependencies [4b76cfa]
303
+ - Updated dependencies [07b627f]
304
+ - Updated dependencies [d0de5b2]
305
+ - Updated dependencies [9c6a8db]
306
+ - Updated dependencies [9c6a8db]
307
+ - Updated dependencies [dfb9b15]
308
+ - Updated dependencies [9665c6e]
309
+ - Updated dependencies [44393be]
310
+ - Updated dependencies [c7fa299]
311
+ - Updated dependencies [7d9cc66]
312
+ - Updated dependencies [7d9cc66]
313
+ - Updated dependencies [5134b3b]
314
+ - Updated dependencies [7911a7d]
315
+ - Updated dependencies [d6b9404]
316
+ - Updated dependencies [62663ae]
317
+ - Updated dependencies [23a30cd]
318
+ - Updated dependencies [7d9cc66]
319
+ - Updated dependencies [7d9cc66]
320
+ - Updated dependencies [5c5ff23]
321
+ - Updated dependencies [9814afc]
322
+ - Updated dependencies [7d9cc66]
323
+ - Updated dependencies [02053ec]
324
+ - Updated dependencies [9c6a8db]
325
+ - @robota-sdk/agent-core@3.0.0
326
+ - @robota-sdk/agent-interface-session@3.0.0
327
+ - @robota-sdk/agent-interface-transport@3.0.0
328
+ - @robota-sdk/agent-transport@3.0.0
329
+ - @robota-sdk/agent-interface-analytics@3.0.0
330
+
331
+ ## 3.0.0-beta.106
332
+ ### Patch Changes
333
+
334
+ - @robota-sdk/agent-core@3.0.0-beta.106
335
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.106
336
+ - @robota-sdk/agent-interface-session@3.0.0-beta.106
337
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.106
338
+ - @robota-sdk/agent-transport@3.0.0-beta.106
339
+
340
+ ## 3.0.0-beta.105
341
+ ### Patch Changes
342
+
343
+ - @robota-sdk/agent-core@3.0.0-beta.105
344
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.105
345
+ - @robota-sdk/agent-interface-session@3.0.0-beta.105
346
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.105
347
+ - @robota-sdk/agent-transport@3.0.0-beta.105
348
+
349
+ ## 3.0.0-beta.104
350
+ ### Patch Changes
351
+
352
+ - @robota-sdk/agent-core@3.0.0-beta.104
353
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.104
354
+ - @robota-sdk/agent-interface-session@3.0.0-beta.104
355
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.104
356
+ - @robota-sdk/agent-transport@3.0.0-beta.104
357
+
358
+ ## 3.0.0-beta.103
359
+ ### Patch Changes
360
+
361
+ - Updated dependencies [6f41c53]
362
+ - @robota-sdk/agent-core@3.0.0-beta.103
363
+ - @robota-sdk/agent-interface-session@3.0.0-beta.103
364
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.103
365
+ - @robota-sdk/agent-transport@3.0.0-beta.103
366
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.103
367
+
368
+ ## 3.0.0-beta.102
369
+ ### Patch Changes
370
+
371
+ - @robota-sdk/agent-core@3.0.0-beta.102
372
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.102
373
+ - @robota-sdk/agent-interface-session@3.0.0-beta.102
374
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.102
375
+ - @robota-sdk/agent-transport@3.0.0-beta.102
376
+
377
+ ## 3.0.0-beta.101
378
+ ### Patch Changes
379
+
380
+ - Updated dependencies [62663ae]
381
+ - @robota-sdk/agent-core@3.0.0-beta.101
382
+ - @robota-sdk/agent-interface-session@3.0.0-beta.101
383
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.101
384
+ - @robota-sdk/agent-transport@3.0.0-beta.101
385
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.101
386
+
387
+ ## 3.0.0-beta.100
388
+ ### Patch Changes
389
+
390
+ - @robota-sdk/agent-core@3.0.0-beta.100
391
+ - @robota-sdk/agent-interface-analytics@3.0.0-beta.100
392
+ - @robota-sdk/agent-interface-session@3.0.0-beta.100
393
+ - @robota-sdk/agent-interface-transport@3.0.0-beta.100
394
+ - @robota-sdk/agent-transport@3.0.0-beta.100
395
+
3
396
  ## 3.0.0-beta.99
4
397
  ### Patch Changes
5
398
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@robota-sdk/agent-transport-ws",
3
- "version": "3.0.0-beta.99",
3
+ "version": "3.0.1",
4
4
  "description": "WebSocket carrier for the Robota SDK",
5
5
  "type": "module",
6
6
  "main": "dist/node/index.js",
@@ -41,11 +41,11 @@
41
41
  ],
42
42
  "dependencies": {
43
43
  "ws": "^8.21.1",
44
- "@robota-sdk/agent-interface-analytics": "3.0.0-beta.99",
45
- "@robota-sdk/agent-interface-session": "3.0.0-beta.99",
46
- "@robota-sdk/agent-interface-transport": "3.0.0-beta.99",
47
- "@robota-sdk/agent-transport": "3.0.0-beta.99",
48
- "@robota-sdk/agent-core": "3.0.0-beta.99"
44
+ "@robota-sdk/agent-core": "3.0.1",
45
+ "@robota-sdk/agent-interface-analytics": "3.0.1",
46
+ "@robota-sdk/agent-transport": "3.0.1",
47
+ "@robota-sdk/agent-interface-transport": "3.0.1",
48
+ "@robota-sdk/agent-interface-session": "3.0.1"
49
49
  },
50
50
  "devDependencies": {
51
51
  "@types/ws": "^8.18.1",