chore(release): v1.1.0 — PyPI packaging - #23
Merged
Merged
Conversation
Swap pipecat-local-stt-server from git-URL pin to PyPI (>=0.1.2,<0.2; 0.1.2 is the release of the previously pinned commit 5062b98 == v0.1.2), removing the direct-reference metadata PyPI rejects. Drop the now-unneeded hatch allow-direct-references. Add readme/authors/urls/classifiers for the PyPI page. Fold [Unreleased] into 1.1.0 and bump the menubar plist.
Tag push v* -> test + build + metadata guards -> publish behind the 'pypi' GitHub environment with OIDC (no stored token). Guards: tag must equal pyproject version; wheel metadata must carry no direct-URL deps (the class of failure PyPI rejects at upload).
- CHANGELOG [1.1.0]: surface the release.yml trusted-publishing workflow - AGENTS.md: 'Releasing to PyPI' paragraph next to the version-surfaces contract (tag-push trigger, one-time PyPI/GitHub setup, no-direct-URL rule) - blackhole-fallback.md: PyPI install one-liner alongside the checkout path
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unblocks publishing onoats to PyPI (name is free; the previous blocker was the git-URL dependency, which PyPI rejects).
pipecat-local-stt-server: git-URL pin → PyPI>=0.1.2,<0.2. Verified equivalence: the pinned commit5062b98is exactly tagv0.1.2, which is the published 0.1.2. Upper bound<0.2until the 0.2/0.3 wire protocol is live-smoked against the recorder.tool.hatch.metadata.allow-direct-references(no longer needed; future direct refs now fail loudly).readme,authors,[project.urls], classifiers.[stt] languagefeature from PR feat(stt): make decode language a first-class config.toml key #22); CHANGELOG[Unreleased]folded into[1.1.0]; menubarInfo.plistbumped (1.1.0 / build 2).Verification:
uv syncresolves stt-server from PyPI (0.1.2); full suite 266 passed;uv buildwheel metadata has no direct-URLRequires-Dist, embeds the README as long description, and carries the new URLs/classifiers.After merge: tag
v1.1.0, thenuv publishwith a PyPI token.CI release workflow (added in this PR)
.github/workflows/release.yml: pushing av*tag runs the full suite + build with two guards (tag == pyproject version; no direct-URL deps in wheel metadata), then publishes via PyPI trusted publishing (OIDC, no stored token) gated behind thepypiGitHub environment.One-time setup after merge (manual, on the web):
onoats, ownervr000m, repoonoats-bot, workflowrelease.yml, environmentpypi.pypi(optionally add yourself as required reviewer to make every publish a click-to-approve).Then
git tag -a v1.1.0 && git push origin v1.1.0performs the release.