Skip to content

release: 1.2.0 (stt-server client >=0.3.3,<0.4) - #25

Merged
vr000m merged 2 commits into
mainfrom
chore/bump-stt-server-0.3.3
Jun 28, 2026
Merged

release: 1.2.0 (stt-server client >=0.3.3,<0.4)#25
vr000m merged 2 commits into
mainfrom
chore/bump-stt-server-0.3.3

Conversation

@vr000m

@vr000m vr000m commented Jun 28, 2026

Copy link
Copy Markdown
Owner

Summary

Release 1.2.0, bringing the bundled pipecat-local-stt-server client 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.0 reports safe to tag. After merge, the release is just git tag v1.2.0 && git push origin v1.2.0 (triggers release.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).
  • 0.3.3 adds server-side UDS trust-boundary hardening (0700 socket-dir enforcement + peer-credential 403 for 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.
  • websockets now resolves to 16.0 (satisfies onoats's >=13 and the server's new >=16,<17).
  • Verified the v0.2.0 socket-path rename (koda-sttpipecat-stt) does not bite onoats: runtime.py:253 already hardcodes the post-rename default, and the 0.3.3 resolver returns all-None on empty env so that override fires.

Release 1.2.0 (also ships previously-unreleased work)

  • Version bumped across pyproject.toml, uv.lock, native/onoats-menubar/Info.plist.
  • CHANGELOG.md [1.2.0] dated 2026-06-28; [Unreleased] drained.
  • 1.2.0 also carries the already-merged-but-unpublished onoats stop subcommand, menu-bar Stop for orphaned/external sessions, and the stop→immediate-start pid-file race fix.

Note: 1.1.0 is already on PyPI (2026-06-13), so 1.2.0 is the correct next publishable version.

Operator note (STT server, separate from this PR)

The 0.3.3 server refuses to start on a legacy 0755 socket dir. Re-run the server installer (not git pull + bare launchctl kickstart) so it self-heals 07550700 and 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 -q295 passed (incl. test_release_meta.py version-surface guards).
  • ruff format --check + ruff check → clean.
  • scripts/release_check.sh v1.2.0 → consistent, safe to tag.
  • Verified pyproject.toml:18 Python >=3.12 rationale still holds (0.3.3 PyPI metadata: requires_python == ">=3.12").

vr000m added 2 commits June 28, 2026 02:23
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.
@vr000m
vr000m merged commit ebdd4c9 into main Jun 28, 2026
1 check passed
@vr000m
vr000m deleted the chore/bump-stt-server-0.3.3 branch June 28, 2026 09:36
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.

1 participant