Repository navigation
Version Packages - #1986
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#1986github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
23 times, most recently
from
November 20, 2026 18:15
d21ddbe to
7ade4dc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 21, 2026 01:15
7ade4dc to
4e8c018
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/[email protected]
Patch Changes
Update the v1 thread schema for shared partitions, ordered history, and millisecond timestamps. - #1885 (@theomonnom)
AgentDB.Wire.Error: a numeric code, its name and a description; what each code means is agent-db's. - #1983 (@theomonnom)
AgentDB.Wire: Hello carries client_version; a frame is at most 16 MiB, both ways.
Dynacast support for data tracks. - #1662 (@ladvoc)
Restore function-call metadata on field 7 for approval identities, resumable tool and delegation state, and provider metadata, keeping incompatible legacy field 6 reserved. - #1885 (@theomonnom)
Add the
DataChannelRpcConnectionClosed(1506, "Connection closed") data channel RPC error code, used by the client SDKs when the caller's own room disconnects while a call is in flight - #1973 (@1egoman)Raise the SIP header value cap from 1 KB to 4 KB so carrier headers like Twilio's
X-Twilio-CallToken(Immutable Call Forwarding token with SHAKEN/STIR PASSporTs, >1 KB) passCreateSIPParticipantvalidation - #1750 (@rkfshakti)Preserve exact framework A2A task states and optional task labels in thread listings. - #1885 (@theomonnom)
github.com/livekit/[email protected]
Patch Changes
Update the v1 thread schema for shared partitions, ordered history, and millisecond timestamps. - #1885 (@theomonnom)
AgentDB.Wire.Error: a numeric code, its name and a description; what each code means is agent-db's. - #1983 (@theomonnom)
AgentDB.Wire: Hello carries client_version; a frame is at most 16 MiB, both ways.
auth:
VerifyWithKeyverifies a token with the algorithm its key picks, HS256 for a version 1 key and EdDSA for a version 2 key, andNewAccessTokenWithPrivateKeysigns a token with EdDSA.ParseAPITokenaccepts EdDSA tokens;Verifystays HS256 only. A version 2 token names its API key in thekidheader and has thetypheaderlivekit-v2+jwt, andVerifyWithKeyrefuses one that does not. Version 2 keys are not supported by any server yet, so do not use them - #1985 (@davidzhao)Tag
addressonClientInfoas PII, sologger.Protoredacts the client IP - #1999 (@anunaym14)Dynacast support for data tracks. - #1662 (@ladvoc)
Restore function-call metadata on field 7 for approval identities, resumable tool and delegation state, and provider metadata, keeping incompatible legacy field 6 reserved. - #1885 (@theomonnom)
Add
utils/netguard, a check that refuses internal and reserved addresses, for clients that connect to destinations a caller supplies:IsBlockedIP,CheckHost,BlockInternal,NewDialControl,ParseCIDR, andReportOnlyandReportOnlyContext, which report what a check would refuse and let the connection go ahead. Existing packages are unchanged. - #2004 (@pksgit)Raise the SIP header value cap from 1 KB to 4 KB so carrier headers like Twilio's
X-Twilio-CallToken(Immutable Call Forwarding token with SHAKEN/STIR PASSporTs, >1 KB) passCreateSIPParticipantvalidation - #1750 (@rkfshakti)Preserve exact framework A2A task states and optional task labels in thread listings. - #1885 (@theomonnom)
Add
TimeoutQueue.Oldest, when the least recently reset item was reset, so a caller can sleep until it times out instead of polling - #1988 (@paulwe)webhook: export
RedactSendErrorfor a host whose webhook owners are tenants. It gives the same text for a destination the dial guard refuses and one that does not resolve, and in any other error replaces each address in the private and reserved ranges thatBlockInternalrefuses.SendErroritself is unchanged.NewDialControlis exported so a caller can add blocked and allowed ranges. The dial guard refuses any zoned address that is not explicitly allowed. An IPv4-mapped range inblocked_cidrsorallowed_cidrsmatches as its IPv4 range, and one shorter than 96 bits is rejected. A blocked range also catches the IPv4 address that a NAT64, v4-compatible or 6to4 address embeds - #2000 (@anunaym14)Tag
whatsapp_biz_opaque_callback_dataonDialWhatsAppCallRequestandAcceptWhatsAppCallRequestas PII, sologger.Protoredacts it - #1990 (@anunaym14)