Skip to content

build(deps-dev): bump the ai-sdk group across 1 directory with 5 updates - #6

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/ai-sdk-ad2cd118c5
Open

build(deps-dev): bump the ai-sdk group across 1 directory with 5 updates#6
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/ai-sdk-ad2cd118c5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 9, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the ai-sdk group with 5 updates in the / directory:

Package From To
@ai-sdk/anthropic 4.0.68 4.0.92
@ai-sdk/google 4.0.85 4.0.108
@ai-sdk/openai 4.0.81 4.0.105
@ai-sdk/openai-compatible 3.0.59 3.0.81
ai 7.0.122 7.0.157

Updates @ai-sdk/anthropic from 4.0.68 to 4.0.92

Release notes

Sourced from @​ai-sdk/anthropic's releases.

@​ai-sdk/mistral@​4.0.77

Patch Changes

  • 19cb252: Centralize Mistral model capabilities and provider option support in a model catalog shared by request preparation and generated documentation, preserving Chat and Conversations reasoning policies and legacy transcription restrictions.

@​ai-sdk/mistral@​4.0.76

Patch Changes

  • 7716e18: Support promises and synchronous or asynchronous callbacks in provider API key and token settings. Resolve credentials per authenticated request while preserving existing authentication behavior and synchronous credential serialization.

    The experimental OpenAI Live getServerWebSocketConfig() method can now resolve asynchronously. Await its result before using the connection settings.

  • Updated dependencies [7716e18]

  • Updated dependencies [5c247e9]

  • Updated dependencies [dcd2f8d]

    • @​ai-sdk/provider-utils@​5.0.72
    • @​ai-sdk/provider@​4.0.35

@​ai-sdk/klingai@​4.0.74

Patch Changes

  • 7716e18: Support promises and synchronous or asynchronous callbacks in provider API key and token settings. Resolve credentials per authenticated request while preserving existing authentication behavior and synchronous credential serialization.

    The experimental OpenAI Live getServerWebSocketConfig() method can now resolve asynchronously. Await its result before using the connection settings.

  • Updated dependencies [7716e18]

  • Updated dependencies [5c247e9]

  • Updated dependencies [dcd2f8d]

    • @​ai-sdk/provider-utils@​5.0.72
    • @​ai-sdk/provider@​4.0.35
Changelog

Sourced from @​ai-sdk/anthropic's changelog.

4.0.92

Patch Changes

  • 61a315e: fix: map the top-level reasoning option consistently across providers

    Providers now resolve reasoning the same way:

    1. A provider-specific reasoning setting in providerOptions is sent unchanged. OpenAI no longer drops providerOptions.openai.reasoningEffort values that are not in its list for the model, and Fireworks no longer rewrites providerOptions.fireworks.reasoningEffort. Fireworks also sends top-level reasoning values directly instead of rounding them to 'high' at most, except for model families known to reject 'none' (GPT-OSS, GLM-5.3, Muse Spark) or 'minimal' (Nemotron, Inkling).
    2. Otherwise, reasoning maps to the closest level the model supports, rounding down, and rounds up only when there is no lower level. For example, 'xhigh' now maps to 'high' instead of 'max' on Anthropic and Bedrock models without xhigh effort, and 'medium' maps to 'low' instead of 'high' on DeepSeek, Kimi K3, and Mistral GLM-5.3 models.
    3. 'none' on a model that cannot disable reasoning maps to the model's lowest level with a compatibility warning, instead of being dropped or sending a request the API rejects. This affects GPT-6 models without 'none', xAI grok-4.5 and later, Groq GPT-OSS, Kimi K3, Perplexity, QuiverAI, Bedrock OpenAI gpt-oss models, and Gemini 2.5 Pro (minimum thinking budget). Gemini 3 and Anthropic and Bedrock between_tools mappings now emit the compatibility warning too.

    mapReasoningToProviderEffort now accepts any reasoning value, returns an optional providerOptionsEffort unchanged, and rounds levels that are missing from the effort map to the closest supported level. mapReasoningToProviderBudget maps 'none' to the minimum reasoning budget, always returns a budget, and uses the default percentage for levels missing from budgetPercentages. OpenAICompatibleChatConfig adds an optional mapReasoning function for mapping the top-level reasoning option.

  • Updated dependencies [61a315e]

    • @​ai-sdk/provider-utils@​5.0.71

