Skip to content

Web: update livekit-client to 2.24.0 - #18

Merged
mdepinet merged 2 commits into
mainfrom
mike/claude-livekit-client-2.24
Nov 14, 2026
Merged

mdepinet merged 2 commits into
mainfrom
mike/claude-livekit-client-2.24

Conversation

@mdepinet

Copy link
Copy Markdown
Collaborator

Updates the web build's embedded livekit-client from 2.22.3 to 2.24.0, and fixes a build bug the update exposed.

livekit-client 2.24.0

  • Data-only receivers now follow a sender's ratchet. Before 2.24.0, a receiver that got data, but no media, from a sender couldn't decrypt that sender's data after it ratcheted its key (livekit/client-sdk-js#2187, fixed by #2188). src/web/README.md no longer lists this as a web difference. New test: test_data_only_receiver_follows_a_ratcheted_key. It fails on 2.22.3 (the data sent after the ratchet never arrives) and passes on 2.24.0. Natively, it's pending like the other E2EE tests.
  • 2.24.0 also splits livekit-client's Room into CoreRoom plus extensions, but the UMD build we embed still includes everything, and nothing in bridge.js needed to change. The license is still Apache-2.0.

Build fix

After a livekit-client version change, ./build.sh web in an existing checkout downloaded the new version but kept embedding the old one. npm gives every file in its packages the same 1985 timestamp, and SCons reuses a file's stored content signature when the file is over two days old and its timestamp hasn't changed. build.sh now extracts livekit-client with tar -m, so its files get the current time. CI wasn't affected, since its cache key includes build.sh. To check the fix, I switched an existing checkout between 2.22.3 and 2.24.0 in both directions, and each build embedded the right version.

Testing

./test_web.sh, with the integration and e2e tests against livekit-server --dev, runs 207 tests: all pass, and one is pending (monitor capture).

🤖 Generated with Claude Code

mdepinet and others added 2 commits November 12, 2026 02:53
npm gives every file in its packages the same 1985 timestamp, and SCons
reuses a stored content signature for a file older than two days whose
timestamp hasn't changed. So after a version change, ./build.sh web
downloaded the new livekit-client but kept embedding the old one.
Extracting with -m gives the files the current time instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
It fixes livekit/client-sdk-js#2187: a receiver that got data, but no
media, from a sender couldn't decrypt that sender's data once it ratcheted
its key. The web differences doc no longer lists it, and a new test
covers it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Approval recommended

No active review issues are recorded for the SDK update and accompanying build and encryption-test changes.

No open issues 🎉

What changed in this PR

Updates the web build’s embedded livekit-client to 2.24.0, fixes stale SDK embedding during incremental builds, and adds coverage for data-only encrypted receivers following key ratchets.

Changes:

  • Updates the SDK version and checksum.
  • Extracts SDK files with current timestamps so SCons detects version changes.
  • Adds a data-only key-ratchet regression test and removes the resolved limitation from the web documentation.
File Description
test/​e2e/​test_e2ee.gd Tests encrypted data delivery before and after a sender’s key ratchet, without media.
src/​web/​README.md Updates the SDK version and removes the data-only ratchet limitation.
build.sh Updates the SDK pin and checksum, and fixes extraction timestamps for incremental builds.

Review effort: Balanced

@mdepinet
mdepinet merged commit 25d0fdd into main Nov 14, 2026
7 checks passed
mdepinet added a commit to avinoamn/godot-livekit that referenced this pull request Nov 16, 2026
NodotProject#18's new data-only ratchet test called _skip_if_unsupported(), which this branch replaced with
per-test checks, so it uses _skip_if_no_server() now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants