Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/livekit-rtc-ffi-bindings.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@livekit/agents': patch
---

update livekit rtc ffi bindings to 0.12.66
3 changes: 3 additions & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,9 @@
},
"packageManager": "pnpm@9.7.0",
"pnpm": {
"overrides": {
"@livekit/rtc-node>@livekit/rtc-ffi-bindings": "0.12.66"
},
Comment on lines +55 to +57

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.

🚩 pnpm override pins transitive dependency without upgrading the direct dependency

The override "@livekit/rtc-node>@livekit/rtc-ffi-bindings": "0.12.66" forces a specific version of @livekit/rtc-ffi-bindings regardless of what @livekit/rtc-node@^0.13.29 (from pnpm-workspace.yaml catalog) declares as its own compatible range. This is a common pattern for urgent fixes, but it creates a version mismatch that could cause runtime issues if @livekit/rtc-node expects a different ffi bindings version. This override should ideally be temporary until @livekit/rtc-node itself publishes a version that depends on the correct @livekit/rtc-ffi-bindings. Worth confirming this is intentional and tracking removal of the override.

Open in Devin Review

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

"patchedDependencies": {
"@changesets/assemble-release-plan": "patches/@changesets__assemble-release-plan.patch"
}
Expand Down
51 changes: 27 additions & 24 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading