feat(regen): add diarize_info, Flux force-end-turn, update-listen, word speaker confidence - #89
Merged
Merged
Conversation
GregHolmes
requested review from
deepgram-kiley and
dg-coreylweathers
as code owners
July 31, 2026 09:07
dg-coreylweathers
previously approved these changes
Jul 31, 2026
dg-coreylweathers
left a comment
dg-coreylweathers
left a comment
Contributor
There was a problem hiding this comment.
Approved — clean pre-regen prep. Verified:
- All 17 .bak snapshots are byte-identical to the patched originals on main (hash-compared each pair), so the reconciliation source-of-truth is faithful and complete.
- Unfreeze is complete: no original (non-.bak) path lingers in .fernignore that would silently keep a file frozen.
- Blast radius is exactly .fernignore + 17 .bak files — no original .java modified/deleted; patches (no_delay escape-hatch + arraysAsRepeats multi-value serialization) still intact on the originals.
- Permanent freezes untouched; functionally inert (.bak isn't compiled, no withSourcesJar() so nothing leaks to a published artifact).
One optional nit: the .bak files sit under src/main/java/ with no .gitignore coverage — carry a cleanup item into the reconciliation PR to delete them and restore the 17 .fernignore entries to their .java paths.
The real risk lives in the post-regen reconciliation, not here. When Fern overwrites the now-unfrozen originals it drops every manual patch; the .bak snapshots are the only safety net. The deepgram-sdk-review-regen pass must confirm all four patch families survive — especially the no_delay escape-hatch + multi-value WS serialization, plus the Flux oneOf non-breaking reshape (#1064) that the regen source carries. Leaving merge to Greg.
GregHolmes
changed the title
GregHolmes
changed the title
…enaming fern-java-sdk 4.16.0 unconditionally shortens provider type names, renaming public types that 0.7.x shipped (e.g. DeepgramSpeakProviderModel -> DeepgramModel). Rename them back and freeze the reverted leaf types + referencing payloads so the regen is source-compatible. Stopgap until the generator regression is fixed upstream.
- AgentV1UpdateListenListen: additive shim — getProvider() still returns DeepgramListenProviderV2 (0.7.x compat) while the new V1|V2 union is exposed via getProviderValue()/provider(DeepgramListenProviderV1) for model/language changes (#1066). - ConversationHistoryMessage / FunctionCallHistoryMessage: restored to 0.7.x shapes and re-added the two deleted ContextMessagesItem types (return-type changes can't be shimmed additively in Java). Frozen. Stopgap until the new shapes ship in a major.
GregHolmes
changed the title
GregHolmes
changed the title
Adds AgentV1UpdateListenShimTest — verifies the hand-written shim keeps the 0.7.x typed API (getProvider()/provider(V2)), exposes the union additively (getProviderValue()/provider(V1)), serializes the provider as the bare object once, and round-trips both V1 and V2.
`version` is optional on both DeepgramListenProviderV1 and V2, so a provider
object without it is a valid payload -- and is exactly what 0.7.x emitted and
parsed as a v2. Fern points the unions' @JsonTypeInfo defaultImpl at
_UnknownValue, whose @JsonCreator has an empty body, so such a payload
deserialized to an unknown variant carrying null: the provider getter returned
null and re-serializing emitted {"provider":null}, silently dropping the
caller's provider. _getUnknown() and equals() threw NullPointerException.
Measured against the released 0.7.1 jar, same input:
IN : {"provider":{"type":"deepgram","model":"nova-3"}}
0.7.1 : getProvider() = DeepgramListenProviderV2
before: getProvider() = null, re-serialize {"provider":null}
after : getProvider() = DeepgramListenProviderV2
Point defaultImpl at V2Value on all three agent listen-provider unions, which
matches the server's own default and restores 0.7.x behaviour. Jackson applies
defaultImpl for an absent OR unrecognized discriminator, so an unknown future
version now coerces to v2 rather than losing the provider; these messages are
client-sent, so the caller chooses the version. This leaves _isUnknown() and
_getUnknown() unreachable on these types.
AgentV1UpdateListenListenProvider is new in the 4.16.0 regen, so that one was a
regression. The two Settings unions shipped with the same defect in 0.7.1 and
are patched too, so all three behave consistently.
Fern emits equals() (all instances of a fields-less message are equal) but no hashCode(), violating the Object contract: two equal instances hash differently, so a HashSet built from one does not contain the other. ListenV2ForceEndTurn is new in this regen and was the only one of twelve fields-less types left unpatched -- the other eleven already carry the manual hashCode(), are frozen, and are asserted by RegenTypesTest. Bring it in line and add it to the existing contract assertion.
The regen added initialRetryDelayMillis, maxRetryDelayMillis and
retryJitterFactor to DeepgramApiClientBuilder only. Those return the parent
type, so using one mid-chain downgraded the static type and build() yielded a
DeepgramApiClient:
DeepgramClient client = DeepgramClient.builder()
.apiKey("k")
.initialRetryDelayMillis(500) // returns the parent type from here on
.build(); // error: DeepgramApiClient -> DeepgramClient
The hand-maintained wrappers already override apiKey/timeout/maxRetries and
friends for exactly this reason; the new methods just were not added. Override
all three in both the sync and async wrappers.
Worth a checklist item on future regens: when the generated parent builder gains
public methods, our frozen wrappers go stale silently -- nothing fails until a
consumer tries the fluent chain.
Freeze the three patched agent listen-provider unions and ListenV2ForceEndTurn so the fixes survive the next regen, and record each one in the temporarily-frozen list in AGENTS.md with the reason and the unfreeze condition. The two Settings provider unions were not frozen before, so without this the next regen would have silently reverted them.
… entry ClientOptions no longer carries x-release-please-version markers -- the regen replaced the hardcoded version strings with a manifest lookup (runtime-version: true), so the release-please "generic" updater had nothing left to rewrite in that file and silently no-opped. Remove the entry rather than leave it looking like that file's version is release-managed. The version now resolves via Package.getImplementationVersion(). pom.xml already stamped the manifest for the published artifact (mvn deploy); add the same to the Gradle jar task so both build paths carry a real Implementation-Version and the hardcoded fallback in ClientOptions stays unreachable in practice.
The Retry Configuration section showed only maxRetries while this release adds three backoff knobs and a per-request RequestOptions.maxRetries override. Note which statuses are retried, and show both. All snippets compile against the SDK.
dg-coreylweathers
approved these changes
Jul 31, 2026
dg-coreylweathers
left a comment
dg-coreylweathers
left a comment
Contributor
There was a problem hiding this comment.
Approved — full Fern 4.16.0 regeneration review (this supersedes the earlier prep-PR approval that was auto-dismissed when the head moved).
Independently verified (build gate run in Docker, not trusting CI):
- ./gradlew clean unitTest spotlessCheck compileExamples -> BUILD SUCCESSFUL, 104 tests, 0 failures; all new guard tests ran (shim, provider-default, regen-types hashCode, additionalProperties wire, forward-compat).
- Source-compat with 0.7.x: 0 removed/renamed public-type files vs v0.7.1; compileExamples (real usage code) green corroborates the surface.
- All 3 documented shims present and correct: type-rename reversal (short-named orphans not in tree), additive UpdateListen union shim, conversation-history reparent restored.
- Version-less provider drop fixed (defaultImpl=V2Value on all 3 agent listen-provider unions).
- hashCode on all 12 fields-less types incl. ListenV2ForceEndTurn; retry-tuning options reachable from both wrapper builders.
- no_delay escape hatch survived: wire test asserts it lands in the real upgrade URL on all 4 WS clients.
- New freezes complete + documented; .bak prep leftovers cleaned up; ClientOptions headers correct.
Two conditions, both about the RELEASE not the merge (details in Slack):
- Merge preserving the fix: commits (not squash-as-chore, or release-please cuts nothing) + add a 0.7.2 changelog stanza for the new features (diarize_info, speaker_confidence, force-end-turn, redact, gzip) so the release isn't undersold.
- Land docs #1069 (one line) so the now-unfrozen ClientOptions doesn't restamp the wrong Maven coordinate on the next regen. Order vs this PR doesn't matter for today's artifact; #1069 just must land before the next regen-from-main.
Cutting 0.7.2 today is safe: release CI does mvn deploy from committed source (no regen), and the correct headers are already committed here.
This was referenced Aug 11, 2026
Merged
GregHolmes
added a commit
that referenced
this pull request
Aug 11, 2026
…ads aren't dropped
Fern points the union @JsonTypeInfo defaultImpl at the empty-bodied _UnknownValue, so a
provider payload omitting the optional "version" discriminator (what 0.7.x emits)
deserialized to null and re-serialized as {"provider":null}, silently dropping the
provider. Patch defaultImpl = V2Value on the three agent listen-provider unions, freeze them
in .fernignore, and guard with AgentSettingsProviderDefaultTest. Re-applies the fix the #89
revert forfeited (issue #93).
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.
GregHolmes
added a commit
that referenced
this pull request
Aug 11, 2026
…ads aren't dropped
Fern points the union @JsonTypeInfo defaultImpl at the empty-bodied _UnknownValue, so a
provider payload omitting the optional "version" discriminator (what 0.7.x emits)
deserialized to null and re-serialized as {"provider":null}, silently dropping the
provider. Patch defaultImpl = V2Value on the three agent listen-provider unions, freeze them
in .fernignore, and guard with AgentSettingsProviderDefaultTest. Re-applies the fix the #89
revert forfeited (issue #93).
GregHolmes
added a commit
that referenced
this pull request
Aug 12, 2026
…provider + google version (#92) Regenerates the SDK against the latest Fern generator (`4.10.1` → `4.16.0`) and API spec (`ff8fd2b` → `03f0677`), reconciles the hand-maintained patches, and documents the resulting breaking changes with a migration guide. Supersedes the reverted #89. ## Base Stacked on the revert branch (#91). Until that merges, this PR's diff includes the revert commit; merge #91 first (or it rides along). ## ⛔ Blocked / do not merge yet Regenerated from an **unmerged spec branch**: `.fern/metadata.json` `originGitCommit` `03f0677` lives only on `origin/jherlihy/flux-tts-ga`, not on `deepgram-docs` `main`. The launch surface here (`breaks_applied`, `ConfigureFailure`, `expressivity`, `speed`, `redact`) exists only on that branch. Kept as a **draft** until it lands. - **Blocked-on:** `deepgram-docs#1094` (Flux TTS copy) + the `jherlihy/flux-tts-ga` spec branch merging to `deepgram-docs` `main`. ## Breaking changes (pre-1.0, source/compile-time only) All three follow the API definition; on-the-wire payloads for existing requests are unchanged. Full before/after in [`docs/Migrating-v0.7-to-v0.8.md`](./docs/Migrating-v0.7-to-v0.8.md). 1. **`AgentV1UpdateListenListen.provider`** retyped `DeepgramListenProviderV2` → `AgentV1UpdateListenListenProvider` (V1/V2 union). Wrap with `AgentV1UpdateListenListenProvider.v2(...)`; read via `getV2()`. 2. **`Google.version`** retyped `Optional<String>` → `Optional<GoogleThinkProviderVersion>`. Use the enum constants (`V1BETA`, `AI_STUDIO_V1BETA`, `GEMINI_ENTERPRISE_AGENT_V1`). 3. **`SpeakV2SpeechMetadataControlsApplied`** gains a required `breaksApplied` field (new builder step; new `getBreaksApplied()`). Read paths unaffected. Origin verified: #2 and #3 are new in the latest spec; #1's union shape existed in #89 but was previously hidden behind an in-SDK shim we intentionally did not carry forward. ## Reconciliation (post-regen review) Diffed each of the 17 `.bak` patches against the freshly generated originals — **all 17 still needed**, none dropped. `.fernignore` restored to its pre-prep state; all `.bak` files deleted. - **13 restored verbatim** (generator produced no other changes): the 11 fields-less `hashCode()` types, `ReconnectingWebSocketListener` (override hook / `connectionTimeoutMs` / `maxRetries(0)` semantics), and the `listen/v1` + `speak/v1` websocket clients (query-param repeats + `additionalProperties`). - **2 surgically merged** (`listen/v2` + `speak/v2` websocket clients): re-applied `QueryStringMapper` array-param serialization, the `additionalProperties` escape hatch, and the forward-compat unknown-message no-op, **while keeping the generator's new features** (speak/v2 `sendInterrupt`/`sendConfigure` + `onSpeechInterrupted`/`onConfigureSuccess`/`onConfigureFailure`; listen/v2 `redact`). - **`ClientOptions`**: kept the new retry-tuning options + `ResponseDecompressionInterceptor`; re-applied only the two `// x-release-please-version` header lines (colon SDK-name form), removed the generator's `getSdkVersion()` helper (build does not stamp the JAR manifest, so it would drift). ## Additive highlights Speak V2 interrupt/configure, Listen V2 `redact`, Speak V2 `speed`/`expressivity`, new Deepgram Flux TTS voices, client retry tuning, automatic response decompression. ## Tests added - `ListenV2ConnectWireTest`: new `redact` connect param (present as wire `numbers`, omitted when absent). - `RegenTypesTest` → "2026-08-11 regen type shapes": the three breaking shapes (provider union v2 factory/`getV2`/serialization, `Google.version` enum wire value, `ListenV2Redact` wire values). ## Verification - `./gradlew unitTest` ✅ · `spotlessCheck` ✅ · `compileExamples` ✅ - `./gradlew integrationTest` ✅ (Tier 1 + Tier 2 against a live key); opt-in Speak V2 WS integration ✅ (returned audio over the new v2 WS path) - Ran all non-`manage` examples: 19 pass, 7 long-running streaming/agent examples connected and worked, 4 environmental (proxy / file-arg / callback URL / SageMaker) — no SDK regressions. ## Post-review additions (from #91 review) - **Re-applied the union default-variant fix** the #89 revert forfeited (issue #93): `defaultImpl = V2Value` on `AgentV1UpdateListenListenProvider`, `AgentV1SettingsAgentListenProvider`, `AgentV1SettingsAgentContextListenProvider`, so a provider payload omitting the optional `version` discriminator (what 0.7.x emits) deserializes as V2 instead of dropping to `{"provider":null}`. Frozen in `.fernignore` + `AGENTS.md`, guarded by the re-added `AgentSettingsProviderDefaultTest`. The `getProvider()` return-type shim is intentionally **not** re-applied — that retype is a deliberate breaking change (see the migration guide). ## Core behavior changes (generator 4.10.1 → 4.16.0) Beyond the spec features, the generator upgrade changes core HTTP-client behavior worth calling out in the release notes: - **Automatic response decompression** is now installed by default (`ResponseDecompressionInterceptor`): gzip/deflate-encoded HTTP responses are transparently decoded. No API change; transparent to callers. - **New optional retry tuning** on `ClientOptions.Builder`: `initialRetryDelayMillis`, `maxRetryDelayMillis`, `retryJitterFactor`. All defaulted — existing behavior is unchanged unless set. ## Follow-ups - Once this lands, release-please cuts a fresh release at **0.8.0** (breaking `feat!`). - **Changelog needs a manual edit before releasing.** `5b6323a` (#89 `feat(regen)`) is still in release-please's range since `v0.7.1`, and release-please can't pair a revert with the commit it reverts — so the generated 0.8.0 notes will re-list the reverted #89 features (`diarize_info`, force-end-turn) under Features. Hand-edit the release PR's `CHANGELOG.md` to drop them before merging it. BREAKING CHANGE: `AgentV1UpdateListenListen.provider` is now `AgentV1UpdateListenListenProvider` (V1/V2 union); `Google.version` is now `Optional<GoogleThinkProviderVersion>`; `SpeakV2SpeechMetadataControlsApplied` has a new required `breaksApplied` field. See docs/Migrating-v0.7-to-v0.8.md. --------- Co-authored-by: fern-api[bot] <115122769+fern-api[bot]@users.noreply.github.com>
GregHolmes
added a commit
that referenced
this pull request
Aug 12, 2026
Replace the auto-generated 0.8.0 feature list with the clean summary used in the PR description, keeping the BREAKING CHANGES section. Drops the Reverts section and the superseded #89 feature line (release-please cannot pair a revert with the commit it reverts) so the published changelog reads as the net GA surface.
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
2 participants
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.
SDK regeneration for 2026-07-31 against fern-java-sdk 4.16.0, generated from the deepgram-docs
sdk-gen-2026-07-31branch (coordinate fix deepgram/deepgram-docs#1069 + Flux non-breaking reshape deepgram/deepgram-docs#1064 + cherry-picked spec PRs deepgram/deepgram-docs#1066, deepgram/deepgram-docs#1063, deepgram/deepgram-docs#1036, deepgram/deepgram-docs#1047).Source-compatible with 0.7.x — no breaking changes
Verified by a full breaking-change sweep against 0.7.1 (public API diffed from compiled trees): zero deleted public types, zero renames, zero removed or retyped getters — 1414 public types and 10,999 public members all still present. The generator (4.16.0) introduced several source-breaking changes that are shimmed back below.
Two caveats on "purely additive", for the record:
provider()overloads onAgentV1UpdateListenListenmake a bareprovider(null)ambiguous, so that one call no longer compiles. No working 0.7.x program is affected — it already threwNullPointerExceptionfromObjects.requireNonNull.ProviderStagegained two abstract methods, which technically breaks anyone implementing that generated builder-stage interface directly.New functionality (additive)
diarize_infoin listen v1 response metadata (deepgram-docs#1036)ListenV2ForceEndTurn+sendForceEndTurn(...)on the listen v2 WS client (deepgram-docs#1047)UpdateListencan now change model/language — exposed additively (see shim below) (deepgram-docs#1066)speaker/speaker_confidenceon pre-recorded words (deepgram-docs#1063)ListenV2Redact, retry-backoff tuning, and transparent gzip/deflate (ResponseDecompressionInterceptor)Back-compat handling for generator-introduced breaks (STOPGAP)
fern-java-sdk 4.16.0 renamed/reshaped public types 0.7.x shipped. These are patched back and frozen; drop once fixed upstream (Fern report pending):
DeepgramSpeakProviderModel→DeepgramModel,AnthropicThinkProviderModel→AnthropicModel,GoogleThinkProviderModel→GoogleModel,Cartesia*,Groq*— renamed back. (OpenAi*was unaffected — it's the only think+speak provider, so its names never collided.)AgentV1UpdateListenListen.getProvider()widenedDeepgramListenProviderV2→ aV1|V2union. Additive shim:getProvider()still returnsDeepgramListenProviderV2andprovider(DeepgramListenProviderV2)still builds; the union is exposed viagetProviderValue()andprovider(DeepgramListenProviderV1)for the new model/language capability. Regression-tested byAgentV1UpdateListenShimTest.ConversationHistoryMessage,FunctionCallHistoryMessage) reparented onto history-specific types with the sharedContextMessagesItem*types deleted — restored to 0.7.x shapes, deleted types re-added (return-type changes can't be shimmed additively in Java).Patch reconciliation
ClientOptionsretired from.fernignore— theruntime-versionflag is on docsmain, and the Maven-coordinate fix is deepgram/deepgram-docs#1069, which is still open. This regen was generated from a branch that includes it, so the headers in this PR are correct, but the unfreeze depends on #1069 landing: #1069 must merge before 0.7.2 is cut, or a later regen frommainwould restamp the wrongX-Fern-SDK-Name(com.deepgram:deepgram-sdk) with no freeze left to catch it. Addedmaven-jar-pluginmanifest stamping topom.xmlso the published JAR carriesImplementation-Versionfrom the release-please-managed<version>.ReconnectingWebSocketListener, 11 fields-lesshashCode()types, listen/speak WS query-param +additionalProperties+ forward-compat patches. listen v2 merge preserves the newredact+sendForceEndTurn.Verification
./gradlew unitTest) — pass, including the newAgentV1UpdateListenShimTest(shim API surface, outbound JSON shape, V1/V2 round-trip) alongside the existing patch guards (RegenTypesTesthashCode,QueryStringMapperTest, connect wire tests,ListenV2/SpeakV2ForwardCompatTest,ReconnectingWebSocketListenerTest,RetryInterceptorTest)../gradlew integrationTest, live API) — pass (transcribe URL/file, speak REST, read analyze, manage projects; invalid-key error handling).compileExamples); the safe / changed-area set runs green against the live API.spotlessCheckclean; CI green.Review follow-ups (added after the initial regen)
versionis optional on both provider variants, so{"provider":{"type":"deepgram","model":"nova-3"}}is valid and is what 0.7.x emitted — but Fern'sdefaultImpl = _UnknownValuesent it to an unknown variant whose value was never populated, so the getter returnednulland re-serializing emitted{"provider":null}, silently dropping the provider. NowdefaultImpl = V2Valueon all three agent listen-provider unions.AgentV1UpdateListenListenProvideris new here so that was a regression; the two Settings unions shipped the same defect in 0.7.1 and are fixed too, so all three agree. Guarded byAgentV1UpdateListenShimTestand the newAgentSettingsProviderDefaultTest.ListenV2ForceEndTurnwas missinghashCode()— the only one of twelve fields-less types not carrying the manual patch. Added, frozen, and asserted inRegenTypesTest.DeepgramClient.builder().initialRetryDelayMillis/maxRetryDelayMillis/retryJitterFactorlanded on the parent builder only, so using one mid-chain downgraded the static type andbuild()returned aDeepgramApiClient. Overridden in both hand-maintained wrappers, matching the existingapiKey/timeout/maxRetriespattern.release-please: dropped the now-deadClientOptions.javaentry (the file has nox-release-please-versionmarkers left, so the updater silently no-opped), and added jar-manifest stamping tobuild.gradlesoPackage.getImplementationVersion()resolves on the Gradle path too, not just the published Maven artifact.RequestOptions.maxRetries(...)override. All snippets were compiled against the built SDK — which is how the builder gap above was found.Gate after these changes:
./gradlew clean unitTest spotlessCheck compileExamples— 104 tests, 0 failures. Each new guard was checked by reverting its fix and confirming the test fails.