Conversation
|
| Name | Type |
|---|---|
| @livekit/agents | Patch |
| @livekit/agents-plugin-openai | Patch |
| @livekit/agents-plugin-cartesia | Patch |
| @livekit/agents-plugin-deepgram | Patch |
| @livekit/agents-plugin-elevenlabs | Patch |
| @livekit/agents-plugin-google | Patch |
| @livekit/agents-plugin-livekit | Patch |
| @livekit/agents-plugin-neuphonic | Patch |
| @livekit/agents-plugin-resemble | Patch |
| @livekit/agents-plugin-rime | Patch |
| @livekit/agents-plugin-silero | Patch |
| @livekit/agents-plugins-test | Patch |
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
| @@ -1,5 +1,5 @@ | |||
| --- | |||
| '@livekit/agents': minor | |||
| '@livekit/agents': patch | |||
There was a problem hiding this comment.
After changing '@livekit/agents' to be a patch release, all plugins are properly resolved to 1.0.7 (the next patch version). My guess is doing a minor bump on '@livekit/agents' will trigger major bump on plugin packages, which does not make any sense though. cc @lukasIO
There was a problem hiding this comment.
agree this doesn't make much sense in our context, here's is an issue report talking about this problem
There was a problem hiding this comment.
changesets/changesets#1011 (comment) oh so it probably right. changeset will bump a major package version if one if its peer dependency has a minor bump.
There was a problem hiding this comment.
unfortunately yes.
It's probably worth employing the manual dependency patching you linked to until changesets/changesets#1132 is merged
This PR should fix the changeset of accidentally bumping all plugins to major version