Repository navigation
Version Packages - #2274
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Version Packages#2274github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
requested review from
1egoman,
lukasIO and
xianshijing-lk
as code owners
November 16, 2026 00:19
github-actions
Bot
force-pushed
the
changeset-release/main
branch
9 times, most recently
from
November 19, 2026 09:43
74af5af to
d7c5bc3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 19, 2026 10:02
d7c5bc3 to
3d1a83e
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
livekit-client@2.25.0
Minor Changes
lk.transcriptiondata streams and advertise client protocol 3 - #2093 (@1egoman)Patch Changes
Retransmit lost audio in single peer connection mode when RED is off, for example with E2EE. - #2270 (@jamesdawsonWD)
Await
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)Deprecate the
TranscriptionReceivedroom, participant and track events and theTranscriptionSegmenttype in favor of a text stream handler for thelk.transcriptiontopic - #2093 (@1egoman)Room events emitted right after a reconnect are no longer held back. The room went back to
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)Keep the last transceiver of the publisher connection when you unpublish its track. A stop of the only transceiver made the browser drop the transport of the connection, and the next publish sent no media. - #2282 (@lukasIO)
Keep the last audio transceiver and the last video transceiver of the publisher connection when you unpublish their tracks. After a stop of all transceivers, some browsers gave the next track new header extension ids, and the publish failed. - #2284 (@lukasIO)
Reject with a
TrackInvalidErrorfor a track stopped during a processor restart orsetProcessor()- #2280 (@lukasIO)Stop the transceivers of a track when you unpublish it or when the server rejects its publish. Chrome then frees their encoders (about 95 MB per screen share) before the room disconnects. This needs a server with protocol 19 or higher; with an older server the transceivers stay inactive as before. - #2249 (@lukasIO)
Add internal
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)