Skip to content

chore(main): release 0.5.0#58

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--deepgram-java-sdk
Open

chore(main): release 0.5.0#58
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--deepgram-java-sdk

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 15, 2026

🤖 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

Environment constructor signature changed (3-arg → 4-arg) — #57 + #59

Listen-provider type refactor — #57

Features

Diarization v2 batch GA — #57

Bug fixes

think/models routed to agentRest#59

Patches preserved through regen

Both regens re-applied the same hand-maintained patches (still listed in .fernignore):

No patches were dropped this cycle — the generator has not caught up on any of the above.

Validation

Cross-SDK reference

The agentRest env fix has equivalents in deepgram/deepgram-python-sdk#715 and deepgram/deepgram-js-sdk#499. The JS SDK additionally needed a client.fetch() passthrough patch; Java has no equivalent passthrough in DeepgramClient / DeepgramClientBuilder, so no analogous patch was required here.


This PR was generated with Release Please. See documentation.

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--deepgram-java-sdk branch from 70ba5c4 to ff82958 Compare May 18, 2026 09:11
@GregHolmes GregHolmes self-assigned this May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants