chore(main): release 0.5.0#58
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
70ba5c4 to
ff82958
Compare
lukeocodes
approved these changes
May 18, 2026
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
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.5.0 — what's in this release
This release bundles two Fern SDK regenerations (2026-05-14 and 2026-05-15) plus the manual patches re-applied on top of each.
See the full changelog:
v0.4.0...v0.5.0.⚠ Breaking changes
Environmentconstructor signature changed (3-arg → 4-arg) — #57 + #59agentRestfield,getAgentRestURL()getter, andEnvironment.Builder#agentRest(...)builder method.Environment.AGENTwas dropped in favor of the dedicatedagentRestREST host.agent.v1.settings.think.models.list()now correctly targetsenv.agentRestinstead ofgetAgentURL(). Any caller of that endpoint was already broken before; this is a corrective break.Environmentmust add the newagentRest(...)slot viaEnvironment.custom().Listen-provider type refactor — #57
AgentV1SettingsAgentContextListenProvider{V1, V2, V2LanguageHint}deleted in favor of canonical top-level typesDeepgramListenProviderV1,DeepgramListenProviderV2,DeepgramListenProviderV2LanguageHint.AgentV1SettingsAgentListenProvider{V1, V2}subtypes also deleted (~958 lines removed across the two wrapper hierarchies, deduped against the canonical top-level types). The sealed-type wrappersAgentV1SettingsAgentContextListenProviderandAgentV1SettingsAgentListenProviderremain.Features
Diarization v2 batch GA — #57
ListenV1RequestUrl,MediaTranscribeRequestOctetStream,MediaTranscribeRequestDiarizeModel.AsyncRawMediaClient/RawMediaClientupdated to surface the new diarize-model and octet-stream request paths.Bug fixes
think/models routed to
agentRest— #59RawModelsClientandAsyncRawModelsClient(underagent/v1/settings/think/models/) now resolve their base URL viaenvironment().getAgentRestURL()instead ofgetAgentURL(). (Same root cause as the breaking change above.)Patches preserved through regen
Both regens re-applied the same hand-maintained patches (still listed in
.fernignore):ClientOptions— restored SDK identity headers (User-Agent,X-Fern-SDK-Name,X-Fern-SDK-Version) to thecom.deepgram:deepgram-java-sdkvalues and re-added// x-release-please-versionmarkers. Generator still overwrites these to the wrong artifact id (com.deepgram:deepgram-sdk/com.deepgram.fern:api-sdk) and strips the markers.ReconnectingWebSocketListener— re-applied the three fixes originally landed in fix(reconnect): listener bug fixes + transport factory policy hook #45:maxRetries(0)semantics:retryCount > maxRetries(initial connect attempt always proceeds; the cap applies only to retries).connectionTimeoutMsonReconnectOptions(nested in the same file; default 4000 ms, previously hardcoded).applyOptionsOverride(...)runtime hook used byTransportWebSocketFactoryto apply per-transport reconnect policy fromDeepgramTransportFactorywithout editing generated WS clients.volatilequalifier on option-derived fields.No patches were dropped this cycle — the generator has not caught up on any of the above.
Validation
./gradlew test compileExamples— BUILD SUCCESSFUL on both regen PRs.ReconnectingWebSocketListenerTestcovers the re-applied WS patches.EnvironmentTestandClientBuilderTestupdated to build agent-shaped environments viaEnvironment.custom().agentRest(...).Cross-SDK reference
The
agentRestenv fix has equivalents in deepgram/deepgram-python-sdk#715 and deepgram/deepgram-js-sdk#499. The JS SDK additionally needed aclient.fetch()passthrough patch; Java has no equivalent passthrough inDeepgramClient/DeepgramClientBuilder, so no analogous patch was required here.This PR was generated with Release Please. See documentation.