Skip to content

Bump the livekit-crates group with 4 updates - #116

Merged
ladvoc merged 1 commit into
mainfrom
dependabot/cargo/livekit-crates-7ab3bb74b5
Nov 20, 2026
Merged

ladvoc merged 1 commit into
mainfrom
dependabot/cargo/livekit-crates-7ab3bb74b5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the livekit-crates group with 4 updates: livekit, livekit-api, livekit-token-source and livekit-capture.

Updates livekit from 0.10.1 to 0.11.0

Release notes

Sourced from livekit's releases.

livekit-api 0.11.0 (2026-11-18)

Breaking Changes

  • Upgrade to the breaking livekit-protocol release that moves the submodule to 538dd3f0: livekit-api's own method signatures are unchanged and its two request literals fill the new UpdateStreamRequest and TransferSipParticipantRequest fields with defaults, but the protocol types it exposes publicly change with it (for example EgressOutput::Stream(proto::StreamOutput) now carries destinations and StreamOutput no longer derives Eq and Hash), so callers that destructure or construct those payloads, or that pass values from an older livekit-protocol, need to update.

Features

  • Add RoomOptions::publish_tracks, a list of tracks and their publish options published while connecting and sent with the join request in single peer connection mode to save the round trips of a separate AddTrackRequest and SDP negotiation; livekit-signaling's SignalClient::connect now takes an InitialPublish instead of a bare publisher offer, and RtcEngine::connect takes the tracks to publish with the join. Local tracks now keep the WebRTC runtime that created them alive, so tracks created before connecting stay usable in the room; call enable_zero_playout_delay before creating local tracks, since it fails once the runtime is active. Publishing a track now fails as soon as the server refuses it instead of after the publish timeout, and a track muted before or while it is published stays muted instead of being re-enabled.

Fixes

  • Preserve all seven framework task states and absent versus empty task names in thread listings, retaining typed status filters.
  • AgentDB wire errors carry a numeric code with its name and description, and Hello carries the client version.
  • Allow LiveKitApi to reuse a caller-supplied HTTP client so services share its TLS configuration and connection pool.

livekit 0.11.0 (2026-11-13)

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.
  • 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.

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.
  • 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)
  • 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)

livekit-api 0.10.2 (2026-11-13)

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.
  • 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.
  • 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)
Commits
  • c0de3bc Release packages (#1635)
  • 18db166 Report Reconnecting before removing participants on full reconnect (#1591)
  • 1b19002 release remote participants when the room is closed (rebased against main, ...
  • 88b619d livekit-rpc: fail in-flight calls with CONNECTION_CLOSED when the room closes...
  • 605a2ea Scope agent database access to a thread or a database (#1666)
  • 78993a1 Passing dotnet telemetry for v1 api (#1669)
  • 81d3f26 feat(telemetry): add device state and RTC stats windowing (#1482)
  • 61db66e feat(telemetry): add the write-ahead batch cache (#1481)
  • ff84187 feat(telemetry): add the transport seam and LiveKit Cloud destinations (#1480)
  • bd94b46 fix(e2ee): bounds-check key indices and clamp key_ring_size in KeyProvider (#...
  • Additional commits viewable in compare view

Updates livekit-api from 0.10.1 to 0.10.2

Release notes

Sourced from livekit-api's releases.

livekit-api 0.10.2 (2026-11-13)

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.
  • 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.
  • 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)
Commits
  • c0de3bc Release packages (#1635)
  • 18db166 Report Reconnecting before removing participants on full reconnect (#1591)
  • 1b19002 release remote participants when the room is closed (rebased against main, ...
  • 88b619d livekit-rpc: fail in-flight calls with CONNECTION_CLOSED when the room closes...
  • 605a2ea Scope agent database access to a thread or a database (#1666)
  • 78993a1 Passing dotnet telemetry for v1 api (#1669)
  • 81d3f26 feat(telemetry): add device state and RTC stats windowing (#1482)
  • 61db66e feat(telemetry): add the write-ahead batch cache (#1481)
  • ff84187 feat(telemetry): add the transport seam and LiveKit Cloud destinations (#1480)
  • bd94b46 fix(e2ee): bounds-check key indices and clamp key_ring_size in KeyProvider (#...
  • Additional commits viewable in compare view

Updates livekit-token-source from 0.1.4 to 0.2.0

Release notes

Sourced from livekit-token-source's releases.

livekit-token-source 0.2.0 (2026-11-13)

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.
Commits
  • c0de3bc Release packages (#1635)
  • 18db166 Report Reconnecting before removing participants on full reconnect (#1591)
  • 1b19002 release remote participants when the room is closed (rebased against main, ...
  • 88b619d livekit-rpc: fail in-flight calls with CONNECTION_CLOSED when the room closes...
  • 605a2ea Scope agent database access to a thread or a database (#1666)
  • 78993a1 Passing dotnet telemetry for v1 api (#1669)
  • 81d3f26 feat(telemetry): add device state and RTC stats windowing (#1482)
  • 61db66e feat(telemetry): add the write-ahead batch cache (#1481)
  • ff84187 feat(telemetry): add the transport seam and LiveKit Cloud destinations (#1480)
  • bd94b46 fix(e2ee): bounds-check key indices and clamp key_ring_size in KeyProvider (#...
  • Additional commits viewable in compare view

Updates livekit-capture from 0.1.9 to 0.2.0

Release notes

Sourced from livekit-capture's releases.

livekit-capture 0.2.0 (2026-11-13)

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.
  • 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)
Commits
  • c0de3bc Release packages (#1635)
  • 18db166 Report Reconnecting before removing participants on full reconnect (#1591)
  • 1b19002 release remote participants when the room is closed (rebased against main, ...
  • 88b619d livekit-rpc: fail in-flight calls with CONNECTION_CLOSED when the room closes...
  • 605a2ea Scope agent database access to a thread or a database (#1666)
  • 78993a1 Passing dotnet telemetry for v1 api (#1669)
  • 81d3f26 feat(telemetry): add device state and RTC stats windowing (#1482)
  • 61db66e feat(telemetry): add the write-ahead batch cache (#1481)
  • ff84187 feat(telemetry): add the transport seam and LiveKit Cloud destinations (#1480)
  • bd94b46 fix(e2ee): bounds-check key indices and clamp key_ring_size in KeyProvider (#...
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the livekit-crates group with 4 updates: [livekit](https://github.com/livekit/rust-sdks), [livekit-api](https://github.com/livekit/rust-sdks), [livekit-token-source](https://github.com/livekit/rust-sdks) and [livekit-capture](https://github.com/livekit/rust-sdks).


Updates `livekit` from 0.10.1 to 0.11.0
- [Release notes](https://github.com/livekit/rust-sdks/releases)
- [Commits](livekit/rust-sdks@livekit/v0.10.1...livekit/v0.11.0)

Updates `livekit-api` from 0.10.1 to 0.10.2
- [Release notes](https://github.com/livekit/rust-sdks/releases)
- [Commits](livekit/rust-sdks@livekit-api/v0.10.1...livekit-api/v0.10.2)

Updates `livekit-token-source` from 0.1.4 to 0.2.0
- [Release notes](https://github.com/livekit/rust-sdks/releases)
- [Commits](livekit/rust-sdks@livekit-token-source/v0.1.4...livekit-token-source/v0.2.0)

Updates `livekit-capture` from 0.1.9 to 0.2.0
- [Release notes](https://github.com/livekit/rust-sdks/releases)
- [Commits](livekit/rust-sdks@livekit-capture/v0.1.9...livekit-capture/v0.2.0)

---
updated-dependencies:
- dependency-name: livekit
  dependency-version: 0.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: livekit-crates
- dependency-name: livekit-api
  dependency-version: 0.10.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: livekit-crates
- dependency-name: livekit-token-source
  dependency-version: 0.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: livekit-crates
- dependency-name: livekit-capture
  dependency-version: 0.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: livekit-crates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from ladvoc as a code owner November 20, 2026 02:44
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 20, 2026
@ladvoc
ladvoc merged commit af19fec into main Nov 20, 2026
9 checks passed
@dependabot
dependabot Bot deleted the dependabot/cargo/livekit-crates-7ab3bb74b5 branch November 20, 2026 03:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant