Repository navigation
Update dependencies (non-major) - #55
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/dependencies-(non-major)
branch
7 times, most recently
from
November 17, 2026 16:55
f9bd20c to
b9f8444
Compare
renovate
Bot
force-pushed
the
renovate/dependencies-(non-major)
branch
from
November 19, 2026 20:23
b9f8444 to
f050de7
Compare
renovate
Bot
force-pushed
the
renovate/dependencies-(non-major)
branch
from
November 20, 2026 22:17
f050de7 to
2038f90
Compare
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
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
2.9.21→2.9.263.1.0→3.2.01.1.0→1.2.0150.1.1→150.2.07.21.0→7.22.07.5.1→7.5.258.0.22→58.0.2658.0.14→58.0.1658.0.18→58.0.2158.0.11→58.0.1258.0.15→58.0.1758.0.29→58.0.3258.0.12→58.0.1458.0.4→58.0.558.0.4→58.0.52.23.0→2.25.019.3.0→19.3.119.3.0→19.3.1~3.3.0→~3.5.04.7.1→4.8.0~5.10.1→~5.11.00.13.0→0.14.0Release Notes
livekit/components-js (@livekit/components-react)
v2.9.26: @livekit/components-react 2.9.26Compare Source
Patch Changes
v2.9.25Compare Source
Patch Changes
Keep chat setup stable when equivalent options are passed inline, preventing render loops and message history resets. - #1450 (@fatihcvs)
Link chat URLs whose scheme is not lowercase, such as
Https://, to that URL instead of prefixing anotherhttps://. - #1505 (@RaphaelFakhri)Update the local screen share track returned by useSession when screen sharing starts or stops. - #1447 (@fatihcvs)
Prevent outdated useToken requests from overwriting the token after the endpoint, room, or user changes. - #1454 (@fatihcvs)
Fix
TypeError: ...getLogger is not a functionon import in environments with a global AMD loader (define.amd). The bundledloglevelUMD wrapper now takes its CommonJS branch at build time, as in 2.9.23. - #1466 (@niconicocarrera)Mark the
trackparameter ofuseMediaDeviceSelectas deprecated. - #1473 (@RaphaelFakhri)Detect horizontal swipes that start or end at a clientX coordinate of zero. - #1452 (@fatihcvs)
Fix the agent-connect timeout leaking when a session ends early, which could fail the next session before its agent had a chance to connect. - #1469 (@1egoman)
Clear stale useParticipantAttribute values when switching to a participant or key without that attribute. - #1453 (@fatihcvs)
Use
areTokenSourceFetchOptionsEqualfromlivekit-clientinuseSessioninstead of a local copy, so the token fetch options comparison stays in sync with the SDK - #1479 (@ninglinLiu)Updated dependencies [
baf02cd,6bf0e61,b62a39f,e24c281,d4e449e,c94f414,6a3049f]:v2.9.24Compare Source
Patch Changes
Add
useAgentExpressionto the React SDK, reading the mood the agent publishes onlk.expression. - #1415 (@theomonnom)Preserve text stream attributes on transcript messages from
useSessionMessages- #1416 (@theomonnom)Updated dependencies [
28b189b,e05b190]:v2.9.23Compare Source
Patch Changes
livekit-client >= 2.20.1. That release ships theNonSharedUint8Array- #1360 (@1egoman)type declaration in its published types; earlier 2.19/2.20.0 builds referenced it
without shipping it, which broke type resolution for consumers (
skipLibCheck: false)and API Extractor. The local workaround shim is removed now that the type resolves
from livekit-client itself.
87220e4dd61b926023ce0d041e6fcf310f515edf]:livekit/client-sdk-react-native (@livekit/react-native)
v3.2.0Compare Source
Minor Changes
Update
@livekit/react-native-webrtcto 150.2.0, which renames its native classes so it can be installed in the same app as other react-native-webrtc forks. - #488 (@davidliu)Update both packages together: this release doesn't build against earlier
@livekit/react-native-webrtcversions, and earlier releases of this package don't build against 150.2.0. Expo users also need to update the Expo plugin.If your app uses any of these native names, switch to the new ones:
LKRNprefix. The Objective-C setup importsWebRTCModuleOptions.hinAppDelegate; change it to#import "LKRNWebRTCModuleOptions.h". UseLKRNWebRTCModuleOptionsin place ofWebRTCModuleOptions, in Swift too.NativeModules.LKRNScreenCapturePickerViewManager.show(reactTag)instead ofNativeModules.ScreenCapturePickerViewManager.show(reactTag).com.oney.WebRTCModule.*becomesio.livekit.reactnative.webrtc.*. Class names are unchanged, soWebRTCModuleOptionsis nowio.livekit.reactnative.webrtc.WebRTCModuleOptions.v3.1.1Compare Source
Patch Changes
Update
@livekit/react-native-webrtcto 150.1.1 - #483 (@davidliu)Fix
MediaRecorderduplicating audio data after it is stopped and started again - #478 (@RaphaelFakhri)livekit/client-sdk-react-native-expo-plugin (@livekit/react-native-expo-plugin)
v1.2.0Compare Source
Minor Changes
@livekit/react-native-webrtc150.2.0, which renames its native classes so it can be installed in the same app as other react-native-webrtc forks. This release requires@livekit/react-native3.2.0 or later and@livekit/react-native-webrtc150.2.0 or later. Plugin versions 1.0.2 to 1.1.0 don't build against@livekit/react-native-webrtc150.2.0, so update all three packages together. - #32 (@davidliu)livekit/react-native-webrtc (@livekit/react-native-webrtc)
v150.2.0Compare Source
react-navigation/react-navigation (@react-navigation/bottom-tabs)
v7.22.0Compare Source
Bug Fixes
Features
react-navigation/react-navigation (@react-navigation/native)
v7.5.2Compare Source
expo/expo (expo)
v58.0.26Compare Source
Patch Changes
/messagesocket and network inspector on port 443 when the bundle URL ishttpswith no port, such as anexpo start --tunnelURL. (#53466 by @vonovak)v58.0.25Compare Source
Patch Changes
Invalid statelog on iOS, and the same warning on Android, whenexpo/fetchcancels a response body. Cancelling before the first read now setsbodyUsed. (#53282 by @Kudo)v58.0.24Compare Source
Patch Changes
ExpoModulesCoreHeaderspackage, which depends on theexpo-modules-macrosSwift package. The SwiftPM plugin no longer links the macro plugin into the build folder, and the manifest needs no unsafe flags. (#53135 by @chrfalch)ExpoModulesCoreHeaderspackage. That package now depends on the React Native header products and the app's generated code package, the same as a module whose Package.swift the SwiftPM plugin generates. (#53289 by @chrfalch)ExpoModulesCoremodule after the precompiled headers change version. The SwiftPM plugin now gives the files it unpacks from a precompiled tarball the time of extraction. (#53211 by @chrfalch)v58.0.23Compare Source
Patch Changes
react-native-safe-area-contextto 5.11.1. (#52852 by @tsapeta)StatusBarhidden and style changes having no effect in apps built with the iOS 27 SDK. (#52728 by @alanjhughes)livekit/client-sdk-js (livekit-client)
v2.25.0Compare Source
Minor Changes
lk.transcriptiondata streams and advertise client protocol 3 - #2093 (@1egoman)Patch Changes
AudioContext.setSinkId()when switching the audio output withwebAudioMixenabled, so the switch only resolves (and emitsActiveDeviceChanged) once routing succeeds, and routing failures reject instead of becoming unhandled rejections - #2276 (@1egoman)TranscriptionReceivedroom, participant and track events and theTranscriptionSegmenttype in favor of a text stream handler for thelk.transcriptiontopic - #2093 (@1egoman)Connectedand emittedReconnectedwhile the engine still reported a pending reconnect until its attempt settled, so events such asRoomMetadataChangedorActiveSpeakersChangedsent in that window were buffered and never emitted. - #2186 (@ANDROIDHASSAN)TrackInvalidErrorfor a track stopped during a processor restart orsetProcessor()- #2280 (@lukasIO)setWrapperSdkInfoso SDKs built on top of livekit-client (e.g. Unity WebGL) report their own SDK and version inClientInfo, with livekit-client's version inother_sdks- #2265 (@MaxHeimbrock)v2.24.1Compare Source
Patch Changes
Stop re-sending the whole keyring to the E2EE worker on each
enableacknowledgement, which made the worker re-derive every key once per remote publication and delayed new keys behind that work. OnSignalConnected, only post the keys the worker has not received yet. Log the per-frame missing key warning only when the throttledMissingKeyerror is emitted. - #2250 (@facupedrazzini)Fix connecting on browsers without
Object.hasOwnorWeakRef(Safari before 15.4) - #2258 (@lukasIO)Report
REACT_NATIVEas the SDK in the v1 join request'sClientInfo, matching thesdk=reactnativequery param sent on the v0 signal path - #2262 (@MaxHeimbrock)Guard
instanceof Eventin the signal connect abort handler so React Native (no globalEvent) can still time out a hanging signal dial instead of throwingReferenceError. - #2224 (@ninglinLiu)performRpcnow rejects with the newCONNECTION_CLOSED(1506) error when the local participant disconnects from the room. Previously a pending call stayed pending until itsresponseTimeout, then rejected withRESPONSE_TIMEOUT. - #2251 (@u9g)v2.24.0Compare Source
Minor Changes
Create the publisher data channels as negotiated (fixed IDs) in single peer connection mode when the server supports it (protocol 18), saving the data channel open round trip. Falls back to in-band channels against older servers. - #2160 (@lukasIO)
Split
RoomintoCoreRoomplus extensions.createRoom(options, [extensions])fromlivekit-client/corebuilds a room with only the extensions an application needs;e2ee,frameMetadataanddataStreamstake their options directly.Room.dispose()releases a room for good. Video publishing (camera, screen share, simulcast, SVC, backup codecs) is thevideoextension; receiving video stays in core. The newlivekit-client/coreentry (ESM only, experimental) exportsCoreRoomand the extensions.simulateParticipantsand the legacy chat messages are extensions too; the core entry does not offer legacy chat. - #2141 (@lukasIO)Patch Changes
If the server disconnects the participant while
room.connect()is still waiting for the transports (e.g. aDUPLICATE_IDENTITYleave), the connection attempt is now cancelled. Previously it kept waiting untilpeerConnectionTimeout, then failed over to another region and rejoined with the same token after the room had already emittedDisconnected;room.disconnect()could not stop it because the room already looked disconnected. - #2177 (@tobelesa)Cancel an incoming data stream when its reader stops early (an aborted
signal, abreakout offor await, or a read error), so the stream is unregistered and later packets for it are dropped instead of buffering until the trailer arrives. A reader can no longer resume a stream after leaving its iteration early. - #2168 (@1egoman)Conform placeholder fmtp for codecs without an fmtp line - #2182 (@eleboucher)
add datatrack data channel to sync state info - #2159 (@lukasIO)
Fix data packet decryption after the sender ratchets its key:
DataCryptornow retries with the ratcheted key instead of the stored one - #2188 (@ninglinLiu)Mark data track unpublished after republish fail - #2170 (@1egoman)
Fix an unhandled promise rejection when the signal passed to
dataTracks.getDeferred()aborts, even though the caller catches the rejected promise. - #2156 (@Abhishek-B-R)Stop playing a remote audio track in Chrome once it is detached. - #2234 (@murilo-teleo)
Fix a memory leak where a
Roomwas never garbage collected after the application dropped it. - #2222 (@1egoman)Keep the H.264 PPS id readable in E2EE keyframes, so that Chrome no longer drops keyframes from encoders such as Intel Quick Sync - #2181 (@lukasIO)
fix(e2ee): keep the encryption state of received tracks per track - #2246 (@lukasIO)
fix(e2ee): track the local encryption state separately from remote participants - #2245 (@lukasIO)
Speed up the emulation prevention step for encrypted H.264 and H.265 frames.
writeRbspnow returns the input unchanged when no byte needs escaping, and otherwise copies runs of bytes instead of building a JS array. The output does not change. - #2184 (@lukasIO)Stop
Room.getLocalDevices()without a kind from callinggetUserMediawhen every device is already listed with a label. - #2232 (@RaphaelFakhri)Ignore a late participant update for an older session of a remote participant, so it no longer removes or replaces the participant's current session in
room.remoteParticipants. - #2229 (@Brian-1812)Follow a full reconnect that happens during the initial connection (e.g. after the server moves a client off dead UDP) instead of timing out on the closed transports and tearing down the recovered session. The room stays
Connectingwhile a resume, a restart or a browser offline event happens insideconnect()and emits noSignalReconnecting,ReconnectingorReconnected. Also stop polling the transports after the connection timeout, and reject an already-aborted transport wait as cancelled instead of leaving it pending. - #2135 (@rafaelhutter)Limit each remote participant to 500 concurrently open incoming data streams by default. Headers for new streams beyond the limit are dropped with an error log, so a participant can no longer exhaust a receiver's memory by opening streams it never closes. The limit can be changed with the
dataStream.maxOpenStreamsPerParticipantroom option. - #2214 (@1egoman)Fixes an issue where if a data stream runs into a terminal error, any packets delivered afterwards will be treated as if the stream doesn't exist (and not throw a sync error) - #2167 (@1egoman)
Apply the
peerConnectionTimeoutconnect option to the negotiation deadline - #2189 (@ninglinLiu)Fix the microphone pre-connect buffer never starting when
preConnectBufferis passed via publish options. - #2252 (@1egoman)fix published type declarations for consumers with
skipLibCheck: falseorexactOptionalPropertyTypes- #2175 (@lukasIO)Stop a disconnected
SignalClientfrom logging a spurious "ping timeout triggered" warning 15 s afterroom.disconnect(). - #2239 (@Brian-1812)Stop logging
error reading from signal streamat error level when the signal socket was closed by the client or replaced; the read failure is now logged at debug level with the ignored close - #2192 (@ninglinLiu)The debug log for a ratcheted E2EE key no longer includes the ratchet result, so the chain key and the new key material stay out of the console and out of log extensions. - #2213 (@lukasIO)
Keep
engine.pendingReconnectaccurate across reconnect attempts. A failed attempt no longer clears the handle of the retry it just scheduled (which madependingReconnectreadfalsewhile a retry was pending), and the flag now clears as soon as the reconnect timer is cleared. Buffered room events are also flushed when the engine finishes restarting if the room already reports connected. - #2193 (@1egoman)Emit
Reconnectedonce and keep room metadata and recording changes when a full reconnect fails over to another region - #2165 (@lukasIO)Fix dynacast never pausing video layers on React Native: save sender encodings before skipping the stats monitor - #2163 (@davidliu)
Wait for the first frame of a screen share before reading its dimensions, so its simulcast layers are announced at the size the capture delivers instead of the requested resolution. - #2217 (@CSantosM)
Ignore signal messages received after the WebSocket is closed on React Native - #2173 (@davidliu)
fix(room): skip a deferred track the server stopped sending - #2225 (@lukasIO)
Keep the mid to track id mapping of the current publisher answer when an answer to an older offer or an answer with an empty mapping arrives in single peer connection mode, so remote tracks whose
trackevent fires later are no longer dropped - #2196 (@ninglinLiu)If
room.disconnect()runs during the signal join, the connection attempt now rejects as cancelled instead of with aTypeError. A stale connection attempt no longer closes the engine of a newer connection or disconnects the room. - #2151 (@lukasIO)Fix
TokenSourcecaching: a failed fetch no longer leaves the previous response cached under the new options, andparticipantAttributesis compared by content - #2198 (@ninglinLiu)Document that
RemoteTrackPublication.videoQualityreturns the quality requested withsetVideoQuality(). It does not show the layer that adaptive stream or network bandwidth selects. - #2220 (@Brian-1812)Reject
WebSocketStream.openedwhen the socket closes before it opens, so that a failed, timed-out or aborted signal (re)connect on React Native no longer holds the connection lock. - #2179 (@sarankumar1325)react/react (react)
v19.3.1: 19.3.1 (October 14th, 2026)Compare Source
React Server Components
software-mansion/react-native-gesture-handler (react-native-gesture-handler)
v3.5.0[Compare Source](https://redirect.github.com/software-mansion/react-native-gesture-hand
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.