Skip to content

livekit-api v1.2.2 #824

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.

Sign up for GitHub

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

Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

livekit-api v1.2.2 #824

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion livekit-api/livekit/api/version.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1 +1 @@
__version__ = "1.2.1"
__version__ = "1.2.2"

@devin-ai-integration devin-ai-integration Bot Sep 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Duplicate API release publication

Merging __version__ 1.2.2 starts the PR publisher, which pushes an API tag. That tag starts the tag publisher, so one identical PyPI upload fails.

Learn more

The release workflow runs when a release pull request closes. Its tag job creates api-v1.2.2, while its API jobs independently build and publish the same version. The tag matches the trigger in Build API, whose publish job uploads another copy. PyPI does not permit replacing an existing filename, so whichever workflow uploads second fails. If the PR-triggered publisher loses, its dependent documentation job does not run.

Example: Merge the release/api-v1.2.2 pull request. publish.yml begins uploading livekit_api-1.2.2 and pushes api-v1.2.2; build-api.yml then uploads the same filenames. One workflow reports an existing-file error instead of completing the release path.

Recommended fix: Keep one publishing owner for API tags. Either stop publish.yml from directly publishing after creating the tag, or remove the tag-triggered publish behavior from build-api.yml. Ensure documentation depends on the surviving publisher.

Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Loading