Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use changesets/changesets for versioning #409

Merged
merged 10 commits into from
Jul 8, 2024
Merged

use changesets/changesets for versioning #409

merged 10 commits into from
Jul 8, 2024

Conversation

nbsp
Copy link
Member

@nbsp nbsp commented Jul 3, 2024

No description provided.

@nbsp nbsp requested review from davidzhao and lukasIO July 3, 2024 14:21
@nbsp nbsp force-pushed the nbsp/changesets branch from 919f041 to 8d9b52d Compare July 3, 2024 14:23
@nbsp nbsp requested a review from theomonnom July 3, 2024 14:28
scripts/bump_version Outdated Show resolved Hide resolved
@theomonnom
Copy link
Member

Not familiar with this CI, can it generate a CHANGELOG file for every package we have?

Copy link
Member

@theomonnom theomonnom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise lgtm!

livekit-agents/package.json Outdated Show resolved Hide resolved
livekit-plugins/livekit-plugins-elevenlabs/package.json Outdated Show resolved Hide resolved
.github/workflows/publish-package.yml Outdated Show resolved Hide resolved
@nbsp nbsp force-pushed the nbsp/changesets branch from 81d4f14 to a163c59 Compare July 4, 2024 15:49
@theomonnom
Copy link
Member

can you add livekit-plugins-rag and livekit-plugins-minimal before merging? 🙏

@nbsp nbsp force-pushed the nbsp/changesets branch from 5fae0f2 to 9f68eb6 Compare July 5, 2024 19:44
@nbsp nbsp force-pushed the nbsp/changesets branch from 9f68eb6 to a947bd7 Compare July 5, 2024 19:47
@nbsp
Copy link
Member Author

nbsp commented Jul 5, 2024

can you add livekit-plugins-rag and livekit-plugins-minimal before merging? 🙏

not merging until Lukas gets another look at this

@@ -0,0 +1,5 @@
{
"name": "livekit-plugins/livekit-plugins-cartesia",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is the name that will be shown to users, mb this is better?

Suggested change
"name": "livekit-plugins/livekit-plugins-cartesia",
"name": "livekit-plugins-cartesia",

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is because we don't know which packages are and which aren't under livekit-plugins unless we do this. it's easier to strip it in the CI than to figure out whether we need to add it

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's used programmatically to know where to cd in the CI

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we can add a comment either in the publish-package.yml (or in the README) about what naming format we expect/need for this logic to work. Just as a reference once we add more lateron.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe in the README for livekit-plugins-minimal, since that might be copied over as boilerplate for new packages?

Copy link
Contributor

@lukasIO lukasIO Jul 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good, the root README sounds also appropriate as the naming convention is not necessarily restricted to plugins

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

having trouble fitting this anywhere in the root README, it feels too end-user focused and this is internal dev doc
i think the plugin part is good, i don't assume we'll add anything to anywhere but the plugin directory in this repository

.github/workflows/publish-package.yml Outdated Show resolved Hide resolved
@@ -0,0 +1,5 @@
{
"name": "livekit-plugins/livekit-plugins-cartesia",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we can add a comment either in the publish-package.yml (or in the README) about what naming format we expect/need for this logic to work. Just as a reference once we add more lateron.

@nbsp nbsp merged commit 24e0b9e into main Jul 8, 2024
1 of 4 checks passed
@nbsp nbsp deleted the nbsp/changesets branch July 8, 2024 15:50
@theomonnom
Copy link
Member

Is it possible to push dev versions with it?
I want to bump livekit-agents to v0.8.0.dev0

chloyi pushed a commit to lumina-uoft/agents that referenced this pull request Jul 9, 2024
SuJingnan pushed a commit to SuJingnan/agents that referenced this pull request Nov 26, 2024
SuJingnan pushed a commit to SuJingnan/agents that referenced this pull request Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants