Version Packages

[github-actions]

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]

Minor Changes

• bump underlying dependencies - be7160d39ea57239a51fbf6ad2cbea1342cc1889 (@bcherry)
  fix load calculation
  report worker status

• cli: add runHeadless function - 36c553a60fef7621b9c4232b5c79555b2f83aad8 (@nbsp)

Patch Changes

• worker: JT_{PUBLISHER => ROOM} - 1c8caf04c148dfa57af4e844b6538d97d6be652a (@nbsp)

• Pass api key and secret to RoomServiceClient - #58 (@bcherry)

• Let defineAgent accept agent type - 24a4f58a23d4a3aad8620fcccabdab5d2e1152c7 (@lukasIO)

• Add transcript support to realtime voice assistant - 1063d2a25c4a01022948699e673d267d04c1ec05 (@bcherry)

@livekit/[email protected]

Minor Changes

• mark omniassistant as alpha - #59 (@nbsp)

Patch Changes

• Fix assistant startup process - #36 (@bcherry)

• Send agent transcript progressively and handle interruptions - #40 (@bcherry)

• Add transcript support to realtime voice assistant - 1063d2a25c4a01022948699e673d267d04c1ec05 (@bcherry)

• Updated dependencies [1c8caf04c148dfa57af4e844b6538d97d6be652a, 5923b1a796642bec4892f41545ea1be1c6b9fb36, be7160d39ea57239a51fbf6ad2cbea1342cc1889, 24a4f58a23d4a3aad8620fcccabdab5d2e1152c7, 1063d2a25c4a01022948699e673d267d04c1ec05, 36c553a60fef7621b9c4232b5c79555b2f83aad8]:

  • @livekit/[email protected]

livekit-agents-examples@null

livekit-agents-examples

null

Minor Changes

• bump underlying dependencies - be7160d39ea57239a51fbf6ad2cbea1342cc1889 (@bcherry)
  fix load calculation
  report worker status

Patch Changes

• Fix assistant startup process - #36 (@bcherry)

• Send agent transcript progressively and handle interruptions - #40 (@bcherry)

• Updated dependencies [1c8caf04c148dfa57af4e844b6538d97d6be652a, 5923b1a796642bec4892f41545ea1be1c6b9fb36, ccff5ce34d071a0fb449da5ce77938e346679b1b, be7160d39ea57239a51fbf6ad2cbea1342cc1889, 5c320c88a04ffd8b7753696d4172a610fbe1bc2b, 24a4f58a23d4a3aad8620fcccabdab5d2e1152c7, 1063d2a25c4a01022948699e673d267d04c1ec05, 36c553a60fef7621b9c4232b5c79555b2f83aad8, 7e6bb7fbf661e6c6aa012f6a362b84d542d2c84e]:

  • @livekit/[email protected]
  • @livekit/[email protected]

[nbsp]

@lukasIO you probably know more about this then i do: is 0.1.0 already released? can we pull it so that it only releases when it's production-ready? i don't want to push this to dev preview when it's 0.5.0 or even 0.1.1 that feels weird

[lukasIO]

0.1.0 is released, but with restricted access, so only people with a valid npm token for the livekit org can actually use/download it. This happened the first time the release github action ran successfully.

changesets also has a pre-release mode where you can specify a tag name e.g. alpha or dev which would then not get released under the latest tag on npm. Not sure if that's necessary though as long as the package access is restricted.

[nbsp]

i see. my issue was more that it'd be nice if the first public version was 0.1.0 and not 0.1.1, but i suppose that's not possible to undo now?

[lukasIO]

ah, damn. No, this would have been only possible within the first 24hrs since publishing. Sorry about that, didn't know about that intention.

What we can do, is to deprecate the release, so it will disappear from npm's website, but that will still make 0.1.1 the next version in line