[dependabot]

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

Updates livekit from 0.9.5 to 0.9.6

Release notes

Sourced from livekit's releases.

livekit 0.9.6 (2026-10-20)

Fixes

• Outgoing data stream chunk and trailer packets now carry the stream's destination identities. Before, only the header was targeted, so the content of a stream sent to specific participants was delivered to everyone in the room.
• Synthesize index-based identifiers on platforms without hardware audio GUIDs and add index-based selection to PlatformAudio.
• Prefix every ffmpeg symbol bundled in the linux libwebrtc.a with LK_, so an application that also links its own FFmpeg, shared or static, no longer calls libwebrtc's copy or fails to link.
• Update zip to 9.0.4, as older releases have security issues and were temporarily yanked (zip-rs/zip2#1075).

Merge livekit-uniffi into livekit-ffi.

There is now one crate, one version and one release tag. The livekit-uniffi crate, its changelog and its livekit-uniffi/v* tags are gone; its history is preserved in git.

The crate carries two mutually exclusive surfaces, selected by feature:

• room-apis (default) is the existing protobuf / C-ABI surface, with livekit and libwebrtc. Everything that built livekit-ffi before builds it unchanged.
• core-modules is the former livekit-uniffi surface — access tokens, log forwarding, data tracks, data streams v2 — and depends on none of livekit, libwebrtc, soxr-sys or imgproc. What previously built livekit-uniffi now builds -p livekit-ffi --no-default-features --features core-modules.

[package.metadata.platform-features] in livekit-ffi/Cargo.toml records which surface each downstream package build gets, and CI resolves its build flags from it.

The merge itself requires no downstream SDK changes: the UniFFI namespace is pinned per surface and every published package name is preserved. The one difference is the native library the crate builds, liblivekit_uniffi → liblivekit_ffi, which is loaded by name from the generated bindings and the Dart build hook and needs no consumer change. The package renames are a separate change, released alongside this one.

The UniFFI node package (@livekit/uniffi) is not built for now and will be reintroduced separately; node bindings ship from livekit-ffi-node-bindings.

livekit-protocol exposes the conversation schema of a thread's database, as protocol's Go package

does: agent::THREAD_SCHEMA_VERSION and agent::THREAD_SCHEMA_V1 (the SQL); the crates that depend on it follow its bump.

Stop failing an RPC call whose reply arrives just after its recipient leaves the room.

Purging a call's pending ack and response the instant its recipient disconnects assumed that "participant left" implies "no reply is coming". It does not: the disconnect is announced on the signalling connection while the ack and response travel on the data channel, and nothing orders the two. A recipient that leaves because of the RPC it just answered — lk.sip.EndCall, where the SIP participant drops out of the room as soon as it has ended the call — produces that order

... (truncated)

Commits

• fa46e84 Release packages (#1533)
• 76d895b livekit-data-stream: send chunks and trailers only to the stream's recipients...
• 819f0f8 webrtc-sys: prefix the bundled ffmpeg symbols to prevent collisions (#1534)
• d699ccd livekit-ffi-node-bindings: don't throw from FfiHandle finalizer after dispose...
• ebf624c (PART 2) Renames old livekit-uniffi builds to use ffi instead post `livek...
• 9906918 Merge livekit-ffi / livekit-uniffi together into a new livekit-ffi with...
• bcef61a livekit-rpc: give a departed recipient's reply time to land (#1520)
• 8c57055 webrtc-sys-build: bump zip to 9.0.4 for security advisories (#1532)
• e127cc5 Ship dSYMs in the Swift xcframework again (#1525)
• 1987013 livekit-protocol: the thread schema (#1530)
• Additional commits viewable in compare view

Updates livekit-api from 0.9.0 to 0.9.1

Release notes

Sourced from livekit-api's releases.

livekit-api 0.9.1 (2026-10-20)

Fixes

Merge livekit-uniffi into livekit-ffi.

There is now one crate, one version and one release tag. The livekit-uniffi crate, its changelog and its livekit-uniffi/v* tags are gone; its history is preserved in git.

The crate carries two mutually exclusive surfaces, selected by feature:

• room-apis (default) is the existing protobuf / C-ABI surface, with livekit and libwebrtc. Everything that built livekit-ffi before builds it unchanged.
• core-modules is the former livekit-uniffi surface — access tokens, log forwarding, data tracks, data streams v2 — and depends on none of livekit, libwebrtc, soxr-sys or imgproc. What previously built livekit-uniffi now builds -p livekit-ffi --no-default-features --features core-modules.

[package.metadata.platform-features] in livekit-ffi/Cargo.toml records which surface each downstream package build gets, and CI resolves its build flags from it.

The merge itself requires no downstream SDK changes: the UniFFI namespace is pinned per surface and every published package name is preserved. The one difference is the native library the crate builds, liblivekit_uniffi → liblivekit_ffi, which is loaded by name from the generated bindings and the Dart build hook and needs no consumer change. The package renames are a separate change, released alongside this one.

The UniFFI node package (@livekit/uniffi) is not built for now and will be reintroduced separately; node bindings ship from livekit-ffi-node-bindings.

livekit-protocol exposes the conversation schema of a thread's database, as protocol's Go package

does: agent::THREAD_SCHEMA_VERSION and agent::THREAD_SCHEMA_V1 (the SQL); the crates that depend on it follow its bump.

Commits

• fa46e84 Release packages (#1533)
• 76d895b livekit-data-stream: send chunks and trailers only to the stream's recipients...
• 819f0f8 webrtc-sys: prefix the bundled ffmpeg symbols to prevent collisions (#1534)
• d699ccd livekit-ffi-node-bindings: don't throw from FfiHandle finalizer after dispose...
• ebf624c (PART 2) Renames old livekit-uniffi builds to use ffi instead post `livek...
• 9906918 Merge livekit-ffi / livekit-uniffi together into a new livekit-ffi with...
• bcef61a livekit-rpc: give a departed recipient's reply time to land (#1520)
• 8c57055 webrtc-sys-build: bump zip to 9.0.4 for security advisories (#1532)
• e127cc5 Ship dSYMs in the Swift xcframework again (#1525)
• 1987013 livekit-protocol: the thread schema (#1530)
• Additional commits viewable in compare view

Updates livekit-token-source from 0.1.3 to 0.1.4

Release notes

Sourced from livekit-token-source's releases.

livekit-token-source 0.1.4 (2026-10-20)

Fixes

Merge livekit-uniffi into livekit-ffi.

There is now one crate, one version and one release tag. The livekit-uniffi crate, its changelog and its livekit-uniffi/v* tags are gone; its history is preserved in git.

The crate carries two mutually exclusive surfaces, selected by feature:

• room-apis (default) is the existing protobuf / C-ABI surface, with livekit and libwebrtc. Everything that built livekit-ffi before builds it unchanged.
• core-modules is the former livekit-uniffi surface — access tokens, log forwarding, data tracks, data streams v2 — and depends on none of livekit, libwebrtc, soxr-sys or imgproc. What previously built livekit-uniffi now builds -p livekit-ffi --no-default-features --features core-modules.

[package.metadata.platform-features] in livekit-ffi/Cargo.toml records which surface each downstream package build gets, and CI resolves its build flags from it.

The merge itself requires no downstream SDK changes: the UniFFI namespace is pinned per surface and every published package name is preserved. The one difference is the native library the crate builds, liblivekit_uniffi → liblivekit_ffi, which is loaded by name from the generated bindings and the Dart build hook and needs no consumer change. The package renames are a separate change, released alongside this one.

The UniFFI node package (@livekit/uniffi) is not built for now and will be reintroduced separately; node bindings ship from livekit-ffi-node-bindings.

Commits

• fa46e84 Release packages (#1533)
• 76d895b livekit-data-stream: send chunks and trailers only to the stream's recipients...
• 819f0f8 webrtc-sys: prefix the bundled ffmpeg symbols to prevent collisions (#1534)
• d699ccd livekit-ffi-node-bindings: don't throw from FfiHandle finalizer after dispose...
• ebf624c (PART 2) Renames old livekit-uniffi builds to use ffi instead post `livek...
• 9906918 Merge livekit-ffi / livekit-uniffi together into a new livekit-ffi with...
• bcef61a livekit-rpc: give a departed recipient's reply time to land (#1520)
• 8c57055 webrtc-sys-build: bump zip to 9.0.4 for security advisories (#1532)
• e127cc5 Ship dSYMs in the Swift xcframework again (#1525)
• 1987013 livekit-protocol: the thread schema (#1530)
• Additional commits viewable in compare view

Updates livekit-capture from 0.1.5 to 0.1.6

Release notes

Sourced from livekit-capture's releases.

livekit-capture 0.1.6 (2026-10-20)

Fixes

• Outgoing data stream chunk and trailer packets now carry the stream's destination identities. Before, only the header was targeted, so the content of a stream sent to specific participants was delivered to everyone in the room.
• Synthesize index-based identifiers on platforms without hardware audio GUIDs and add index-based selection to PlatformAudio.
• Prefix every ffmpeg symbol bundled in the linux libwebrtc.a with LK_, so an application that also links its own FFmpeg, shared or static, no longer calls libwebrtc's copy or fails to link.
• Update zip to 9.0.4, as older releases have security issues and were temporarily yanked (zip-rs/zip2#1075).

Merge livekit-uniffi into livekit-ffi.

There is now one crate, one version and one release tag. The livekit-uniffi crate, its changelog and its livekit-uniffi/v* tags are gone; its history is preserved in git.

The crate carries two mutually exclusive surfaces, selected by feature:

• room-apis (default) is the existing protobuf / C-ABI surface, with livekit and libwebrtc. Everything that built livekit-ffi before builds it unchanged.
• core-modules is the former livekit-uniffi surface — access tokens, log forwarding, data tracks, data streams v2 — and depends on none of livekit, libwebrtc, soxr-sys or imgproc. What previously built livekit-uniffi now builds -p livekit-ffi --no-default-features --features core-modules.

[package.metadata.platform-features] in livekit-ffi/Cargo.toml records which surface each downstream package build gets, and CI resolves its build flags from it.

The merge itself requires no downstream SDK changes: the UniFFI namespace is pinned per surface and every published package name is preserved. The one difference is the native library the crate builds, liblivekit_uniffi → liblivekit_ffi, which is loaded by name from the generated bindings and the Dart build hook and needs no consumer change. The package renames are a separate change, released alongside this one.

The UniFFI node package (@livekit/uniffi) is not built for now and will be reintroduced separately; node bindings ship from livekit-ffi-node-bindings.

livekit-protocol exposes the conversation schema of a thread's database, as protocol's Go package

does: agent::THREAD_SCHEMA_VERSION and agent::THREAD_SCHEMA_V1 (the SQL); the crates that depend on it follow its bump.

Stop failing an RPC call whose reply arrives just after its recipient leaves the room.

Purging a call's pending ack and response the instant its recipient disconnects assumed that "participant left" implies "no reply is coming". It does not: the disconnect is announced on the signalling connection while the ack and response travel on the data channel, and nothing orders the two. A recipient that leaves because of the RPC it just answered — lk.sip.EndCall, where the SIP participant drops out of the room as soon as it has ended the call — produces that order

... (truncated)

Commits

• fa46e84 Release packages (#1533)
• 76d895b livekit-data-stream: send chunks and trailers only to the stream's recipients...
• 819f0f8 webrtc-sys: prefix the bundled ffmpeg symbols to prevent collisions (#1534)
• d699ccd livekit-ffi-node-bindings: don't throw from FfiHandle finalizer after dispose...
• ebf624c (PART 2) Renames old livekit-uniffi builds to use ffi instead post `livek...
• 9906918 Merge livekit-ffi / livekit-uniffi together into a new livekit-ffi with...
• bcef61a livekit-rpc: give a departed recipient's reply time to land (#1520)
• 8c57055 webrtc-sys-build: bump zip to 9.0.4 for security advisories (#1532)
• e127cc5 Ship dSYMs in the Swift xcframework again (#1525)
• 1987013 livekit-protocol: the thread schema (#1530)
• 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