[cloudwebrtc]

To confirm ffi-bindings upgrade to 0.12.76+ (libwebrtc m150, with WARP enabled by default).

[changeset-bot]

🦋 Changeset detected

Latest commit: fe18cb6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@livekit/rtc-node	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Copilot]

🔵 Needs a closer look

Native runtime compatibility and the described libwebrtc/WARP behavior require cross-platform validation not established by this review.

No open issues 🎉

1 file not reviewed

• pnpm-lock.yaml: Generated file

What changed in this PR

Updates the RTC package’s native bindings from 0.12.73 to 0.12.83, targeting the described libwebrtc m150 upgrade with WARP enabled by default.

Changes:

• Bumps the pinned bindings dependency.
• Synchronizes lockfile versions and integrity hashes for all supported platform binaries.

File	Description
pnpm-lock.yaml	Updates bindings and platform-specific dependency resolutions.
packages/​livekit-rtc/​package.json	Pins RTC bindings to 0.12.83.

_{Review effort: Balanced}

[1egoman]

Note that the e2e tests still seem to fail periodically with the below:

⎯⎯⎯⎯⎯ Uncaught Exception ⎯⎯⎯⎯⎯
Error: trying to drop an invalid handle
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'GenericFailure' }
This error originated in "src/tests/e2e_data_streams.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

This seems to be flaky starting with this FFI update, in previous FFI releases this was fine. My current theory is that livekit/rust-sdks#1395 is causing ffi objects to be double disposed. I've opened a PR here to try to fix this: livekit/rust-sdks#1539

[1egoman]

I gave this a shot with agents-js locally and it looks good to me!

Two nitpicks:

• Consider bumping to 0.13.1 as it has been released within the past few hours and has a small security related fix.
• Please add a changeset (run npx @changesets/cli and follow the prompts) before merging.