@ai-sdk/provider-utils
5.0.83 · 20 Nov 2026Apache-2.076.4M / weekRepositoryHomepagenpmAtom feed
Upgrading @ai-sdk/provider-utils From 5.0.53 to 5.0.83
29 releases in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 14
- new
- 20
- fixes
Before you upgrade
Tick each one off as you go- Breaking5.0.74
Release by release
- Fixed
Bound bash tool output collection before returning it from supporting sandbox adapters, and copy retained prefixes so truncated results do not keep large source strings alive. Preserve output text, omission counts, command completion, exit codes, and timeout behavior. Custom sandbox implementations remain compatible; just-bash's interpreter buffering remains subject to its native execution limits.
- Fixed
- Fixed
Fix validation of non-Zod Standard Schema results: a result that contains
issuesis now always treated as a failure, even when it also carries avalue. Previously a failing schema such as Valibot's throughtoStandardJsonSchema()could be reported as valid, so rejected input, including tool input, was accepted. - Fixed
Centralize empty extraction value normalization in
experimental_extract, preserving missing-value behavior while removing duplicated conversion from extraction providers.
- Fixed
- New
Add experimental extraction models backed by structured language model output
- New
- Fixed
Move Node.js connection-time DNS validation to the optional
guarded-fetchpackage. It uses an Undici agent to validate every resolved address and pin the connection to those results, independently of global fetch wrappers. It supports explicitly trusted private origins and connection-pool cleanup.
- Fixed
- Fixed
Infer Zod 3 schemas through Standard Schema to prevent recursive type comparisons between installed Zod versions, preserving tool input and streamed output inference.
- Fixed
Use Zod Mini for internal validation schemas to reduce bundle size while preserving the public message schemas' classic Zod methods, error messages, and compatibility with supported Zod 3 and Zod 4 versions.
- Fixed
- Fixed
Require a DNS-pinned fetch for untrusted MCP OAuth discovery and metadata-derived token/registration URLs on server runtimes without a protected default transport. Preserve developer-configured endpoints and allow explicitly supplied fetch implementations that provide equivalent connect-time validation. Browser workers without a DOM follow the same explicit custom-fetch requirement.
- Fixed
- New
Add
resolveProviderOptionsto parse provider options that a model accepts under severalproviderOptionskeys, either as aliases (first) or merged in order (merge), and use it for the existing multi-key lookups in the OpenAI, OpenAI-compatible, Anthropic, Google, and Amazon Bedrock models. Resolution behavior for these models is unchanged. - Fixed
Reject HTTPS-to-HTTP redirects in validated downloads before requesting the insecure target, including when it matches a configured trusted origin.
- Fixed
Return undefined instead of throwing when detectMediaType receives an unsupported topLevelType that matches an inherited object property.
- New
- New
provider-utils: Add an
experimental_binaryFieldsoption tocreateJsonResponseHandler
- New
22 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.