release: 0.25.2 — streaming synthesis + idle-token deadline (#106)#107
Merged
Conversation
Ships the synthesis-reliability fix to npm: synthesis always streams (even in --json / non-TTY) bounded by an idle-token deadline, so a long generation completes in one pass and a stalled stream fails fast instead of burning 3x whole-call retries.
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.
Patch release shipping the #106 synthesis-reliability fix (merged but unreleased) to npm.
package.json0.25.1 → 0.25.2[0.25.2]entryUser-facing effect: synthesis on long or briefly-stalling generations is reliable — it streams in one pass and fast-fails a genuine stall instead of the old 120s whole-call timeout re-running the full generation 3×. Merging triggers
auto-release.yml(tag + GitHub release + npm publish).