4.0.91

Patch Changes

  • 50da4c5: Fix workflow serialization of Anthropic models using API keys or synchronous auth tokens while preserving support for asynchronous token providers.

4.0.90

Patch Changes

  • 63bf860: Support synchronous and asynchronous authToken providers so applications can use refreshable credentials, including Anthropic workload identity federation helpers for inference. Resolve tokens before each request while preserving existing authentication headers and beta-header behavior.
  • Updated dependencies [57086ff]
  • Updated dependencies [95348b3]
    • @​ai-sdk/provider-utils@​5.0.70

4.0.89

Patch Changes

  • Updated dependencies [e64ed82]
    • @​ai-sdk/provider-utils@​5.0.69

4.0.88

Patch Changes

  • e729d58: chore(docs): update README.md for consistent format and to avoid duplication
  • Updated dependencies [5475347]
  • Updated dependencies [e729d58]
    • @​ai-sdk/provider@​4.0.34
    • @​ai-sdk/provider-utils@​5.0.68

4.0.87

... (truncated)

Commits

Updates @ai-sdk/google from 4.0.85 to 4.0.108

Release notes

Sourced from @​ai-sdk/google's releases.

@​ai-sdk/openai@​4.0.106

Patch Changes

  • 7716e18: Support promises and synchronous or asynchronous callbacks in provider API key and token settings. Resolve credentials per authenticated request while preserving existing authentication behavior and synchronous credential serialization.

    The experimental OpenAI Live getServerWebSocketConfig() method can now resolve asynchronously. Await its result before using the connection settings.

  • dcd2f8d: Introduce a model entry contract with named capability sections and request configuration. Consolidate the OpenAI and Anthropic model catalogs so existing request behavior and generated capability documentation use the same source of truth. Catalogs also declare the provider options each provider accepts and which models support them.

  • Updated dependencies [7716e18]

  • Updated dependencies [5c247e9]

  • Updated dependencies [dcd2f8d]

    • @​ai-sdk/provider-utils@​5.0.72
    • @​ai-sdk/provider@​4.0.35
Changelog

Sourced from @​ai-sdk/google's changelog.

4.0.108

Patch Changes

  • 9f108f8: close string values in tool-call input streamed with streamFunctionCallArguments on their final chunk

  • b1bcea1: Add videoMetadata support for file parts. Pass startOffset, endOffset, and fps through per-file providerOptions to control video clipping and frame rate with the Google and Google Vertex providers.

  • 61a315e: fix: map the top-level reasoning option consistently across providers

    Providers now resolve reasoning the same way:

    1. A provider-specific reasoning setting in providerOptions is sent unchanged. OpenAI no longer drops providerOptions.openai.reasoningEffort values that are not in its list for the model, and Fireworks no longer rewrites providerOptions.fireworks.reasoningEffort. Fireworks also sends top-level reasoning values directly instead of rounding them to 'high' at most, except for model families known to reject 'none' (GPT-OSS, GLM-5.3, Muse Spark) or 'minimal' (Nemotron, Inkling).
    2. Otherwise, reasoning maps to the closest level the model supports, rounding down, and rounds up only when there is no lower level. For example, 'xhigh' now maps to 'high' instead of 'max' on Anthropic and Bedrock models without xhigh effort, and 'medium' maps to 'low' instead of 'high' on DeepSeek, Kimi K3, and Mistral GLM-5.3 models.
    3. 'none' on a model that cannot disable reasoning maps to the model's lowest level with a compatibility warning, instead of being dropped or sending a request the API rejects. This affects GPT-6 models without 'none', xAI grok-4.5 and later, Groq GPT-OSS, Kimi K3, Perplexity, QuiverAI, Bedrock OpenAI gpt-oss models, and Gemini 2.5 Pro (minimum thinking budget). Gemini 3 and Anthropic and Bedrock between_tools mappings now emit the compatibility warning too.

    mapReasoningToProviderEffort now accepts any reasoning value, returns an optional providerOptionsEffort unchanged, and rounds levels that are missing from the effort map to the closest supported level. mapReasoningToProviderBudget maps 'none' to the minimum reasoning budget, always returns a budget, and uses the default percentage for levels missing from budgetPercentages. OpenAICompatibleChatConfig adds an optional mapReasoning function for mapping the top-level reasoning option.

  • Updated dependencies [61a315e]

    • @​ai-sdk/provider-utils@​5.0.71

4.0.107

Patch Changes

  • Updated dependencies [57086ff]
  • Updated dependencies [95348b3]
    • @​ai-sdk/provider-utils@​5.0.70

4.0.106

Patch Changes

  • Updated dependencies [e64ed82]
    • @​ai-sdk/provider-utils@​5.0.69

4.0.105

Patch Changes

  • e729d58: chore(docs): update README.md for consistent format and to avoid duplication

  • bbe2bd1: fix(google): keep empty arrays and objects in tool-call input streamed with streamFunctionCallArguments

    Vertex sends a value-less partialArgs entry for an empty container (e.g. $.tags[]), which was dropped, so [] and {} arguments went missing from the streamed tool-call input.

  • Updated dependencies [5475347]

  • Updated dependencies [e729d58]

    • @​ai-sdk/provider@​4.0.34
    • @​ai-sdk/provider-utils@​5.0.68

4.0.104

... (truncated)

Commits

Updates @ai-sdk/openai from 4.0.81 to 4.0.105

Changelog

Sourced from @​ai-sdk/openai's changelog.

4.0.105

Patch Changes

  • 47b1d8b: feat(openai): send native JSON input and prompt cache keys to Decisions

  • d07b475: fix(openai): map top-level reasoning to efforts supported by GPT-5.x models instead of sending unsupported values that OpenAI rejects with a 400. max is now only sent on the Responses API, and GPT-5.6 on Chat Completions sends reasoning_effort: 'none' when function tools are used, since it rejects function tools with reasoning. A warning is emitted when a reasoning level was requested.

  • 61a315e: fix: map the top-level reasoning option consistently across providers

    Providers now resolve reasoning the same way:

    1. A provider-specific reasoning setting in providerOptions is sent unchanged. OpenAI no longer drops providerOptions.openai.reasoningEffort values that are not in its list for the model, and Fireworks no longer rewrites providerOptions.fireworks.reasoningEffort. Fireworks also sends top-level reasoning values directly instead of rounding them to 'high' at most, except for model families known to reject 'none' (GPT-OSS, GLM-5.3, Muse Spark) or 'minimal' (Nemotron, Inkling).
    2. Otherwise, reasoning maps to the closest level the model supports, rounding down, and rounds up only when there is no lower level. For example, 'xhigh' now maps to 'high' instead of 'max' on Anthropic and Bedrock models without xhigh effort, and 'medium' maps to 'low' instead of 'high' on DeepSeek, Kimi K3, and Mistral GLM-5.3 models.
    3. 'none' on a model that cannot disable reasoning maps to the model's lowest level with a compatibility warning, instead of being dropped or sending a request the API rejects. This affects GPT-6 models without 'none', xAI grok-4.5 and later, Groq GPT-OSS, Kimi K3, Perplexity, QuiverAI, Bedrock OpenAI gpt-oss models, and Gemini 2.5 Pro (minimum thinking budget). Gemini 3 and Anthropic and Bedrock between_tools mappings now emit the compatibility warning too.

    mapReasoningToProviderEffort now accepts any reasoning value, returns an optional providerOptionsEffort unchanged, and rounds levels that are missing from the effort map to the closest supported level. mapReasoningToProviderBudget maps 'none' to the minimum reasoning budget, always returns a budget, and uses the default percentage for levels missing from budgetPercentages. OpenAICompatibleChatConfig adds an optional mapReasoning function for mapping the top-level reasoning option.

  • Updated dependencies [61a315e]

    • @​ai-sdk/provider-utils@​5.0.71

