Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
49e5a8a to
088a45a
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
088a45a to
79b1f7e
Compare
|
[Commenting to indicate this PR is being closed due to cleanup process] |
github-actions
bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
4ddc397 to
db8653b
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
db8653b to
092bf0a
Compare
1egoman
approved these changes
Feb 19, 2026
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
2 participants
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/components-js-docs@0.1.73
Patch Changes
5e174e11d5ab6f8678ae144f11360e9cc6901d1e]:@livekit/components-core@0.12.13
Patch Changes
Adds in support for attachments and attributes fields into data streams - #1283 (@1egoman)
Update all livekit-client to not use internal exports - #1289 (@1egoman)
@livekit/components-react@2.9.20
Patch Changes
Remove misleading useIsMuted docs example - #1281 (@1egoman)
Updated dependencies [
f40ba89c44b57ca8004d0ccc45ab3e63de0cd4e5,176749aa10fc9807da985ec41b7442761c56f83b]:@livekit/component-docs-storybook@1.0.100
Patch Changes
5e174e11d5ab6f8678ae144f11360e9cc6901d1e]:@livekit/component-example-next@0.2.73
Patch Changes
5e174e11d5ab6f8678ae144f11360e9cc6901d1e]:@agents-ui@1.0.3
Patch Changes
5e174e11d5ab6f8678ae144f11360e9cc6901d1e]:@livekit/components-docs-gen@0.0.95
Patch Changes
5e174e11d5ab6f8678ae144f11360e9cc6901d1e]: