Skip to content

Bump to livekit-ffi/v0.14.0 - #57

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
bump/livekit-ffi-v0.14.0
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
bump/livekit-ffi-v0.14.0

Conversation

@github-actions

Copy link
Copy Markdown

Bumps livekit-ffi from v0.13.2 to v0.14.0.

This PR updates the livekit-rtc/rust-sdks submodule to livekit-ffi/v0.14.0, regenerates the protobuf stubs in livekit-rtc/livekit/rtc/_proto and adds a changeset for livekit-rtc.

Check the proto diff for API changes that need matching updates in the Python SDK (new fields, renamed messages, new requests/events).

Generated files

 .changeset/bump-livekit-ffi-v0.14.0.md         |   5 +
 livekit-rtc/livekit/rtc/_proto/capture_pb2.py  |  38 +--
 livekit-rtc/livekit/rtc/_proto/capture_pb2.pyi |  67 +++--
 livekit-rtc/livekit/rtc/_proto/ffi_pb2.py      |  40 +--
 livekit-rtc/livekit/rtc/_proto/ffi_pb2.pyi     |  32 ++-
 livekit-rtc/livekit/rtc/_proto/room_pb2.py     | 330 +++++++++++++------------
 livekit-rtc/livekit/rtc/_proto/room_pb2.pyi    |  11 +-
 livekit-rtc/rust-sdks                          |   2 +-
 8 files changed, 289 insertions(+), 236 deletions(-)
Release notes

Breaking Changes

  • Add an opt-in decoded HTTP response limit, used by telemetry export, that reports an oversized response as the new TransportError::ResponseTooLarge variant. Code that matches TransportError exhaustively, in Rust or in the generated Swift and Kotlin bindings, needs a case for it.

Fixes

  • Scope agent database access to a thread or a database: AgentThreadGrants gains sql, and the new agentDatabase claim (AgentDatabaseGrants) grants read, write and delete on listed databases plus project-wide create and list. AgentGrants::database_admin is removed, and DatabaseClient signs each call with only the grant it needs. A thread's database id is its thread id, so Thread::database_id is gone.
  • Fix remote participant and track leaks when closing a room, including encrypted tracks, cancelled closure, and participant updates racing with teardown.
  • Compile the LiveKitFFI CocoaPod in Swift 5 mode, matching SPM and allowing Swift 6 hosts without inheriting their language mode.
  • Handle out-of-range key indices gracefully in KeyProvider and clamp key_ring_size to valid bounds.
  • Log libwebrtc messages at their own severity instead of reporting every one as debug, so its warnings and errors are no longer filtered out by default in every SDK.
  • On a full reconnect, Room now reports Reconnecting (and the ConnectionStateChanged that precedes it) before removing remote participants, so the ParticipantDisconnected events of a full reconnect arrive after Reconnecting rather than before it and can be told apart from participants actually leaving. #1591 (@MaxHeimbrock)
  • When the local room closes, in-flight perform_rpc calls now fail with RpcErrorCode::ConnectionClosed (1506) instead of RecipientDisconnected (1503), which remains reserved for remote participant departures.
  • Report the .NET SDK as ClientInfo.SDK.DOTNET in the join request. The dotnet SDK name fell through to UNKNOWN on the single peer connection path. - #1669 (@MaxHeimbrock)

Triggered by @cloudwebrtc via the Bump livekit-ffi workflow.

@cloudwebrtc

Copy link
Copy Markdown
Owner

Test run of the bump-ffi workflow; closing.

@cloudwebrtc
cloudwebrtc deleted the bump/livekit-ffi-v0.14.0 branch November 15, 2026 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant