Skip to content

chore(master): release 2.0.0#17

Merged
luke-speechify merged 1 commit into
masterfrom
release-please--branches--master--components--speechify-api
Jun 22, 2026
Merged

chore(master): release 2.0.0#17
luke-speechify merged 1 commit into
masterfrom
release-please--branches--master--components--speechify-api

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

2.0.0 (2026-06-22)

⚠ BREAKING CHANGES

  • Speechify(token=...) is now Speechify(api_key=...). The tts. namespace has been removed — call sites move from client.tts.audio.speech(...) to client.audio.speech(...) and from client.tts.voices.X to client.voices.X. The livekit extra-dependency has been removed; if you were importing it transitively through speechify-api, install it explicitly. Generator-line crossed 4.x5.x, so internal/private code paths have moved.

Features

  • regenerate SDK on fern-python-sdk@5.14.20 with TTS-only surface (#16) (2ebb0a5)

This PR was generated with Release Please. See documentation.

@luke-speechify luke-speechify merged commit 06b3adc into master Jun 22, 2026
4 checks passed
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

luke-speechify added a commit that referenced this pull request Jun 22, 2026
release-please tagged 2.0.0 and updated .release-please-manifest.json
in #17, but its python release-type didn't update [tool.poetry] version
in pyproject.toml (likely tripped by the [project] dynamic = ["version"]
pattern). Result: the publish job built and uploaded speechify_api-1.2.4
artifacts again instead of 2.0.0.

This commit aligns the version sources with the existing 2.0.0 tag +
manifest. The actual speechify-api 2.0.0 PyPI publish is being done
manually with these contents (poetry build + poetry publish locally).

Follow-up: fix release-please-config.json so the next bump finds and
updates [tool.poetry] version automatically — either point version-file
at pyproject.toml explicitly, or remove the [project] dynamic block in
favour of a PEP 621 [project] version field that release-please can
parse on its own.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant