@google/genai 2.8.0: StreamTranslationConfig removed from all three entry points

@google/genai 2.8.0 removes StreamTranslationConfig. The interface, the streamTranslationConfig field on LiveConnectConfig that held it, and the re-export are gone from the package root, @google/genai/node and @google/genai/web alike. Code importing the type by name, from any of the three entry points, stops compiling on upgrade.

What changed

• StreamTranslationConfig no longer exists. 2.7.0 exported it as a named interface with two fields, echoTargetLanguage and targetLanguageCode, describing stream translation for a Live API session. 2.8.0 drops the interface itself, along with the streamTranslationConfig property on LiveConnectConfig that referenced it. Nothing replaces it under a new name.
• The removal is repeated across three subpaths. The same type was re-exported from @google/genai, @google/genai/node and @google/genai/web, and it is gone from all three in 2.8.0. An import written against any one of them breaks the same way.

Before and after

An import of the type from the package root:

import { StreamTranslationConfig } from '@google/genai';

export { StreamTranslationConfig };

@google/genai/node and @google/genai/web break the same import the same way, with only the specifier changed. There is no after. All three carry an assisted fix, so emendant fix asks a model once you name a provider, but the published packages show no replacement type to rewrite the import to and the guidance tells the model to decline rather than invent one.

Migration guidance and its limits

There is most likely nothing to apply. All three findings carry an assisted fix, so naming a model provider on the command line or in emendant.json lets emendant fix try them, and without one they are reported with their guidance and nothing is sent anywhere. Expect all three back unfixed. The release deleted the type and the field that used it and renamed neither, so the guidance asks the model to decline rather than name a replacement that does not exist.

Find every use of StreamTranslationConfig and the streamTranslationConfig field it filled, and decide by hand whether the stream translation behaviour has a replacement in the release you are upgrading to. Read the release notes for @google/genai 2.8.0 before you upgrade a LiveConnectConfig that sets this field; a type error at the import is the easy half, and a config object silently missing a field it used to set is the one your typecheck will not catch on its own if the field access is looser than a literal.

A clean scan proves only that the three import forms this entry names are not in the code. It does not prove the stream translation feature was unused, and it does not cover a StreamTranslationConfig reached through a re-export your own code defines.

What Emendant detects, fixes and verifies

3 changes in @google/genai 2.8.0. 0 patched by a transform, 3 patched only with a model provider you name, 0 report only. Every patch is proved in a copy of your repository before it is offered, and its header names the checks that passed. This table is generated from the feed entry, so it cannot claim more than the entry does.

emendant explain <change-id> prints any row's entry, guidance and sources at the terminal.

Coverage

Snapshot

2026-09-20.1, sequence 27, signed 20 September 2026

Minimum CLI

emendant@0.1.0

Feed entry

feed/npm/@google/genai/2.8.0.json

emendant feed status shows the snapshot your machine holds, and emendant feed update fetches the latest.

Primary sources

Every claim above was checked against these, each pinned to the release rather than to a default branch.

• @google/genai@2.8.0npm registry, the published package
• @google/genai@2.7.0npm registry, the published package

Scan your repository

Runs locally, reads your lockfile and source, sends nothing anywhere.

npx emendant scan

Then npx emendant fix writes the patches the table says exist. The getting started guide covers the flags and the patch grades.