release: 1.2.0 (stt-server client >=0.3.3,<0.4) - #25
Merged
Conversation
Keep the client library in lockstep with the running server generation. 0.3.3 added UDS trust-boundary hardening (0700 socket-dir enforcement + peer-cred 403); wire protocol stays "0.1", so the recorder client code is unchanged. Verified: client imports clean, PROTOCOL_VERSION == 0.1, empty-env resolver still returns all-None (onoats pipecat-path default override still fires), websockets resolves to 16.0 (satisfies onoats >=13 and the server's new >=16,<17). Full suite: 295 passed.
Bump version across all surfaces (pyproject, uv.lock, Info.plist) and date the CHANGELOG entry. 1.2.0 ships the previously-unreleased onoats stop subcommand, menu-bar Stop for orphaned/external sessions, and the stop->immediate-start pid-file race fix, plus the stt-server client bump to >=0.3.3,<0.4. Note: 1.1.0 is already published on PyPI (2026-06-13), so 1.2.0 is the next publishable version.
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
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.
Summary
Release 1.2.0, bringing the bundled
pipecat-local-stt-serverclient library in lockstep with the running server generation and cutting the previously-unreleased recorder-lifecycle work.This is a complete release PR — every version surface is bumped and
scripts/release_check.sh v1.2.0reports safe to tag. After merge, the release is justgit tag v1.2.0 && git push origin v1.2.0(triggersrelease.yml→ PyPI trusted publish). No follow-up PR needed.Dependency bump
pipecat-local-stt-server:>=0.1.2,<0.2→>=0.3.3,<0.4(resolves 0.3.3).403for cross-uid connections). The wire protocol stays"0.1", so the recorder's client code is unchanged — onoats connects to a separately-running server, it does not build or pull it.websocketsnow resolves to 16.0 (satisfies onoats's>=13and the server's new>=16,<17).koda-stt→pipecat-stt) does not bite onoats:runtime.py:253already hardcodes the post-rename default, and the 0.3.3 resolver returns all-Noneon empty env so that override fires.Release 1.2.0 (also ships previously-unreleased work)
pyproject.toml,uv.lock,native/onoats-menubar/Info.plist.CHANGELOG.md[1.2.0]dated 2026-06-28;[Unreleased]drained.onoats stopsubcommand, menu-bar Stop for orphaned/external sessions, and the stop→immediate-start pid-file race fix.Operator note (STT server, separate from this PR)
The 0.3.3 server refuses to start on a legacy
0755socket dir. Re-run the server installer (notgit pull+ barelaunchctl kickstart) so it self-heals0755→0700and restarts in one step. No client/protocol coordination is needed.Test plan
uv sync+ client sanity:PROTOCOL_VERSION == "0.1", empty-env resolver returns all-None, websockets 16.0.uv run pytest -q→ 295 passed (incl.test_release_meta.pyversion-surface guards).ruff format --check+ruff check→ clean.scripts/release_check.sh v1.2.0→ consistent, safe to tag.pyproject.toml:18Python>=3.12rationale still holds (0.3.3 PyPI metadata:requires_python == ">=3.12").