https://livekit.io logo
Join Slack
Powered by
What;s the new update livekit-server-sdk from 2.14...
# ask-ai
b
What;s the new update livekit-server-sdk from 2.14.2 to 2.15.0
✅ 1
t
Thanks for reaching out, G. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I see you’re asking what changed in the livekit-server-sdk moving from 2.14.2 to 2.15.0. I don’t currently have the specific changelog for that exact release. To fetch the correct release notes quickly, could you tell me: • Which language/package you’re using (for example: Go, Node, Rust, Java, or another)? • Where you saw the version (GitHub, npm, your project lockfile, etc.)? • Do you want the full changelog, just breaking/migration notes, or a short summary of highlights? Once you share that, I’ll pull the exact 2.15.0 notes and call out any breaking changes or upgrade steps you need. , with interactive elements
b
Node
t
Thanks — you asked what changed in the Node 
livekit-server-sdk
when moving from 2.14.2 → 2.15.0. Below is a concise summary of the notable changes in 2.15.0 that affect Node usage. Key changes in v2.15.0 • Webhook event additions: New webhook event types were added, including 
egress_started
and 
egress_ended
, so servers can react to egress/recording lifecycle events. • Improved TypeScript support: Updated type definitions (for 
WebhookEvent
, 
RoomServiceClient
, 
EgressClient
, etc.) to improve IDE autocomplete and compile-time checks. • Egress API enhancements: 
EgressClient
gained more granular control and options for room/track egress (improved output destination options such as S3/GCS and layout/customization options for recordings). • Version compatibility alignment: The SDK bump aligns with newer 
@livekit/protocol
versions (1.40.0–1.44.0), keeping compatibility with LiveKit Server 1.x and Twirp-based HTTP APIs. • Agent/backend improvements: Refinements for programmatically generating tokens and agent join flows to improve reliability in agent deployment scenarios. Upgrade guidance (what to check) • Webhook handlers: Verify your webhook consumer handles the new 
egress_*
events (and any additional 
WebhookEvent
variants) if you rely on webhook event types. • Egress usage: If you use 
EgressClient
, review any new options you want to adopt (output destinations, layout settings) and test recordings/egress flows. • Type changes: Run TypeScript/compile checks to catch any typing updates; adjust imports or types if needed. • Compatibility: Ensure your server components that depend on 
@livekit/protocol
are compatible with the aligned protocol versions. If you want, I can: • Paste the exact release notes or changelog entry for 2.15.0 (if you’d like the full text). • Point out any potential breaking changes line-by-line for your codebase if you share where/how you use the SDK (e.g., webhook handling, egress calls, token generation). Which would you prefer? Sources: server-sdk-js | livekit/livekit_composite | DeepWiki, with interactive elements
2 Views
Open in Slack
PreviousNext
Powered by