Skip to content

Release packages - #1362

Open
knope-bot[bot] wants to merge 1 commit into
mainfrom
knope/release
Open

Release packages#1362
knope-bot[bot] wants to merge 1 commit into
mainfrom
knope/release

Conversation

@knope-bot

@knope-bot knope-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Important

Merging this pull request will create these releases

livekit-api 0.6.5 (2026-09-04)

Features

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol
  • Add self_test_http_get / self_test_ws_echo / has_http_client / has_ws_client UniFFI exports so foreign hosts can exercise the transport seam end-to-end.
  • Update sip_busy test GRPc code: failed_precondition -> failed_precondition

Moves the internal region-discovery cache into a new livekit-region crate. No

public API or behaviour change.

Moves the signalling client into a new livekit-signaling crate. livekit-api

re-exports it under the historical livekit_api::signal_client path, now marked
deprecated: it is internal SDK API, and dependents should use livekit-signaling
directly. livekit-api no longer depends on livekit-net.

Also drops two dependencies that were declared but never used: scopeguard and
bytes.

webrtc-sys 0.3.44 (2026-09-04)

Features

  • Handle capture of dmabuf using existing capture path

Fixes

  • Fix pre-encoded frame segfault on macOS

Make AdmProxy worker-thread-affine: all platform ADM access now happens on the WebRTC worker thread, matching the ADM threading contract.

  • The platform ADM is now created lazily on the first PlatformAudio acquire on all platforms, so apps that never use platform audio never construct it.
  • Fixes Android platform recording delivering no audio: the audio transport was never registered on the lazily created ADM.
  • Fixes a shutdown race by keeping the runtime threads alive as long as Rust can reach the audio device controller.
  • Adds a platform_audio example exercising the PlatformAudio API and the worker-thread marshaling.

livekit-protocol 0.7.13 (2026-09-04)

Features

  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol

livekit 0.8.5 (2026-09-04)

Features

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol
  • Fix pre-encoded frame segfault on macOS
  • Handle capture of dmabuf using existing capture path
  • Add self_test_http_get / self_test_ws_echo / has_http_client / has_ws_client UniFFI exports so foreign hosts can exercise the transport seam end-to-end.

Make AdmProxy worker-thread-affine: all platform ADM access now happens on the WebRTC worker thread, matching the ADM threading contract.

  • The platform ADM is now created lazily on the first PlatformAudio acquire on all platforms, so apps that never use platform audio never construct it.
  • Fixes Android platform recording delivering no audio: the audio transport was never registered on the lazily created ADM.
  • Fixes a shutdown race by keeping the runtime threads alive as long as Rust can reach the audio device controller.
  • Adds a platform_audio example exercising the PlatformAudio API and the worker-thread marshaling.

Close peer connections before awaiting signal teardown

SessionInner::close released the peer connections only after two awaits that can block
indefinitely, so cancelling close() — for example by wrapping it in a timeout — left the
transports open and their ICE UDP sockets bound for the lifetime of the process. Long-lived
clients eventually exhausted their file descriptors. The transports are now closed before
the first await, which makes the teardown safe to cancel.

Moves the internal region-discovery cache into a new livekit-region crate. No

public API or behaviour change.

Moves the signalling client into a new livekit-signaling crate. livekit-api

re-exports it under the historical livekit_api::signal_client path, now marked
deprecated: it is internal SDK API, and dependents should use livekit-signaling
directly. livekit-api no longer depends on livekit-net.

Also drops two dependencies that were declared but never used: scopeguard and
bytes.

Expose network_type on IceCandidateStats

Chromium's local RTCIceCandidateStats carries a non-standard networkType field (WiFi,
cellular, ethernet, etc.), but IceCandidateStats had no place to put it, so it was silently
dropped during get_stats() deserialization. Adds network_type: Option<String> to the struct;
non-breaking since it already derives #[serde(default)].

livekit-uniffi 0.1.10 (2026-09-04)

Features

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol
  • Add self_test_http_get / self_test_ws_echo / has_http_client / has_ws_client UniFFI exports so foreign hosts can exercise the transport seam end-to-end.

livekit-common 0.1.3 (2026-09-04)

Fixes

  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol

livekit-ffi 0.12.77 (2026-09-04)

Features

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol
  • Fix pre-encoded frame segfault on macOS
  • Handle capture of dmabuf using existing capture path
  • Add self_test_http_get / self_test_ws_echo / has_http_client / has_ws_client UniFFI exports so foreign hosts can exercise the transport seam end-to-end.

Make AdmProxy worker-thread-affine: all platform ADM access now happens on the WebRTC worker thread, matching the ADM threading contract.

  • The platform ADM is now created lazily on the first PlatformAudio acquire on all platforms, so apps that never use platform audio never construct it.
  • Fixes Android platform recording delivering no audio: the audio transport was never registered on the lazily created ADM.
  • Fixes a shutdown race by keeping the runtime threads alive as long as Rust can reach the audio device controller.
  • Adds a platform_audio example exercising the PlatformAudio API and the worker-thread marshaling.

Close peer connections before awaiting signal teardown

SessionInner::close released the peer connections only after two awaits that can block
indefinitely, so cancelling close() — for example by wrapping it in a timeout — left the
transports open and their ICE UDP sockets bound for the lifetime of the process. Long-lived
clients eventually exhausted their file descriptors. The transports are now closed before
the first await, which makes the teardown safe to cancel.

Moves the internal region-discovery cache into a new livekit-region crate. No

public API or behaviour change.

Moves the signalling client into a new livekit-signaling crate. livekit-api

re-exports it under the historical livekit_api::signal_client path, now marked
deprecated: it is internal SDK API, and dependents should use livekit-signaling
directly. livekit-api no longer depends on livekit-net.

Also drops two dependencies that were declared but never used: scopeguard and
bytes.

Expose network_type on IceCandidateStats

Chromium's local RTCIceCandidateStats carries a non-standard networkType field (WiFi,
cellular, ethernet, etc.), but IceCandidateStats had no place to put it, so it was silently
dropped during get_stats() deserialization. Adds network_type: Option<String> to the struct;
non-breaking since it already derives #[serde(default)].

livekit-token 0.1.2 (2026-09-04)

Fixes

  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol

livekit-region 0.1.1 (2026-09-04)

Fixes

Moves the internal region-discovery cache into a new livekit-region crate. No

public API or behaviour change.

livekit-data-stream 0.1.4 (2026-09-04)

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol

livekit-signaling 0.1.1 (2026-09-04)

Features

Fixes

Moves the signalling client into a new livekit-signaling crate. livekit-api

re-exports it under the historical livekit_api::signal_client path, now marked
deprecated: it is internal SDK API, and dependents should use livekit-signaling
directly. livekit-api no longer depends on livekit-net.

Also drops two dependencies that were declared but never used: scopeguard and
bytes.

livekit-net 0.1.3 (2026-09-04)

Features

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add self_test_http_get / self_test_ws_echo / has_http_client / has_ws_client UniFFI exports so foreign hosts can exercise the transport seam end-to-end.

livekit-token-source 0.1.3 (2026-09-04)

Features

Fixes

livekit-datatrack 0.1.15 (2026-09-04)

Features

Fixes

  • Add data streams v2 to exposed uniffi interface - Data streams v2 uniffi #1286 (@1egoman)
  • Add the PASSTHROUGH encoding preset and remove the unused UpdateEgressRequest from the generated protocol

libwebrtc 0.3.47 (2026-09-04)

Features

Expose network_type on IceCandidateStats

Chromium's local RTCIceCandidateStats carries a non-standard networkType field (WiFi,
cellular, ethernet, etc.), but IceCandidateStats had no place to put it, so it was silently
dropped during get_stats() deserialization. Adds network_type: Option<String> to the struct;
non-breaking since it already derives #[serde(default)].

Fixes

  • Fix pre-encoded frame segfault on macOS

Make AdmProxy worker-thread-affine: all platform ADM access now happens on the WebRTC worker thread, matching the ADM threading contract.

  • The platform ADM is now created lazily on the first PlatformAudio acquire on all platforms, so apps that never use platform audio never construct it.
  • Fixes Android platform recording delivering no audio: the audio transport was never registered on the lazily created ADM.
  • Fixes a shutdown race by keeping the runtime threads alive as long as Rust can reach the audio device controller.
  • Adds a platform_audio example exercising the PlatformAudio API and the worker-thread marshaling.

@knope-bot
knope-bot Bot requested review from jhugman and ladvoc as code owners August 26, 2026 13:55

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@knope-bot
knope-bot Bot force-pushed the knope/release branch 2 times, most recently from 3840927 to f03216d Compare August 27, 2026 19:36
@knope-bot
knope-bot Bot requested a review from lukasIO as a code owner August 27, 2026 19:36
@knope-bot
knope-bot Bot force-pushed the knope/release branch 2 times, most recently from 72c4137 to 065c3d5 Compare August 28, 2026 22:44
@knope-bot
knope-bot Bot requested a review from cloudwebrtc as a code owner August 28, 2026 22:44
@knope-bot
knope-bot Bot force-pushed the knope/release branch 3 times, most recently from a96ef5b to abe5c97 Compare September 1, 2026 02:38

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

This report is out of date. Scroll down for Devin Review's latest report on this PR.

Devin Review found 1 new potential issue.

⚠️ 1 issue in files not directly in the diff

⚠️ FFI clients lose network type

When Chromium reports networkType, network_type captures it only in Rust. FFI conversions discard it, so foreign clients never receive the released field.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

@knope-bot
knope-bot Bot force-pushed the knope/release branch 2 times, most recently from b6b391c to c5bcc04 Compare September 1, 2026 19:33

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 new potential issue.

2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)

Devin Review

Comment thread livekit/Cargo.toml
[package]
name = "livekit"
version = "0.8.4"
version = "0.8.5"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Breaking changes ship as patches

livekit 0.8.5 removes runtime features while remaining compatible with ^0.8.4. Existing consumers can receive it automatically and stop building.

Prompt for agents
The remove_livekit_runtime changeset classified nine affected crates as minor releases, but this release commit increments only patch versions. For pre-1.0 Cargo packages, existing caret requirements accept patch updates, so consumers pinned compatibly to the previous versions can resolve releases that removed runtime features and public APIs. Reissue the affected versions at the next minor boundary and keep the root workspace dependency versions, Cargo.lock entries, changelogs, and Node FFI package versions synchronized. Affected crates are livekit, libwebrtc, livekit-api, livekit-datatrack, livekit-ffi, livekit-net, livekit-signaling, livekit-token-source, and livekit-uniffi.
Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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.

0 participants