livekit-api v1.2.2 - #824
github-actions[bot] wants to merge 1 commit into
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| @@ -1 +1 @@ | |||
| __version__ = "1.2.1" | |||
| __version__ = "1.2.2" | |||
There was a problem hiding this comment.
🟡 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.
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Merging this PR will publish livekit-api v1.2.2 to PyPI.