chore(main): release 0.7.2 - #90
Closed
github-actions[bot] wants to merge 2 commits into
Closed
Conversation
github-actions
Bot
requested review from
GregHolmes,
deepgram-kiley and
dg-coreylweathers
as code owners
July 31, 2026 15:06
This was referenced Aug 11, 2026
Collaborator
|
Closing: a 0.7.2 cut now would publish a changelog advertising the #89 features (ForceEndTurn, |
GregHolmes
added a commit
that referenced
this pull request
Aug 11, 2026
#91) Reverts the listen v2 regen (`5b6323a`, originally #89: Flux force-end-turn, listen v1 diarize metadata + arch, word speaker confidence, `AgentV1UpdateListen` provider retype, `ListenV2Redact`) off `main`. Mirrors the equivalent revert on deepgram-python-sdk: deepgram/deepgram-python-sdk#757 ## Why This work isn't ready to ship yet, and other priorities need to release from `main` without it. Since the regen is already on `main`, any release cut from `main` (including the pending release-please 0.7.2, #90) would publish it. Reverting removes it from the release line cleanly, without rewriting history. ## Redoing the regen The regen commit `5b6323a` stays reachable in history (and on the #89 branch), and the next regen branch `gh/sdk-gen-2026-08-11` (#92) is stacked on this revert. **Caveat:** re-landing is a fresh 4.16.0 regen, not a replay of #89's hand-patches — see "Forfeited by this revert" below. ## Also reverted (not spec features) Beyond the five spec features, this 184-file revert also rolls back: - **Fern toolchain downgrade** (`.fern/metadata.json`): `cliVersion` 5.89.0 → 5.44.6, `generatorVersion` 4.16.0 → 4.10.1, `runtime-version` dropped. This is what makes most of the rest follow. - **Restores** the `ClientOptions.java` `.fernignore` freeze block + its release-please `generic` extra-file entry (both dropped by #89) — this is what keeps `X-Fern-SDK-Version` release-please-bumpable (no wire-version drift). - **Removes** the three 4.16.0-era stopgap freeze blocks (type-rename, return-type shim, union default-variant) and the `ListenV2ForceEndTurn` `hashCode()` entry from `.fernignore` and `AGENTS.md`. - **`README.md`**: removes the 4.16.0 retry-knob docs (retry-behavior prose that remains accurate has been restored — see the diff). ## Forfeited by this revert (tracked in #93) The revert also drops patches #89 carried that are **not** preserved on `gh/sdk-gen-2026-08-11` and **not** among #92's 17 reconciled patches (verified: all three unions read `defaultImpl = _UnknownValue.class` on #92, both tests absent): - **Union default-variant fix** (`defaultImpl = V2Value`) on `AgentV1UpdateListenListenProvider`, `AgentV1SettingsAgentListenProvider`, `AgentV1SettingsAgentContextListenProvider`. The two Settings unions carry this bug in **released 0.7.1** (pre-existing, not a regression), so the revert restores released behavior — it forfeits an *unreleased* fix. - **`AgentV1UpdateListenListen.getProvider()` additive return-type shim.** - **Regression guards** `AgentV1UpdateListenShimTest.java`, `AgentSettingsProviderDefaultTest.java`. Whether to re-apply the `defaultImpl` fix on #92 is a deliberate decision tracked in #93. ## Verification - `./gradlew compileJava compileExamples unitTest` — build successful, all unit tests pass. - The revert is a clean inverse of the single regen commit (184 files): `git diff 5b6323a^ HEAD` over the pre-README-fix tree is empty (byte-identical to the 0.7.1 release commit `8b3c605`). Restores pre-regen `.fern/metadata.json` (sdkVersion 0.7.1, generator 4.10.1), the `.fernignore` freeze blocks, and the `release-please-config.json` `ClientOptions.java` generic entry. - Escape-hatch (`additionalProperties`), forward-compat no-op, and fields-less `hashCode()` patches from 0.7.1 all survive.
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.
🤖 I have created a release beep boop
0.7.2 (2026-07-31)
Features
ForceEndTurnclient message (sendForceEndTurn(...)on the listen v2 WebSocket client) forces the model to finalize the current turn on demand, plus aredactconnect option (ListenV2Redact.NUMBERS/AGGRESSIVE_NUMBERS) that removes sensitive information from live transcripts;TurnInfoalso gains atriggerfield indicating what ended the turn. Also adds Listen v1 diarization metadata (diarizeInfoon response metadata plus per-wordspeaker/speakerConfidence), the mid-session agentUpdateListenprovider selection, and 12 new Flux (flux-*-en) text-to-speech voices. (#89) (5b6323a)This PR was generated with Release Please. See documentation.