node-sdks

Frameworks & LibrariesApache-2.0

node-sdks release notes.

Latest @livekit/rtc-node@0.13.34 · by node-sdksWritten in TypeScriptWebsitelivekit/node-sdksRSS

Release activity

Release activity — 13 releases across 9 days since May 13, 2026. Each cell is one day; darker means more releases that day. Nothing is recorded before May 13, 2026. Older weeks are hidden at this screen width.
JunJulAugSep
SundayNo releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026No releases on Aug 16, 2026No releases on Aug 23, 2026No releases on Aug 30, 2026No releases on Sep 6, 2026
MondayNo releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 2026No releases on Aug 17, 2026No releases on Aug 24, 2026No releases on Aug 31, 2026No releases on Sep 7, 2026
Tuesday1 release on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 2026No releases on Jun 23, 20262 releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 2026No releases on Jul 21, 20261 release on Jul 28, 2026No releases on Aug 4, 2026No releases on Aug 11, 20262 releases on Aug 18, 2026No releases on Aug 25, 2026No releases on Sep 1, 2026
WednesdayNo releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 20262 releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026No releases on Aug 12, 2026No releases on Aug 19, 2026No releases on Aug 26, 2026No releases on Sep 2, 2026
Thursday1 release on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 20261 release on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026No releases on Aug 13, 2026No releases on Aug 20, 2026No releases on Aug 27, 2026No releases on Sep 3, 2026
FridayNo releases on May 29, 2026No releases on Jun 5, 2026No releases on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 20261 release on Jul 31, 2026No releases on Aug 7, 2026No releases on Aug 14, 2026No releases on Aug 21, 2026No releases on Aug 28, 2026No releases on Sep 4, 2026
SaturdayNo releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026No releases on Aug 8, 2026No releases on Aug 15, 2026No releases on Aug 22, 2026No releases on Aug 29, 2026No releases on Sep 5, 2026

13 releases since May 13, 2026, busiest day 2

Changelog

@livekit/rtc-node@0.13.34

Latest
Changed 2
  • Convert data streams to use livekit-ffi exposed data streams interface
  • Update e2ee defaults to conform to required FFI fields and update protocol

From node-sdks

Patch Changes
  • Convert data streams to use livekit-ffi exposed data streams interface - #697 (@1egoman)

  • update e2ee defaults to confirm to required FFI fields and update protocol - #708 (@lukasIO)

View originalPermalink
How @livekit/rtc-node@0.13.34 went

livekit-server-sdk@2.18.0

Added 1
  • Add EgressClient.startEgress(), a unified convenience method that calls the v2 Egress.StartEgress RPC with a StartEgressRequest or a partial init object
Changed 1
  • Update e2ee defaults to conform to required FFI fields and update protocol

From node-sdks

Minor Changes
  • Add EgressClient.startEgress(), a unified convenience method that calls the v2 Egress.StartEgress RPC with a StartEgressRequest (or a partial init object). The existing per-type start helpers are unchanged. - #706 (@frostbyte73)
Patch Changes
  • update e2ee defaults to confirm to required FFI fields and update protocol - #708 (@lukasIO)
View originalPermalink
How livekit-server-sdk@2.18.0 went

@livekit/rtc-node@0.13.33

Changed 1
  • update to livekit ffi 0.12.73
Fixed 1
  • avoid dual package hazard by building single CJS version with an ESM wrapper

From node-sdks

Patch Changes
  • fix: avoid dual package hazard by building single CJS version with an ESM wrapper - #700 (@lukasIO)

  • Update to livekit ffi 0.12.73 - #698 (@1egoman)

View originalPermalink
How @livekit/rtc-node@0.13.33 went

@livekit/rtc-node@0.13.32

Changed 1
  • Bump FFI to 0.12.68
Fixed 1
  • Close audio streams when their track is unsubscribed to prevent stale streams from delivering frames after reconnection

From node-sdks

Patch Changes
  • Close audio streams when their track is unsubscribed. An unsubscribed track never receives eos from the FFI, so any AudioStream attached to it kept delivering frames — after a reconnect that meant the stale stream and the new subscription's stream both delivered the publisher's audio. - #701 (@davidzhao)

  • bump FFI to 0.12.68 - #701 (@davidzhao)

View originalPermalink
How @livekit/rtc-node@0.13.32 went

livekit-server-sdk@2.17.0

Added 4
  • Add LiveKitAPI, a unified entry point that exposes every server API through properties (api.room, api.egress, api.ingress, api.sip, api.agentDispatch, api.connector), constructable with an API key and secret or with a pre-signed token, with fallback to environment variables
  • Add SipCallError, a TwirpError subclass thrown by SipClient.createSipParticipant and transferSipParticipant when a call fails with a SIP status, exposing the SIP response code and reason as sipStatusCode and sipStatus getters
  • Add auto failover APIs with LK Cloud
  • Individual clients now accept a token via ClientOptions

From node-sdks

Minor Changes
  • Add LiveKitAPI, a unified entry point that exposes every server API through a property (api.room, api.egress, api.ingress, api.sip, api.agentDispatch, api.connector). It can be constructed with an API key and secret, or with a pre-signed token (no secret required, so it can run client-side), and falls back to the LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET, and LIVEKIT_TOKEN environment variables. Individual clients also accept a token via ClientOptions. - #695 (@davidzhao)

  • Add SipCallError, a TwirpError subclass thrown by SipClient.createSipParticipant / transferSipParticipant when a call fails with a SIP status. It exposes the SIP response code and reason as sipStatusCode / sipStatus getters, while other error metadata remains available via metadata. - #695 (@davidzhao)

Patch Changes
View originalPermalink
How livekit-server-sdk@2.17.0 went

@livekit/rtc-node@0.13.31

Fixed 1
  • Fix AudioSource.waitForPlayout resolving immediately with audio still queued by discarding the waiter when released and lazily re-creating it on the next captureFrame, and make waitForPlayout() resolve immediately when no audio is queued instead of blocking until the next release

From node-sdks

Patch Changes
  • Fix AudioSource.waitForPlayout resolving immediately with audio still queued. The internal playout promise could be left resolved ("latched") by the drain timer firing during a gap between captures, or by clearQueue()/pause; a later waitForPlayout() then consumed the stale resolution and reported playout complete ~queueSizeMs early, clipping the tail of agent speech on every turn in downstream consumers. The waiter is now discarded when released and lazily re-created on the next captureFrame, mirroring python-sdks. As part of this, waitForPlayout() now resolves immediately when no audio is queued instead of blocking until the next release. - #693 (@chenghao-mou)
View originalPermalink
How @livekit/rtc-node@0.13.31 went

livekit-server-sdk@2.16.0

Added 2
  • Support SIP media configs
  • Add callee dispatch rule support to createSipDispatchRule

From node-sdks

Minor Changes
Patch Changes
  • Add callee dispatch rule support to createSipDispatchRule - #684 (@lukasIO)
View originalPermalink
How livekit-server-sdk@2.16.0 went

@livekit/rtc-node@0.13.30

Added 1
  • Add initial support for frame processor usage directly on tracks

From node-sdks

Patch Changes
  • Add initial support for frame processor usage directly on tracks - #671 (@1egoman)
View originalPermalink
How @livekit/rtc-node@0.13.30 went

@livekit/rtc-node@0.13.29

Added 1
  • Add getRtcStats() method to query rtcStats on room
Changed 1
  • Bump ffi bindings to include rpc v2 support

From node-sdks

Patch Changes
View originalPermalink
How @livekit/rtc-node@0.13.29 went

@livekit/rtc-node@0.13.28

Added 3
  • Expose kindDetails on Participant and re-export the ParticipantKindDetail enum
  • Handle track republish
  • Add support for SimulateScenario

From node-sdks

Patch Changes
View originalPermalink
How @livekit/rtc-node@0.13.28 went

livekit-server-sdk@2.15.3

Added 6
  • Add restartPolicy option to AgentDispatchClient.createDispatch (cloud only)
  • Add ringingTimeout option to ConnectorClient.dialWhatsAppCall and acceptWhatsAppCall
  • Add waitUntilAnswered option to ConnectorClient.acceptWhatsAppCall
  • Add optional disconnectReason parameter to ConnectorClient.disconnectWhatsAppCall
  • Re-export JobRestartPolicy and DisconnectWhatsAppCallRequest_DisconnectReason
  • Add canManageAgentSession to VideoGrant
Changed 1
  • Bump @livekit/protocol to 1.45.6

From node-sdks

Patch Changes
  • Bump @livekit/protocol to 1.45.6 and surface new fields on the agent dispatch and connector clients: - #657 (@anunaym14)

    • AgentDispatchClient.createDispatch: new restartPolicy option (cloud only)
    • ConnectorClient.dialWhatsAppCall / acceptWhatsAppCall: new ringingTimeout option (and waitUntilAnswered on accept)
    • ConnectorClient.disconnectWhatsAppCall: new optional disconnectReason parameter
    • Re-export JobRestartPolicy and DisconnectWhatsAppCallRequest_DisconnectReason
  • Add canManageAgentSession to VideoGrant - #661 (@theomonnom)

View originalPermalink
How livekit-server-sdk@2.15.3 went
View all

Discussion

If you publish node-sdks, you can claim this product by proving you administer its repository.