Bump livekit to 0.8.3 and livekit-api to 0.6.3 - #50
Open
MaxHeimbrock wants to merge 2 commits into
Open
Conversation
The released 0.7.x/0.5.x line is no longer buildable on a fresh resolution: livekit-protocol 0.7.12 added the wait_until_answered field to ConnectWhatsAppCallRequest, but livekit-api 0.5.6 (which declares livekit-protocol ^0.7.10) was published without initializing it. Main currently builds only because Cargo.lock pins livekit-protocol 0.7.10; any cargo update or added dependency re-resolves the graph and breaks the build. livekit 0.8.3 / livekit-api 0.6.3 is the coherent published set. Adapt StreamTextOptions/StreamByteOptions construction to the new builder API (struct init with Default is no longer available). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Closes the high-severity dependabot alert (remote memory exhaustion via unbounded out-of-order stream reassembly, patched in 0.11.15). Lockfile-only change; quinn-proto is a transitive dependency of the livekit QUIC stack. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Main currently builds only because of a stale
Cargo.lock. The released 0.7.x/0.5.x line is mutually broken on crates.io:livekit-protocol 0.7.12added thewait_until_answeredfield toConnectWhatsAppCallRequestlivekit-api 0.5.6declareslivekit-protocol = "^0.7.10"but was published without initializing that field, so it fails to compile against 0.7.12 witherror[E0063]: missing field wait_until_answeredAny fresh resolution —
cargo update, adding a dependency, or the next dependabot bump touching this subgraph — picks protocol 0.7.12 and breaks the build. The fix is only published in thelivekit 0.8.x/livekit-api 0.6.xline, which is the coherent set this PR moves to.Changes
livekit0.7.49 → 0.8.3,livekit-api0.5.4 → 0.6.3 (lockfile re-resolved:livekit-protocol0.7.12,livekit-common0.1.1,livekit-data-stream0.1.2,livekit-datatrack0.1.13)StreamTextOptions/StreamByteOptionsno longer implementDefault; construction adapted to the new builder API (new_with_topic(...).with_destination_identities(...))quinn-proto0.11.14 → 0.11.16 (lockfile-only): closes the open high-severity dependabot alert (remote memory exhaustion, patched in 0.11.15)Verification
cargo build✅cargo clippy --all-targets -- -D warnings --no-deps✅ (CI flags)cargo test✅ (no tests defined)🤖 Generated with Claude Code