Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: deepgram/deepgram-python-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: deepgram/deepgram-python-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v5
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 2 commits
  • 12 files changed
  • 1 contributor

Commits on Feb 24, 2026

  1. fix(websockets): tolerate unknown message types from API (#671) 

    ## Summary
- Backport of the v6.0.1 `construct_type` fix to the v5 maintenance
branch
- Adds `unchecked_base_model.py` (from v6) with `construct_type` which
does best-effort union coercion instead of strict Pydantic validation
- Switches all 4 socket clients (listen v1, listen v2, speak v1, agent
v1) from `parse_obj_as` to `construct_type`
- Unknown WebSocket message types (e.g. `ConfigureSuccess`) now pass
through without crashing the listener

## Test plan
- [x] 853 unit/integration tests pass
- [x] Verified against live Deepgram API with Listen V2 (Flux) —
`ConfigureSuccess` unknown message type coerced cleanly as
`ListenV2ConnectedEvent`
- [x] Verify no regressions in existing v5 consumers
    @lukeocodes
    lukeocodes authored Feb 24, 2026
    Configuration menu
    Copy the full SHA
    7deb302 View commit details
    Browse the repository at this point in the history

  2. chore(release): release 5.3.3

    @lukeocodes
    lukeocodes committed Feb 24, 2026
    Configuration menu
    Copy the full SHA
    0378dfd View commit details
    Browse the repository at this point in the history
Loading