Skip to content

chore(main): release 7.19.0 - #829

Merged
GregHolmes merged 1 commit into
mainfrom
gh/release-7.19.0-repair
Nov 13, 2026
Merged

GregHolmes merged 1 commit into
mainfrom
gh/release-7.19.0-repair

Conversation

@GregHolmes

@GregHolmes GregHolmes commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

7.19.0 (2026-11-12)

Features

  • Listen: Add the optional redact_usage control to Listen V1 and V2 clients. Active Flux sessions can update it through ListenV2Configure, and ListenV2ConfigureSuccess reports the active setting. (#828) (0487431)
  • Flux TTS: Add the normalize_volume control for batch and WebSocket synthesis. Expand the typed Flux voice catalog with new multilingual voices, including support for Deepgram Agent TTS providers. (#828) (0487431)

Highlights

  • Control usage redaction for Listen V1 and V2 connections; Flux users can update the setting during an active session and inspect the server-confirmed value.
  • Control Flux speech-volume normalization for batch and streaming synthesis.
  • Select from the expanded typed catalog of multilingual Flux voices, including in Deepgram Agent TTS configuration.

This PR was prepared for the Deepgram Python SDK release workflow.

@github-actions

Copy link
Copy Markdown
Contributor

Code Coverage

Package Line Rate Branch Rate Complexity Health
src.deepgram 97% 94% 0 ✔
src.deepgram.agent 100% 100% 0 ✔
src.deepgram.agent.v1 98% 100% 0 ✔
src.deepgram.agent.v1.settings 100% 100% 0 ✔
src.deepgram.agent.v1.settings.think 100% 100% 0 ✔
src.deepgram.agent.v1.settings.think.models 97% 100% 0 ✔
src.deepgram.auth 100% 100% 0 ✔
src.deepgram.auth.v1 100% 100% 0 ✔
src.deepgram.auth.v1.tokens 97% 100% 0 ✔
src.deepgram.core 89% 84% 0 ➖
src.deepgram.errors 100% 100% 0 ✔
src.deepgram.helpers 98% 92% 0 ✔
src.deepgram.listen 100% 100% 0 ✔
src.deepgram.listen.v1 98% 93% 0 ✔
src.deepgram.listen.v1.media 97% 100% 0 ✔
src.deepgram.listen.v2 98% 93% 0 ✔
src.deepgram.manage 100% 100% 0 ✔
src.deepgram.manage.v1 100% 100% 0 ✔
src.deepgram.manage.v1.models 96% 100% 0 ✔
src.deepgram.manage.v1.projects 97% 100% 0 ✔
src.deepgram.manage.v1.projects.billing 100% 100% 0 ✔
src.deepgram.manage.v1.projects.billing.balances 96% 100% 0 ✔
src.deepgram.manage.v1.projects.billing.breakdown 97% 100% 0 ✔
src.deepgram.manage.v1.projects.billing.fields 97% 100% 0 ✔
src.deepgram.manage.v1.projects.billing.purchases 97% 100% 0 ✔
src.deepgram.manage.v1.projects.keys 96% 100% 0 ✔
src.deepgram.manage.v1.projects.members 97% 100% 0 ✔
src.deepgram.manage.v1.projects.members.invites 96% 100% 0 ✔
src.deepgram.manage.v1.projects.members.scopes 96% 100% 0 ✔
src.deepgram.manage.v1.projects.models 96% 100% 0 ✔
src.deepgram.manage.v1.projects.usage 98% 100% 0 ✔
src.deepgram.manage.v1.projects.usage.breakdown 97% 100% 0 ✔
src.deepgram.manage.v1.projects.usage.fields 97% 100% 0 ✔
src.deepgram.read 100% 100% 0 ✔
src.deepgram.read.v1 100% 100% 0 ✔
src.deepgram.read.v1.text 98% 100% 0 ✔
src.deepgram.self_hosted 100% 100% 0 ✔
src.deepgram.self_hosted.v1 100% 100% 0 ✔
src.deepgram.self_hosted.v1.distribution_credentials 96% 100% 0 ✔
src.deepgram.speak 100% 100% 0 ✔
src.deepgram.speak.v1 98% 97% 0 ✔
src.deepgram.speak.v1.audio 91% 80% 0 ✔
src.deepgram.speak.v2 98% 93% 0 ✔
src.deepgram.speak.v2.audio 100% 100% 0 ✔
src.deepgram.voice_agent 100% 100% 0 ✔
src.deepgram.voice_agent.configurations 95% 100% 0 ✔
src.deepgram.voice_agent.variables 95% 100% 0 ✔
Summary 96% (6619 / 6916) 92% (1457 / 1578) 0 ✔

Scope: hand-maintained SDK logic. Fern-generated data models (types/, requests/), package __init__.py files, version.py, and the unused core/http_sse/ scaffolding are excluded — see .coveragerc. Unscoped whole-package coverage is ~70%.

@dg-coreylweathers dg-coreylweathers left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. This bumps the SDK's version number to 7.19.0 and adds the changelog entry for the usage-redaction and volume-normalization features that already merged — I checked it line by line and it matches exactly what the automated release process would have produced on its own.

One thing worth flagging before this merges, since it changes what happens next: I dug into why the automated release process didn't create this PR itself. The description on the feature PR this is releasing (#828) had a code example with nested parentheses in it, and the tool that reads commit messages to decide what to release choked on that exact line. That's now permanently part of that commit's history, so every time this happens again (on every future push to main), the same tool will hit the same error and quietly do nothing — no new release, no publish — until something gives it a reason to stop looking at that old commit.

Merging this PR fixes the version numbers and changelog, but it won't by itself make the package publish to PyPI, because that step only fires automatically when the release tool creates the release itself, which isn't what's happening here. The actual unblock is to manually tag this merge as v7.19.0 once it lands, so future runs stop tripping over the old broken commit — and then publish to PyPI needs a manual step too, since I don't have access to do that part. Let me know if you've already got that covered, or if you'd like me to do the tagging piece once this is in.

@GregHolmes
GregHolmes merged commit 5a420ce into main Nov 13, 2026
11 checks passed
@GregHolmes
GregHolmes deleted the gh/release-7.19.0-repair branch November 13, 2026 09:41
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