deepgram-upgrade-migration
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
Deepgram Upgrade Migration
Prerequisites
- Current/target SDK or API versions, compatibility matrix, approved fixtures, quality/latency thresholds, and rollback owner.
- Separate staging credentials plus a data-retention and consent review for any migration/reprocessing action.
Examples
Upgrade the SDK in staging, run mock/unit tests and a small licensed-fixture comparison against the prior version, and compare aggregate output/latency/error metrics. Promote through an approved canary only after acceptance passes; revert to the prior lockfile/configuration on regression and do not reprocess production recordings to validate the upgrade.
Current State
!npm list @deepgram/sdk 2>/dev/null | grep deepgram || echo 'SDK not installed'
Overview
Guide for Deepgram SDK version upgrades (v3 -> v4 -> v5) and model migrations (Nova-2 -> Nova-3). Includes breaking change maps, side-by-side API comparison, A/B testing scripts, automated validation, and rollback procedures.