Never miss a release that matters
AI-powered summaries of every GitHub release.
AI Summaries
Changelogs condensed into clear, actionable insights.
Always Free
Track up to 5 packages at no cost, forever.
Weekly Digest
A curated summary of every release, delivered weekly.
TL;DR
A critical security fix prevents API keys from being exposed to unintended origins when following provider-supplied URLs. Several providers were updated to include this fix.
Breaking
- Credential Security: Provider clients now restrict sending API credentials to same-origin URLs only, preventing potential key exposure when following redirects from provider responses. (This impacts providers like Replicate, Fireworks, Gladia, Fal, and Google.)
New
- Azure Deepseek Support: The
@ai-sdk/azurepackage now supports the Deepseek model. - Anthropic Claude-3 Fable: The
@ai-sdk/anthropicpackage now supports theclaude-fable-5model and thefallbacksAPI parameter.
Fixes Worth Knowing
- Fixed an issue where API keys could be unintentionally sent to external origins when following URLs provided in provider responses. This impacts several providers.
- Gateway now correctly maps
forbiddenerrors toGatewayForbiddenError.
Before You Upgrade
Review your provider configurations to ensure all response URLs are appropriately secured and only accessed from your intended origin.
TL;DR
The Vercel AI SDK now supports the claude-fable-5 model via Anthropic and related providers, and introduces a new error type, GatewayFailedDependencyError, for better dependency failure handling.
Breaking
- Provider Credentials Security: The SDK now restricts sending API credentials to same-origin URLs only, preventing potential credential exfiltration via compromised provider responses. This impacts integrations relying on credentials being sent to arbitrary URLs.
- SSRF Protection: Enhanced security measures in
provider-utilsprevent Server-Side Request Forgery (SSRF) attacks when downloading files from untrusted URLs.
New
- Claude Fable 5 Support: Added support for the
claude-fable-5model through the Anthropic provider and related integrations (Azure, Google Vertex, Amazon Bedrock). - Tool Namespaces: OpenAI tool definitions can now be organized using namespaces for better management.
Fixes Worth Knowing
- Gateway Error Handling: Gateway now surfaces provider warnings for embedding and reranking responses.
Forbiddenerrors from providers are now correctly mapped toGatewayForbiddenError. - Google Prototype Pollution: Fixed a potential prototype pollution vulnerability when streaming tool arguments in the Google provider.
- Azure Deepseek Support: Added support for Deepseek models in the Azure provider.
Before You Upgrade
- Review your integrations to ensure API credentials are only being sent to same-origin URLs.
- Verify that file download URLs are trusted and not susceptible to SSRF attacks.
TL;DR
This release significantly improves security across multiple provider integrations by preventing API key leakage when following redirects to untrusted origins.
Breaking
- Prodia: Image URLs are now validated to prevent Server-Side Request Forgery (SSRF) attacks. Ensure any URLs you provide are publicly accessible and do not point to internal resources.
- MCP: Fixed a vulnerability that could have exposed MCP OAuth credentials during rediscovery.
New
- Deepseek: Added support for Deepseek models on Azure.
Fixes Worth Knowing
- Provider Security: A critical fix prevents API keys from being sent to unintended hosts when a provider redirects to a different origin. This impacts
@ai-sdk/replicate,@ai-sdk/fireworks,@ai-sdk/gladia,@ai-sdk/fal,@ai-sdk/google,@ai-sdk/black-forest-labs. - MCP: Prevented prototype-named tools from bypassing schema allowlists, enhancing security.
Before You Upgrade
- Review any custom image URL handling in your Prodia integrations to ensure URLs are publicly accessible.
- No action is required for the security fix, but it's recommended to upgrade promptly.
TL;DR
The Vercel AI SDK now includes critical security fixes to prevent Server-Side Request Forgery (SSRF) vulnerabilities when downloading files via URLs, protecting your application from malicious access to internal resources.
Fixes Worth Knowing
- Fixed a potential security issue where untrusted URLs could be exploited during file downloads. The SDK now validates URLs more thoroughly, including handling redirects and blocking internal/private addresses.
- Enhanced security against prototype pollution attacks when processing stream data, preventing potential manipulation of stream IDs.
- Improved error handling to prevent sensitive server error details from being exposed to users by default. Error messages now display a generic message unless a custom error handler is provided.
Before You Upgrade
Review your application's error handling to ensure you are intentionally surfacing detailed error messages if needed, as the default behavior has changed to a generic message.
TL;DR
The Vercel AI SDK now includes critical security fixes to prevent API key exposure and address potential Server-Side Request Forgery (SSRF) vulnerabilities when downloading files.
Breaking
- Credential Security: The SDK now restricts sending provider credentials to same-origin URLs only, preventing potential API key leakage to malicious hosts.
- Download URL Validation: Enhanced validation prevents bypassing security checks when downloading files via untrusted URLs, mitigating SSRF risks.
New
- Anthropic Claude Fable 5 Support: Added support for the
claude-fable-5model and thefallbacksAPI parameter across multiple providers. - Bedrock Embedding Token Usage: Amazon Bedrock now correctly extracts Cohere embedding token usage from response headers.
Fixes Worth Knowing
- Improved security when handling URLs from provider responses to prevent accidental credential sharing.
- Strengthened file download URL validation to prevent potential SSRF attacks.
TL;DR
The Vercel AI SDK now includes critical security fixes addressing potential Server-Side Request Forgery (SSRF) vulnerabilities in file downloads and replay attacks via forged tool calls. These updates protect against malicious actors exploiting your AI applications.
Breaking
- Stream Errors:
streamTextnow rejects with aNoOutputGeneratedErrorif the model stream completes without producing any output, instead of resolving with an empty result. (Error handling) - Tool Approval Revalidation: Tool calls from client message history are now re-validated for approval and input schema, preventing potential exploitation through forged requests. (Security)
New
- Array Output Validation: Array outputs now consistently apply schema transformations (coercion, defaults, pipes) like object outputs. (Data handling)
- Redacted Error Messages: Server error details are no longer streamed to the client by default, improving security and user experience. (Security/UX)
Fixes Worth Knowing
- Fixed a vulnerability allowing bypass of download URL security checks. (Security)
- Improved protection against prototype pollution vulnerabilities in stream processing. (Security)
- Denied tool outputs are now properly guarded against execution. (Security)
Before You Upgrade
- Update your error handling for
streamTextto catch the newNoOutputGeneratedError. - If you rely on streaming raw error details, explicitly provide an
onErrorhandler tostreamTextorcreateUIMessageStream.
TL;DR
The Vercel AI SDK now renames key event callbacks from onStepFinish and onObjectStepFinish to onStepEnd and onObjectStepEnd respectively, impacting observability and tooling integrations. A new agent TUI (text-based user interface) has also been introduced.
Breaking
- Event Callback Renames:
onStepFinishis nowonStepEnd, andonObjectStepFinishis nowonObjectStepEnd. (Update your code to use the new event names for accurate tracking.) - OutputInterface Removal: The
OutputInterfaceexport has been removed from the@ai-sdk/otelpackage. (Adjust any code directly importing this interface.)
New
- Agent TUI: A new text-based user interface is available for interacting with agents. (This provides a command-line interface for agent interaction.)
Fixes Worth Knowing
- Workflow Security: Improved security in the workflow agent by re-validating tool approvals before execution, preventing potential malicious tool calls.
- Harness Bug Fixes: Resolved issues with harness skills processing and session resumption.
- Devtools Security: Enhanced security for the devtools viewer API access.
- Sandbox/Harness Dependencies: Fixed an issue where sandbox and harness SDKs were incorrectly using peer dependencies.
TL;DR
The Vercel AI SDK now supports Deepseek models on Azure and introduces namespaces for tool definitions in OpenAI, improving organization and flexibility. Security has also been enhanced by preventing API key exposure when following provider-supplied URLs.
Breaking
- React MCP App Tool Calls: Tool invocation from MCP App content is now deny-by-default. You must explicitly allow tools via
handlers.allowedToolsto expose them to the app.
New
- Deepseek on Azure: Added support for Deepseek models within the Azure provider.
- OpenAI Tool Namespaces: Introduced namespaces for tool definitions, enabling better organization and preventing naming conflicts.
Fixes Worth Knowing
- Google API Key Security: Prevents accidental exposure of API keys when following URLs provided by the Google provider.
- Gateway Error Handling: Added a
GatewayFailedDependencyError(status code 424) for better error reporting. - Gateway Forbidden Errors: Gateway now correctly maps
forbiddenerrors toGatewayForbiddenError. - Gateway File Encoding: Correctly base64-encodes binary data in reasoning and tool result files.
- Google Streaming Args: Prevents prototype pollution when streaming arguments to Google models.
- Gateway Warnings: Provider warnings are now surfaced in embedding and reranking responses.
Before You Upgrade
- If you are using MCP Apps in React, explicitly define
allowedToolsto ensure expected tool access. - Review your Google provider configurations to ensure proper URL handling after this security update.
TL;DR
The Vercel AI SDK now includes support for Google Cloud Speech-to-Text transcription models via the @ai-sdk/google-vertex package and the claude-fable-5 model with fallbacks API parameter via @ai-sdk/anthropic. Crucially, several high-severity security vulnerabilities related to credential exposure and tool approval have been addressed.
Breaking
- Credential Security: The SDK now restricts sending API keys to same-origin URLs only, preventing potential exposure via provider response URLs. (Prevents accidental key leakage to untrusted hosts)
- Tool Approval: Tool call approvals are now re-validated before execution, mitigating a potential vulnerability where malicious tool calls could be forged. (Enhances security of tool integrations)
- Download Security: Download URL validation has been significantly hardened to prevent Server-Side Request Forgery (SSRF) attacks. (Protects against malicious file downloads)
New
- Google Speech-to-Text: Added support for transcribing audio using Google Cloud's Speech-to-Text models. (Enables audio processing capabilities)
- Anthropic Claude-fable-5: Added support for the
claude-fable-5model and thefallbacksAPI parameter. (Provides access to a new model and feature)
Fixes Worth Knowing
- Socket Leaks: Fixed a potential socket leak during download failures, preventing denial-of-service attacks. (Improves stability and resource management)
- Redirect Handling: Improved redirect handling during downloads to prevent SSRF vulnerabilities and ensure legitimate redirects work. (Enhances download security and reliability)
Before You Upgrade
- Review your provider configurations to ensure your API origins are correctly set, as credential sending is now restricted to same-origin URLs.
- If you are using custom tools, verify that your tool schemas are up-to-date and that your approval policies are correctly configured, as tool calls are now re-validated.
TL;DR
A critical security fix prevents accidental exposure of API keys when following redirects from AI providers. Additionally, Langchain citations are now correctly surfaced as source information in the UI.
Breaking
- Credential Exposure: API keys could be unintentionally exposed via redirects to untrusted origins. The SDK now restricts credential inclusion to same-origin redirects, preventing potential security breaches.
New
- Langchain Citations: Langchain citation metadata is now correctly exposed as
source-urlandsource-documentUI message parts, improving traceability of AI-generated content. - Deepseek Azure Support: Added support for Deepseek models on the Azure platform.
Fixes Worth Knowing
- Fixed an issue where API keys were being sent in redirects to potentially malicious domains. This impacts all providers using response-supplied URLs.
TL;DR
The Vercel AI SDK now includes critical security fixes addressing potential SSRF (Server-Side Request Forgery) vulnerabilities in file downloads and preventing replay attacks via forged tool calls. These changes enhance the security and reliability of AI-powered applications.
Breaking
- Deprecated Functionality Removed: The
generateImageexports marked as experimental have been removed. - Event Renames:
onObjectStepFinishandonStepFinishevents have been renamed toonObjectStepEndandonStepEndrespectively.
New
- Array Output Validation:
generateTextnow returns validated elements when configured for array output. - Improved Tool Approval Security: Enhanced validation of tool approvals to prevent malicious exploitation.
Fixes Worth Knowing
- SSRF Protection: Strengthened download URL validation to prevent bypassing security checks and accessing internal resources.
- Error Redaction: Server error details are no longer included in UI message streams by default, improving user privacy.
- Socket Leak Prevention: Fixed a potential socket leak during download rejections, improving stability under heavy load.
- Step Timeout: Corrected step timeout behavior in
streamTextto reliably enforce thetimeout.stepMssetting. - Tool Output Guard: Added an approval guard for denied tool outputs.
Before You Upgrade
- Update any code referencing the removed
generateImageexports. - Adjust your event listeners to use the new event names (
onObjectStepEnd,onStepEnd).
TL;DR
Critical security fixes have been released across multiple providers, preventing potential credential leakage and Server-Side Request Forgery (SSRF) attacks.
Breaking
- The MCP tool allowlist now uses
Object.hasOwninstead ofinto prevent prototype-named tools from bypassing schema restrictions. This may affect code relying on inheriting properties for tool definitions.
Fixes Worth Knowing
- Security: Prevented API key leakage to untrusted hosts when following provider-supplied URLs. This impacts Black Forest Labs, Fireworks, Replicate, Gladia, FAL, and Google providers.
- Security: Mitigated a potential SSRF vulnerability in the Prodia video model by validating user-supplied image URLs before fetching.
- Fixed an issue in MCP where the first SSE endpoint was not being locked.
Before You Upgrade
- Review your MCP tool definitions to ensure they are explicitly defined in your schemas and do not rely on inherited properties.
TL;DR
The Vercel AI SDK now prevents API key leakage to unintended origins when following redirects from providers, significantly improving security.
Breaking
- Tool schemas in
@ai-sdk/mcpnow strictly enforce allowed tools, preventing unintended exposure of prototype properties (likeconstructor) that could be exploited.
Fixes Worth Knowing
- Fixed an issue in
@ai-sdk/mcpwhere the first SSE (Server-Sent Events - real-time data stream) endpoint received could be dropped. - The Devtools viewer API in
@ai-sdk/devtoolsis now more secure. - API keys are no longer sent with requests to different origins when following provider-supplied URLs, addressing a critical security vulnerability across multiple providers including Black Forest Labs, Fireworks, Replicate, Gladia, FAL, and Google.
TL;DR
The Vercel AI SDK now supports sandboxed environments for running AI code, offering sandbox-just-bash and sandbox-vercel options for enhanced security and control (isolated execution environments).
New
- Introduced sandboxed environments via the
sandbox-just-bashandsandbox-vercelharnesses, allowing for safer AI code execution. - Added a new harness abstraction to support various sandbox types (execution contexts).
TL;DR
The Vercel AI SDK now supports programmatic tool calling with Anthropic models, image editing, and Standard JSON Schema (data validation) for more flexible AI interactions.
New
- Programmatic Tool Calling (Anthropic): Enables developers to define and invoke tools within Anthropic models.
- Image Editing: Allows manipulation of images using the AI SDK.
- Standard JSON Schema Support: Adds validation for AI responses using JSON Schema (data format).
Fixes Worth Knowing
- Fixed a header loss issue when
statusTextwas undefined during response writing. - Resolved an issue where messages were incorrectly named in the agent UI stream functions.
Before You Upgrade
- If you are using the SDK's base URL, update your code to use
https://ai-sdk.devinstead ofhttps://v6.ai-sdk.dev. - Review changes to
toModelOutputarguments, which now accept a parameter object.