Skip to content

chore(main): release 5.7.0#523

Merged
GregHolmes merged 1 commit into
mainfrom
release-please--branches--main--components--sdk
Jul 22, 2026
Merged

chore(main): release 5.7.0#523
GregHolmes merged 1 commit into
mainfrom
release-please--branches--main--components--sdk

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

5.7.0 (2026-07-22)

Features

  • regen: listen v2 numerals, multilingual Aura-2 voices, and streaming close() fix (#522) (7f0b9e0)

Bug Fixes

  • agent: re-add deprecated stt_latency to AgentV1LatencyReport (back-compat shim) (007c7e4)
  • socket: make streaming close() idempotent to prevent close-handler recursion (bf3d1df)

What's in this release

SDK regeneration for 2026-07-20 (spec ff8fd2b). No breaking changes.

New API surface (Fern-owned, additive)

  • listen.v2 numerals — new numerals param + ListenV2Numerals type. Connection-time only. Verified end-to-end (serializes onto the connect URL; a TTS'd digits phrase transcribes as 5 5 5 1 2 3 4 … 42 … 3rd with numerals: true vs spelled-out with false).
  • New Aura-2 multilingual TTS voices — ~40 voices (es / de / nl / fr / it / ja) on SpeakV1Model / AudioGenerateRequestModel. Additive only.

Bug fix — streaming close() recursion (bf3d1df)

  • The generated Socket.close() synchronously re-fires the registered close handler via handleClose(); a close handler that calls close() 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 on main.
  • Fixed at the wrapper layer (CustomClient.ts, already frozen) with a shared WeakSet guard — no generated files frozen. Regression test drives the public createConnection path for all 5 services.

Bug fix — stt_latency back-compat shim (007c7e4)

  • The spec removed stt_latency from AgentV1LatencyReport (docs #1006). Since it's a server-emitted (read-only) message, stt_latency?: number is re-added by hand as a deprecated read-side field (frozen in .fernignore): report.stt_latency keeps resolving (to undefined) instead of breaking existing readers at compile time — no request/wire impact. Mirrors the Python SDK's read-side shim (deepgram-python-sdk#746).
  • Both shims work around generator output and can be dropped once corrected upstream.

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.

@GregHolmes
GregHolmes merged commit d330c39 into main Jul 22, 2026
5 checks passed
@GregHolmes
GregHolmes deleted the release-please--branches--main--components--sdk branch July 22, 2026 14:18
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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.

1 participant