Releases

The current stable release is @anvia/server 1.1.4. The entries below preserve notable v0 transport milestones.

Version	Summary
1.1.4	Kept code, retryable, and JSON-safe details on JSONL/SSE error events (including prototype-defined fields JSON.stringify drops), degraded non-JSON-safe throws to { message }, and exported errorEvent.
1.0.11	Updated the Client dependency to 1.0.11.
1.0.10	Updated the Client dependency to 1.0.10.
1.0.9	Updated the Client dependency to 1.0.9.
1.0.8	Updated the Client dependency to 1.0.8.
1.0.7	Updated the Client dependency to 1.0.7.
1.0.6	Updated the Client dependency to 1.0.6.
1.0.5	Declared and verified Bun 1.3.14 runtime compatibility for Client and Server streaming.
1.0.4	Updated the Client dependency to 1.0.4.
1.0.3	Updated the Client dependency to 1.0.3.
1.0.2	Updated the Client dependency to 1.0.2.
1.0.1	Updated the Client dependency to 1.0.1.
1.0.0	Aligned framed client responses with protocol v3 so message requests and interaction-response requests can create linked agent stream phases while continuations remain server-owned.
1.0.0-rc.9	Synchronized Server with the Anvia 1.0 release-candidate train.
0.7.5	Updated the Core dependency to 0.26.0.
0.7.4	Updated the Core dependency to 0.25.1.
0.7.0	Carried model-aware context limits and active context usage through UI stream events.
0.6.0	Added the legacy createEventStream({ resume }) and createUIStreamResponse({ resume }) overloads for first-class stream continuation.
0.5.0	Added resumable event envelopes, replay/tail helpers, and the in-memory resumable stream store.
0.4.6	Hardened SSE control-field validation alongside transport behavior fixes.
0.4.0	Added the legacy shared UI message stream protocol and createUIStreamResponse.
0.3.1	Split stream internals, added coverage-gated tests, and removed stack traces from default streamed error events.
0.2.0	Introduced JSONL and SSE response helpers.

Upgrade checks

• Upgrade @anvia/core with Server when the changelog lists a dependency alignment.
• Keep clients aligned with envelope and UI-event changes; resumable routes require a resume-aware React client.
• Validate the discriminated ClientStreamRequest union and persist interaction continuations server-side; never return trusted continuations to the browser.
• Re-test proxy buffering, content types, cancellation, and custom serializers after transport changes.
• When adopting resume, add shared persistence before enabling it across multiple production replicas.

Read the complete Server changelog.