4.0.104

Patch Changes

  • 01d7a03: feat(openai): add GPT-6.1 Terra model support

  • 599a97f: fix(openai): read transcription duration from usage for duration-billed json responses

    durationInSeconds now falls back to usage.seconds when usage.type is duration and the response has no top-level duration (e.g. gpt-transcribe with the default json response format).

  • 8375141: Support streaming transcription with gpt-live-transcribe and gpt-transcribe. For these models the language provider option is sent as a single-entry languages list. gpt-transcribe warns about and omits streaming.delay, which it does not support. gpt-live-transcribe rejects non-streaming transcription, since it has no REST endpoint.

  • 7eac057: fix(openai): strip propertyNames schemas that omit type: 'string' (e.g. Zod 3 records with constrained keys) instead of throwing an unsupported functionality error

  • 436374e: fix(openai): report unfinished web searches as tool errors

  • 9026c7d: fix(openai): only send transcription response format and timestamp defaults when needed

    Transcription requests no longer send response_format=verbose_json or timestamp_granularities[]=segment unless the caller sets them or the model needs them. Previously, any providerOptions.openai value (such as a prompt) caused verbose_json to be sent for models like gpt-transcribe, which rejected the request.

  • Updated dependencies [57086ff]

  • Updated dependencies [95348b3]

    • @​ai-sdk/provider-utils@​5.0.70

4.0.103

Patch Changes

  • 02dbab1: add azure.tools.toolSearch and support azure provider options on responses function tools
  • 27a53b4: Fix string interpolation in Amazon Bedrock unsupported provider tool warnings and OpenAI / OpenAI-compatible completion errors for unexpected system messages.
  • Updated dependencies [e64ed82]
    • @​ai-sdk/provider-utils@​5.0.69

4.0.102

... (truncated)

