Packages

@ai-sdk/google

4.0.122 · 17 Nov 2026Apache-2.014.6M / weekRepositoryHomepagenpmAtom feed

Upgrading @ai-sdk/google From 4.0.118 to 4.0.122

4 releases in betweenevery note read

Reading releases, release notes and advisories…

0
changes to make
0
advisories fixed
2
new
6
fixes

Release by release

  1. 4.0.122

    17 Nov 20263 fixes
    • Fixed

      google: Reject structured output schemas in batch requests because inline Google batch requests ignore responseJsonSchema

    • Fixed

      provider/google: Redact MCP server credentials in telemetry

    • Fixed

      google: Include promptFeedback.blockReasonMessage in provider metadata

  2. 4.0.121

    13 Nov 20262 fixes
    • Fixed

      Derive known model ID suggestions from each provider's model catalog declarations so catalog updates automatically update autocomplete, while preserving existing suggestions, endpoint-specific model lists, and support for custom model IDs.

    • Fixed

      Fix Google Interactions ignoring top-level reasoning in generation and streaming calls. Map reasoning to model-supported thinking levels, including Hydrogen's xhigh, preserve explicit thinkingLevel overrides and API defaults, and warn when reasoning is unsupported.

  3. 4.0.120

    13 Nov 20261 new
    • New

      Add experimental extraction models backed by structured language model output

  4. 4.0.119

    12 Nov 20261 new · 1 fix
    • New

      Add the gemini-4-hydrogen model ID and support Hydrogen's xhigh thinking level in Google Generate Content and Interactions provider options. Map portable reasoning: 'xhigh' to xhigh only for Hydrogen models.

    • Fixed

      Forward the provider's configured fetch transport when downloading file inputs. Add a fetch option to createDownload so core downloads can also use guarded-fetch for opt-in DNS validation on Node.js. The function returned by createDownload can now also be passed as experimental_download to generateText and streamText, and experimental_download now also handles generated file URLs returned by the model, so one hook covers all core downloads. Document that the default URL checks do not resolve DNS and recommend the guarded transport or network egress controls for untrusted URLs.

3 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.