@google/genai 3.0.0: Node support narrows to >=22.0.0

@google/genai 3.0.0 declares support for Node >=22.0.0 only, a narrower range than 2.32.0. You are affected if a Node version pinned in your repository falls outside that range. The declaration does not by itself mean a build fails. It means that Node version is unsupported by this release.

What changed

• The supported Node range is narrower. 2.32.0 accepted a wider range of Node versions. 3.0.0 declares >=22.0.0 only, and the feed carries this as one breaking change at medium confidence.
• The scan reads version pins, not code. emendant scan reports a Node version pinned outside >=22.0.0 in .nvmrc, .node-version, .tool-versions, volta.node or an actions/setup-node step. No API in the package changed shape for this entry, so there is no import or call site to point at.

Before and after

This release has no patch. The finding appears when a pin sits below the supported range, as in a .nvmrc that names Node 20:

20

The same file naming Node 22 is inside the range and is not reported:

22

The other pin locations are reported the same way when they name a version outside >=22.0.0. None of them is rewritten for you, so the edit to each pin is yours to make.

Migration guidance and its limits

Nothing in this release is patched. The one finding is report only, so emendant fix has no edit to offer for it, and no model provider changes that. Run emendant scan to see which pin files are named, then move each pin to a Node version within >=22.0.0, and update the runtime your deployments use to match.

The finding is medium confidence. A pin below the range means that Node version is unsupported by 3.0.0, not that your build is known to break. Run your own typecheck and tests on the version you move to before you ship.

A clean scan proves only that the pin files and the actions/setup-node steps it reads do not name a version outside the range. It does not read a Node version set anywhere else, such as a container image or a hosting setting, and it does not show that your code runs correctly on the newer Node. Check those places yourself.

What Emendant detects, fixes and verifies

1 change in @google/genai 3.0.0. 0 automatic fixes, 0 fixes requiring a model provider you choose, 1 report only. Each patch states which checks passed. Understand patch evidence.

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

Coverage

Requires emendant@0.11.0 or later. Run emendant feed update to get the latest coverage.

Primary sources

• @google/genai@3.0.0npm registry, the published package
• @google/genai@2.32.0npm registry, the published package

Scan your repository

Find affected code without editing your files.

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.

Related release pages

• Earlier @google/genai release: @google/genai 2.8.0: translation config migration

Every @google/genai release page is listed on one page.