feat!: regenerate SDK for API 2026-09-13 with consent-challenge voice cloning - #27
Merged
Merged
Conversation
… cloning Empty commit to re-trigger release-please for the 4.0.0 release. No code changes here; #26 is already on main. The squash commit for #26 could not be parsed by release-please. A multi-line Python example in the body left an open bracket at the end of a line, which the conventional-commit grammar rejects. The parse aborted, the commit was discarded, and feat! plus the breaking-change notes and the Release-As footer were never read, so no release PR was cut. Keep commit bodies free of multi-line code examples. BREAKING CHANGE: voices.create requires consent_challenge_id and consent_recording; the consent form field is gone. BREAKING CHANGE: GetStreamRequestModel moved from speechify.audio to speechify.types. BREAKING CHANGE: the default API version is now 2026-09-13. Release-As: 4.0.0
luke-speechify
pushed a commit
that referenced
this pull request
Aug 18, 2026
🤖 I have created a release *beep* *boop* --- ## [4.0.0](3.0.1...4.0.0) (2026-08-18) ### ⚠ BREAKING CHANGES * the default API version is now 2026-09-13. ### Features * regenerate SDK for API 2026-09-13 with consent-challenge voice cloning ([#27](#27)) ([f3f323d](f3f323d)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Empty commit to re-trigger release-please for the 4.0.0 release. No code changes here; #26 is already on main.
The squash commit for #26 could not be parsed by release-please. A multi-line Python example in the body left an open bracket at the end of a line, which the conventional-commit grammar rejects. The parse aborted, the commit was discarded, and feat! plus the breaking-change notes and the Release-As footer were never read, so no release PR was cut.
Keep commit bodies free of multi-line code examples.
BREAKING CHANGE: voices.create requires consent_challenge_id and consent_recording; the consent form field is gone.
BREAKING CHANGE: GetStreamRequestModel moved from speechify.audio to speechify.types.
BREAKING CHANGE: the default API version is now 2026-09-13.
Release-As: 4.0.0