fix(packaging): make the SDK installable from source [DRG-31]#11
Merged
Conversation
The generated pyproject carried a partial PEP-621 `[project]` table
(name only, no version/dependencies) alongside the real `[tool.poetry]`
config. PEP-621 build frontends (uv, pip git installs) validate
`[project]` and fail ("project.version neither set nor in dynamic"), so
`pip install git+...` / uv source installs were broken (PyPI wheels were
unaffected). Drop the vestigial `[project]`/`[project.urls]` tables and
move the URLs under `[tool.poetry.urls]` so poetry-core fully owns the
metadata. `uv build` now produces sdist + wheel.
NOTE: hand-patch of a generated file; the durable fix is upstream in the
Fern python generator's pyproject emission.
lspeechify
added a commit
that referenced
this pull request
Jun 17, 2026
Resolve conflicts with the release-please landing from master (PR #10, PR #11): - src/speechify/core/client_wrapper.py: keep the 1.2.4 version bump from realtime-connect and apply master's `# x-release-please-version` marker so release-please can manage the X-Fern-SDK-Version header from here on. - .github/workflows/release-please.yml: keep realtime-connect's python-version 3.12 (livekit / realtime requires >=3.9) instead of master's 3.8 baseline. The file is the renamed ci.yml from master's release-please workflow. - pyproject.toml: auto-merged cleanly. The fix(packaging) commit (3ae1442) was cherry-picked to master via PR #11, so both branches apply the same structural fix; realtime-connect's 1.2.4 version is preserved. - .fernignore: auto-merged (both branches added non-overlapping entries). - context7.json: pulled the URL fix that landed on master via PR #6. Release-please will reconcile the 1.2.4 → next version on the first run after this PR lands (feat! in the PR title will drive a major bump).
lspeechify
added a commit
that referenced
this pull request
Jun 17, 2026
Regenerated SDK after adding `audiences: [tts]` to the python and
typescript groups in the upstream `speechify-api/fern/generators.yml`.
This drops every endpoint that carries `x-fern-audiences: [voice-agents]`
in `apps/server/swagger.yaml` — 144 of the 150 operations — leaving just
the 6 TTS operations (audio + voices).
Removed:
- All `src/speechify/agent/*` and the historical `src/speechify/tts/{agents,auth,conversations,tools,...}` subtrees.
- The hand-written `src/speechify/realtime/` layer (it accepts a
conversation produced by `client.agent.create_conversation()`; with
agent endpoints gone there is no way to produce that input).
- Livekit dependency (only needed by the realtime layer).
- Python 3.9 floor / 3.12 CI bump that landed for livekit.
Re-applied PR #11's pyproject structural fix on top of the fresh
regeneration: Fern's python generator re-emits the partial PEP-621
`[project]` table with `name` only, which release-please's
`release-type: python` rejects. Same fix as before — drop the
versionless `[project]` table and move URLs under `[tool.poetry.urls]`.
Durable fix is upstream in the Fern python generator's pyproject
emission.
The version mismatch (`pyproject.toml` 1.2.4 vs `client_wrapper.py`
1.2.3) is intentional and transient — release-please owns versioning
post-merge and will reconcile on the next release PR. The `feat!:`
marker drives a semver-major bump.
BREAKING CHANGE: all voice-agents endpoints (agent.*) are removed from
the Python SDK. Use the API directly or wait for a dedicated
voice-agents SDK.
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.
Cherry-pick of
3ae1442fromrealtime-connect(PR #8).pyproject.tomlon master carries a partial PEP-621[project]table withnameonly and noversion. This breaks two consumers today:release-type: pythonerrors withinvalid file(failing run) because PEP 621 treats a versionless[project]as invalid.pip install git+.../uvsource installs — PEP-621 build frontends fail withproject.version neither set nor in dynamic. PyPI wheels are unaffected because they bypass the source build.Pulled out of PR #8 as a standalone fix so master's release-please workflow stops failing while PR #8 continues to bake. The commit is byte-identical to the one in
realtime-connect, so merging this first leaves the hunk a no-op for PR #8.