chore(main): release 5.7.0#523
Merged
Merged
Conversation
github-actions
Bot
requested review from
GregHolmes,
deepgram-kiley and
dg-coreylweathers
as code owners
July 22, 2026 13:59
GregHolmes
approved these changes
Jul 22, 2026
Contributor
Author
|
🤖 Created releases: 🌻 |
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
5.7.0 (2026-07-22)
Features
Bug Fixes
What's in this release
SDK regeneration for 2026-07-20 (spec
ff8fd2b). No breaking changes.New API surface (Fern-owned, additive)
listen.v2numerals— newnumeralsparam +ListenV2Numeralstype. Connection-time only. Verified end-to-end (serializes onto the connect URL; a TTS'd digits phrase transcribes as5 5 5 1 2 3 4 … 42 … 3rdwithnumerals: truevs spelled-out withfalse).SpeakV1Model/AudioGenerateRequestModel. Additive only.Bug fix — streaming
close()recursion (bf3d1df)Socket.close()synchronously re-fires the registeredclosehandler viahandleClose(); aclosehandler that callsclose()again (idiomatic cleanup) recursed infinitely →RangeError: Maximum call stack size exceeded. All 5 streaming sockets were affected (agent.v1, listen.v1, listen.v2, speak.v1, speak.v2); pre-existing onmain.CustomClient.ts, already frozen) with a sharedWeakSetguard — no generated files frozen. Regression test drives the publiccreateConnectionpath for all 5 services.Bug fix —
stt_latencyback-compat shim (007c7e4)stt_latencyfromAgentV1LatencyReport(docs #1006). Since it's a server-emitted (read-only) message,stt_latency?: numberis re-added by hand as a deprecated read-side field (frozen in.fernignore):report.stt_latencykeeps resolving (toundefined) instead of breaking existing readers at compile time — no request/wire impact. Mirrors the Python SDK's read-side shim (deepgram-python-sdk#746).Validation — all green
make build✅ ·make test✅ (unit 580/580, wire 139/139) ·make typecheck-tests✅ ·biome lint✅ ·biome format✅ · 27/27 non-management examples run clean against the live API.This PR was generated with Release Please. See documentation.