Commits
  • d1067fd Version Packages (#24173)
  • d07b475 fix(openai): map reasoning to efforts supported by GPT-5.x models (#24190)
  • 61a315e fix: map reasoning consistently across providers (#24123)
  • 47b1d8b feat(openai): send native JSON input and prompt cache keys to Decisions (#24132)
  • 1f3cdbb Version Packages (#24084)
  • 436374e fix(openai): report unfinished web searches as tool errors (#24121)
  • 599a97f fix(openai): gpt-transcribe REST response format and duration (#24110)
  • 8375141 feat(openai): support streaming transcription with gpt-live-transcribe and gp...
  • 7eac057 fix(openai): strip propertyNames schemas that omit type (#24115)
  • 9026c7d fix(openai): only default transcription response format and timestamps when n...
  • Additional commits viewable in compare view

Updates @ai-sdk/openai-compatible from 3.0.59 to 3.0.81

Changelog

Sourced from @​ai-sdk/openai-compatible's changelog.

3.0.81

Patch Changes

  • 61a315e: fix: map the top-level reasoning option consistently across providers

    Providers now resolve reasoning the same way:

    1. A provider-specific reasoning setting in providerOptions is sent unchanged. OpenAI no longer drops providerOptions.openai.reasoningEffort values that are not in its list for the model, and Fireworks no longer rewrites providerOptions.fireworks.reasoningEffort. Fireworks also sends top-level reasoning values directly instead of rounding them to 'high' at most, except for model families known to reject 'none' (GPT-OSS, GLM-5.3, Muse Spark) or 'minimal' (Nemotron, Inkling).
    2. Otherwise, reasoning maps to the closest level the model supports, rounding down, and rounds up only when there is no lower level. For example, 'xhigh' now maps to 'high' instead of 'max' on Anthropic and Bedrock models without xhigh effort, and 'medium' maps to 'low' instead of 'high' on DeepSeek, Kimi K3, and Mistral GLM-5.3 models.
    3. 'none' on a model that cannot disable reasoning maps to the model's lowest level with a compatibility warning, instead of being dropped or sending a request the API rejects. This affects GPT-6 models without 'none', xAI grok-4.5 and later, Groq GPT-OSS, Kimi K3, Perplexity, QuiverAI, Bedrock OpenAI gpt-oss models, and Gemini 2.5 Pro (minimum thinking budget). Gemini 3 and Anthropic and Bedrock between_tools mappings now emit the compatibility warning too.

    mapReasoningToProviderEffort now accepts any reasoning value, returns an optional providerOptionsEffort unchanged, and rounds levels that are missing from the effort map to the closest supported level. mapReasoningToProviderBudget maps 'none' to the minimum reasoning budget, always returns a budget, and uses the default percentage for levels missing from budgetPercentages. OpenAICompatibleChatConfig adds an optional mapReasoning function for mapping the top-level reasoning option.

  • Updated dependencies [61a315e]

    • @​ai-sdk/provider-utils@​5.0.71

3.0.80

Patch Changes

  • Updated dependencies [57086ff]
  • Updated dependencies [95348b3]
    • @​ai-sdk/provider-utils@​5.0.70

3.0.79

Patch Changes

  • 27a53b4: Fix string interpolation in Amazon Bedrock unsupported provider tool warnings and OpenAI / OpenAI-compatible completion errors for unexpected system messages.
  • Updated dependencies [e64ed82]
    • @​ai-sdk/provider-utils@​5.0.69

3.0.78

Patch Changes

  • e729d58: chore(docs): update README.md for consistent format and to avoid duplication
  • Updated dependencies [5475347]
  • Updated dependencies [e729d58]
    • @​ai-sdk/provider@​4.0.34
    • @​ai-sdk/provider-utils@​5.0.68

3.0.77

Patch Changes

  • Updated dependencies [8202f5b]
  • Updated dependencies [85d84a1]
    • @​ai-sdk/provider-utils@​5.0.67

... (truncated)

Commits

Updates ai from 7.0.122 to 7.0.157

Changelog

Sourced from ai's changelog.

7.0.157

Patch Changes

  • 0cc4921: graduate LanguageModelStreamPart to stable and deprecate Experimental_LanguageModelStreamPart
  • 077cfb3: feat(ai): Graduate filterActiveTools from experimental. It is now exported as filterActiveTools; experimental_filterActiveTools remains as a deprecated alias.
  • eb768e2: Fix Next.js Edge Runtime warnings from Node.js runtime detection used by telemetry tracing.
  • Updated dependencies [9ca8bcf]
  • Updated dependencies [61a315e]
    • @​ai-sdk/gateway@​4.0.130
    • @​ai-sdk/provider-utils@​5.0.71

7.0.156

Patch Changes

  • Updated dependencies [9f19c79]
    • @​ai-sdk/gateway@​4.0.129

7.0.155

Patch Changes

  • b6b9dca: chore(ai): remove runtime validation of inputs that TypeScript types already guarantee

    streamText, generateText, generateObject and streamObject no longer validate messages against the ModelMessage schema. This removes a cost that grew linearly with message history and was paid on every streamText step. Type checks on call settings, steering messages, tool caller configuration, smoothStream chunking, experimental_streamSpeech text input, the shape of decide state and questions, and the batch reference version have also been removed. Value constraints that types cannot express, such as integer ranges, non-empty collections, unknown keys, and non-finite numbers or cycles in decide JSON input, are still validated.

  • Updated dependencies [57086ff]

  • Updated dependencies [01d7a03]

  • Updated dependencies [95348b3]

    • @​ai-sdk/provider-utils@​5.0.70
    • @​ai-sdk/gateway@​4.0.128

7.0.154

Patch Changes

  • 47236dd: add onStepError callback to generateText, streamText, ToolLoopAgent and telemetry integrations, and onError and onAbort to ToolLoopAgent
  • c8e8866: Add aiVersion to telemetry events so tracing-channel subscribers and telemetry integrations can identify the emitting ai package version, including in bundled applications and applications with multiple SDK versions.
  • 1cf95c6: add experimental steering to generateText, streamText and ToolLoopAgent
  • Updated dependencies [e64ed82]
    • @​ai-sdk/provider-utils@​5.0.69
    • @​ai-sdk/gateway@​4.0.127

7.0.153

Patch Changes

  • 5475347: Fix non-streaming Responses API structured output failing when multiple assistant messages contain JSON. Providers can supply separate structured-output text for parsing, allowing OpenAI and Azure Responses models to select the last final_answer while preserving all generated content, annotations, conversation history, and token usage.
  • Updated dependencies [5475347]

... (truncated)

Commits

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 9, 2026
@dependabot
build(deps-dev): bump the ai-sdk group across 1 directory with 5 updates
7985a7f 
Bumps the ai-sdk group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@ai-sdk/anthropic](https://github.com/vercel/ai/tree/HEAD/packages/anthropic) | `4.0.68` | `4.0.92` |
| [@ai-sdk/google](https://github.com/vercel/ai/tree/HEAD/packages/google) | `4.0.85` | `4.0.108` |
| [@ai-sdk/openai](https://github.com/vercel/ai/tree/HEAD/packages/openai) | `4.0.81` | `4.0.105` |
| [@ai-sdk/openai-compatible](https://github.com/vercel/ai/tree/HEAD/packages/openai-compatible) | `3.0.59` | `3.0.81` |
| [ai](https://github.com/vercel/ai/tree/HEAD/packages/ai) | `7.0.122` | `7.0.157` |



Updates `@ai-sdk/anthropic` from 4.0.68 to 4.0.92
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/anthropic/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/@ai-sdk/anthropic@4.0.92/packages/anthropic)

Updates `@ai-sdk/google` from 4.0.85 to 4.0.108
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/google/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/@ai-sdk/google@4.0.108/packages/google)

Updates `@ai-sdk/openai` from 4.0.81 to 4.0.105
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/openai/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/@ai-sdk/openai@4.0.105/packages/openai)

Updates `@ai-sdk/openai-compatible` from 3.0.59 to 3.0.81
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/openai-compatible/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/@ai-sdk/openai-compatible@3.0.81/packages/openai-compatible)

Updates `ai` from 7.0.122 to 7.0.157
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/ai/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/ai@7.0.157/packages/ai)

---
updated-dependencies:
- dependency-name: "@ai-sdk/anthropic"
  dependency-version: 4.0.72
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: ai-sdk
- dependency-name: "@ai-sdk/google"
  dependency-version: 4.0.88
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: ai-sdk
- dependency-name: "@ai-sdk/openai"
  dependency-version: 4.0.84
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: ai-sdk
- dependency-name: "@ai-sdk/openai-compatible"
  dependency-version: 3.0.63
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: ai-sdk
- dependency-name: ai
  dependency-version: 7.0.128
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: ai-sdk
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps-dev): bump the ai-sdk group with 5 updates build(deps-dev): bump the ai-sdk group across 1 directory with 5 updates Nov 2, 2026
@dependabot
dependabot Bot force-pushed the dependabot/bun/ai-sdk-ad2cd118c5 branch from 591be8a to 7985a7f Compare November 2, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants