Skip to content

fix(deps): update ai sdk (major) - #151

Merged
dawsontoth merged 1 commit into
mainfrom
renovate/major-ai-sdk
Aug 17, 2026
Merged

fix(deps): update ai sdk (major)#151
dawsontoth merged 1 commit into
mainfrom
renovate/major-ai-sdk

Conversation

@renovate

@renovate renovate Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@ai-sdk/google (source) ^3.0.24^4.0.0 age confidence
@ai-sdk/openai (source) ^3.0.26^4.0.0 age confidence
ai (source) ^6.0.79^7.0.0 age confidence
ollama-ai-provider-v2 ^3.3.0^4.0.0 age confidence

Release Notes

vercel/ai (@​ai-sdk/google)

v4.0.44

Compare Source

Patch Changes
  • 16650e9: feat(google): add gemini-3.7-flash model

v4.0.43

Patch Changes
  • 8e90283: Preserve forced tool calls when strict function tools are configured.

v4.0.42

Patch Changes

v4.0.41

Patch Changes
  • da78d58: fix(google): convert enum values to the Gemini schema format
  • 8a2482d: Preserve Google API error details in APICallError.data.

v4.0.40

Compare Source

Patch Changes

v4.0.39

Compare Source

Patch Changes

v4.0.38

Compare Source

Patch Changes

v4.0.37

Compare Source

Patch Changes
  • bbd9b31: chore: rename *TranslationModel and its related types to *SpeechTranslationModel for consistency

v4.0.36

Compare Source

Patch Changes

v4.0.35

Compare Source

Patch Changes

v4.0.34

Compare Source

Patch Changes

v4.0.33

Compare Source

Patch Changes

v4.0.32

Compare Source

Patch Changes
  • 79e133c: async APIs for generateVideo (poll, webhook)

    Adds an asynchronous start/status flow to the experimental video model
    interface (VideoModelV4): models may now implement doStart, doStatus,
    and handleWebhookOption instead of (or in addition to) doGenerate, and
    experimental_generateVideo accepts poll and webhook options to
    orchestrate completion via polling or webhooks. Polling configuration can use
    a custom delay implementation for durable workflow compatibility.

  • Updated dependencies [79e133c]

v4.0.31

Compare Source

Patch Changes

v4.0.30

Compare Source

Patch Changes

v4.0.29

Compare Source

Patch Changes

v4.0.28

Compare Source

Patch Changes

v4.0.27

Compare Source

Patch Changes
  • d2d9324: Forward topK through Google Interactions requests and warn when unsupported frequency or presence penalties are provided.
  • 8bedb2c: Allow fetch to derive the content length for Google file upload request bodies.

v4.0.26

Compare Source

Patch Changes
  • c49380c: feat: add experimental streaming speech translation models (openai.translation('gpt-realtime-translate') over the OpenAI Realtime translations WebSocket and google.translation('gemini-3.5-live-translate-preview') over the Gemini Live API). connectToWebSocket in @ai-sdk/provider-utils now passes close code and reason to onClose (additive, optional parameter).
  • Updated dependencies [0c464d9]
  • Updated dependencies [c49380c]

v4.0.25

Compare Source

Patch Changes

v4.0.24

Compare Source

Patch Changes
  • c57a353: fix(google): omit unsupported function call IDs

v4.0.23

Compare Source

Patch Changes
  • f126649: feat(provider/google): default unknown Gemini model IDs to the newest supported capabilities

v4.0.22

Compare Source

Patch Changes
  • 66b7151: fix(provider/google): preserve Gemini Live lifecycle events
  • 5e5453c: Avoid missing thought-signature warnings and skip-validator injection for valid unsigned Gemini 3 parallel function calls in the same model response.

v4.0.21

Compare Source

Patch Changes
  • 7c16f21: feat(google): add gemini-3.6-flash and gemini-3.5-flash-lite models

v4.0.20

Compare Source

Patch Changes

v4.0.19

Compare Source

Patch Changes
  • a70b027: fix(provider/google): associate multiple code execution results with their tool call
  • a3ce307: fix(provider/google): surface Gemini responseId as response-metadata (stream) and response.id (generate)

v4.0.18

Compare Source

Patch Changes

v4.0.17

Compare Source

Patch Changes
  • 5b4a299: fix(provider/google): forward Vertex-only imageConfig options (personGeneration, prominentPeople, imageOutputOptions)

v4.0.16

Compare Source

Patch Changes
  • 662ddfc: Allow google.interactions agent requests to include supported tools, including file_search.

v4.0.15

Compare Source

Patch Changes

v4.0.14

Compare Source

Patch Changes
  • 4be62c1: fix(provider-utils): validate provider-response URLs in getFromApi

    getFromApi now has a validateUrl flag. It is optional so existing callers keep compiling (omitting it behaves like false, i.e. no validation), but all AI SDK provider packages set it explicitly at every call site so each one makes a visible trust decision. When true, the URL is routed through fetchWithValidatedRedirects — the same guard used by downloadBlob — which rejects private/loopback/link-local targets, re-validates every redirect hop, strips proxy/metadata/cookie request headers, and drops all caller headers except the user-agent on cross-origin redirects (custom API-key headers must not follow a redirect off-origin any more than Authorization may); blocked URLs throw DownloadError. It is enabled at the image/video/audio download and polling call sites where the URL comes from a provider response body; URLs built from developer-configured endpoints pass validateUrl: false and are unaffected.

    A new optional credentialedOrigin withholds caller headers unless the URL is same-origin with it, so the API key is not sent to a response-supplied host on a different origin.

    A new optional trustedOrigin exempts URLs (and redirect hops) that are same-origin with the developer-configured provider endpoint from target validation, so self-hosted and localhost deployments whose response URLs point back at the configured host keep working; all other hops are still validated.

    Also closes range gaps in validateDownloadUrl (IPv4 224.0.0.0/4 multicast and the TEST-NET documentation ranges 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24; IPv6 documentation ranges 2001:db8::/32 and 3fff::/20), and follows only the fetch-spec redirect status codes (301/302/303/307/308) — a Location header on any other status is not followed. This guard performs string/literal checks only and does not resolve DNS; hostnames that resolve to private addresses and DNS rebinding remain out of scope and must be constrained at the network layer (or by injecting a Node fetch that pins the resolved IP at connect time) for server deployments handling untrusted URLs. See contributing/secure-url-handling.md.

  • Updated dependencies [4be62c1]

  • Updated dependencies [7805e4a]

  • Updated dependencies [cd12954]

v4.0.12

Compare Source

Patch Changes
  • e40118c: Forward text file references as documents when using the Google Interactions API.

v4.0.11

Compare Source

Patch Changes
  • 17d66c5: Fix Google tool result conversion to send file data as inline data instead of JSON text on the legacy tool-result path.
  • 96d40bc: Expand standalone Google threshold provider options into safety settings.
  • 0f93c57: feat (video): support video (not just image) reference inputs in inputReferences for reference-to-video generation
  • Updated dependencies [0f93c57]

v4.0.10

Compare Source

Patch Changes

v4.0.9

Compare Source

Patch Changes
  • 7401c2c: Pass documented Gemini external HTTPS file URLs through without downloading them.

v4.0.8

Compare Source

Patch Changes

v4.0.7

Compare Source

Patch Changes
  • c6f5e62: Prevent prototype pollution when synchronously parsing provider JSON inputs and expose secureJsonParse from provider-utils.
  • bd8d172: Fix Google embedding batch size to respect the Gemini API limit of 100 requests per batch.
  • Updated dependencies [c6f5e62]

v4.0.6

Compare Source

Patch Changes
  • d20f0dc: Add vertex.interactions() for the Gemini Interactions API on Vertex AI. Targets the location-scoped .../locations/{region}/interactions resource using the existing Vertex OAuth credentials, enabling multimodal-output models such as gemini-omni-flash-preview (video output) through Vertex. The GoogleInteractionsLanguageModel is now exported from @ai-sdk/google/internal for provider reuse.

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes
  • dc1eb8d: Support Gemini Interactions video output. Parse video output blocks from the Google Interactions API into file parts (buffered and streaming), and surface the per-modality output token breakdown via providerMetadata.google.outputTokensByModality.

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes
  • ba6d510: chore: fix deprecated use of zod .passthrough()

v4.0.0

Compare Source

Major Changes
  • a3757d7: chore(provider/google): remove useless GenerativeAI affix from types and classes for consistency

  • f7d4f01: feat(provider): add support for reasoning-file type for files that are part of reasoning

  • ef992f8: Remove CommonJS exports from all packages. All packages are now ESM-only ("type": "module"). Consumers using require() must switch to ESM import syntax.

  • c29a26f: feat(provider): add support for provider references and uploading files as supported per provider

  • 3887c70: feat(provider): add new top-level reasoning parameter to spec and support it in generateText and streamText

  • 8359612: Start v7 pre-release

  • 04e9009: chore: make provider implementations code patterns more consistent, including renaming certain exported symbols

    For all externally exported symbols that were renamed, the old names continue to work via deprecated aliases.

Patch Changes
  • 7f04802: feat(provider/google): add support for managed agents in the Interactions API

  • 38fc777: Add AI Gateway hint to provider READMEs

  • b71c0d7: feat(provider/google): support Google search grounding when using generateImage with Gemini

  • 6190649: chore(provider/google): remove obsolete Google image model

  • 55db546: fix(provider/google): fix Gemini service tier enum after upstream update

  • 9a0a618: fix(google): fix serviceTier to be correctly formatted for Vertex API

  • 00a0f36: feat(google, google-vertex): added gemini-embedding-2, deep-research-max-preview-04-2026 and deep-research-preview-04-2026

  • 9715ec7: feat(provider/google): add support for service tier parameter

  • 41da50c: fix(provider/google): support functionCall.id when returned by Gemini API and provide matching functionResponse.id

  • add4326: fix(provider/google): correct JSDoc for multimodal embedding content option

  • a8d70b6: fix(google): auto-inject skip_thought_signature_validator for Gemini 3 tool-call replays without a signature

  • 947cdab: Add Google realtime Live Translation provider options for gemini-3.5-live-translate-preview.

  • 4e825f3: feat(google): update Interactions API implementation to cater for upstream breaking changes coming May 26

  • b563707: feat(provider/google): add Gemini text-to-speech (speech) model support

  • a05109d: feat(provider/google): preserve per-modality token details in usage data

  • cfca634: fix(google): emit Vertex no-args streaming tool calls and preserve thoughtSignature

    Vertex emits a no-args function call as a single chunk shaped { functionCall: { name: 'X' } } with no args, no partialArgs, and no willContinue. The streaming parser had no branch for this shape, so the call was dropped along with any thoughtSignature it carried. For Gemini 3 thinking models this caused the next multi-turn step to 400 with missing thought_signature. The unary (doGenerate) path had the same drop.

    Both paths now emit the call as a complete tool call with '{}' input and propagate thoughtSignature provider metadata.

    Fixes #​14847.

  • c9c4661: fix(provider/google): preserve groundingMetadata and urlContextMetadata when they arrive in a stream chunk before the finishReason chunk

  • 045d2e8: fix(google): read serviceTier from usageMetadata.serviceTier in both generate and stream paths

    The previous implementation read serviceTier from the x-gemini-service-tier
    response header, which is only populated on non-streaming responses. Gemini
    streaming includes the value in usageMetadata.serviceTier on every chunk, so
    providerMetadata.google.serviceTier was always null for streams. Read from
    usageMetadata for both paths instead.

  • 19b95f9: fix(google): use VALIDATED function calling mode when any tool has strict:true

  • 2ce3c65: feat(provider/google-vertex): add Gemini text-to-speech (speech) model support

  • 5878b40: fix(google): prevent prototype pollution when streaming tool args

  • 46d1149: chore(provider-utils,google): fix grammar errors in error and warning messages

  • 6a26901: feat(google): add fileData support to embedding model

  • 01fa606: feat(provider/google): support combining built-in tools with function calling on Gemini 3

  • 5036db8: feat(google-vertex): add support for streaming tool arguments input

  • 9f0e36c: trigger release for all packages after provenance setup

  • a2609df: fix(google): fix streaming tool call args

  • ab43029: feat(provider/google): support multimodal content parts in embedding provider options

  • 82288b0: feat(provider/google): add gemini-embedding-2-preview and fix multimodal embedding support with embedMany

  • b04e23e: feat(provider/google): add support for the Gemini Interactions API

  • 58a2ad7: fix: more precise default message for tool execution denial

  • e59176c: chore(google): update v3 specs to v4

  • ebbb0f2: fix(provider/google): fix lack of image consistency when using Interactions API in stateless mode

  • aeda373: fix: only send provider credentials to same-origin response-supplied URLs

    Several provider clients followed a URL taken from the provider's API response (a polling/status URL or a final media URL such as polling_url, urls.get, result_url, result.sample, or video.uri) and reused the authenticated headers — or appended ?key=<API_KEY> — on that request. Because the host of the response-supplied URL was never validated, the long-lived API key was sent to whatever host the response named (a CDN in the benign case, or an attacker-chosen host if the provider response was tampered with), allowing credential exfiltration.

    A new isSameOrigin helper is added to @ai-sdk/provider-utils, and the affected fetches in @ai-sdk/black-forest-labs, @ai-sdk/fireworks, @ai-sdk/replicate, @ai-sdk/gladia, @ai-sdk/fal, and @ai-sdk/google now attach credentials only when the followed URL is same-origin with the provider's configured API origin. Requests to a foreign origin are made without the credential.

  • 7fc6bd6: Raise minimum supported Node.js version to 22. Supported versions: 22, 24, and 26.

  • 0c4c275: trigger initial canary release

  • bdb9ea1: chore(google): remove now obsolete Interactions API Api-Revision header

  • db394ab: feat(provider/google): support cancelling long-running Interactions API agents via AbortSignal, and process their intermittent stream

  • ce769dd: feat(provider): add experimental Realtime API support for voice conversations

    Adds first-class support for realtime (speech-to-speech) APIs:

    • Experimental_RealtimeModelV4 spec in @ai-sdk/provider with normalized event types and factory
    • OpenAI, Google, and xAI realtime provider implementations
    • openai.experimental_realtime() / google.experimental_realtime() / xai.experimental_realtime() work in both server and browser
    • .getToken() static method on each provider for server-side ephemeral token creation
    • experimental_getRealtimeToolDefinitions helper for provider session tool definitions
    • experimental_useRealtime hook in @ai-sdk/react returning UIMessage[] (aligned with useChat), with onToolCall and addToolOutput for client-driven tool execution
    • inputAudioTranscription session config for showing transcribed user audio messages when supported by the provider
  • 5b7e7c2: fix(google-vertex): don't send streamFunctionCallArguments for unary API calls and change default to false

  • 2edd14e: fix(provider/google): correctly mark reasoning files as such and fix related multi-turn errors

  • 9bd6512: feat(provider): change file part data property to be tagged with a type and remove the image part type

  • 258c093: chore: ensure consistent import handling and avoid import duplicates or cycles

  • 546cefe: feat(provider/google): add gemini-3.5-flash

  • 5463d0d: feat(provider): align tool result output content file part types with top-level message file part types

  • 55f0938: chore(provider/google): update available models

  • b8396f0: trigger initial beta release

  • 84f36e0: fix(google): omit passing includeServerSideToolInvocations for Vertex tool_config

  • 90e2d8a: chore: fix unused vars not being flagged by our lint tooling

  • 4dac142: feat(google): add new finishMessage field in providerMetadata

  • aeea161: feat(google): read serviceTier from x-gemini-service-tier response header in Gemini API and use PayGo for Vertex

  • 18c1970: feat(provider/google): Add multimodal tool-result support for Google function responses.

    Tool results with output.type = 'content' now map media parts into
    functionResponse.parts for Google models, including image-data,
    file-data, and base64 data: URLs in URL-style content parts.
    Remote HTTP(S) URLs in URL-style tool-result parts are not supported.

  • b3976a2: Add workflow serialization support to all provider models.

    @ai-sdk/provider-utils: New serializeModel() helper that extracts only serializable properties from a model instance, filtering out functions and objects containing functions. Third-party provider authors can use this to add workflow support to their own models.

    All providers: headers is now optional in provider config types. This is non-breaking — existing code that passes headers continues to work. Custom provider implementations that construct model configs manually can now omit headers, which is useful when models are deserialized from a workflow step boundary where auth is provided separately.

    All provider model classes now include WORKFLOW_SERIALIZE and WORKFLOW_DESERIALIZE static methods, enabling them to cross workflow step boundaries without serialization errors.

  • ff5eba1: feat: roll image-* tool output types into their equivalent file-* types

v3.0.110

Compare Source

Patch Changes

v3.0.109

Compare Source

Patch Changes
  • 71e94ad: feat(google): add gemini-3.7-flash model

v3.0.108

Compare Source

Patch Changes
  • dd7ecd7: Preserve forced tool calls when strict function tools are configured.

v3.0.107

Compare Source

Patch Changes

v3.0.106

Compare Source

Patch Changes

v3.0.105

Compare Source

Patch Changes

v3.0.104

Compare Source

Patch Changes
vercel/ai (@​ai-sdk/openai)

v4.0.41

Compare Source

Patch Changes
  • 59d6def: Reconstruct provider-executed shell calls when continuing OpenAI Responses with storage disabled.

v4.0.40

Patch Changes
  • e19a4a6: Avoid duplicate MCP approval request references when continuing stored OpenAI Responses.

v4.0.39

Patch Changes

v4.0.38

Patch Changes
  • d302134: Keep client-executed function calls paired with their outputs when chaining OpenAI Responses with a previous response ID.

v4.0.37

Compare Source

Patch Changes

v4.0.36

Compare Source

Patch Changes
  • 6157098: fix(openai): serialize tool text outputs when an output schema is configured
  • 4cd4548: Accept serviceTier: 'fast' on OpenAI chat and responses models. OpenAI renamed priority processing to Fast mode and accepts service_tier: 'fast' and 'priority' interchangeably, so 'fast' is now passed through verbatim and gated on the same model capability as 'priority'.
  • Updated dependencies [ad6a650]
  • Updated dependencies [81cd026]

v4.0.35

Compare Source

Patch Changes

v4.0.34

Compare Source

Patch Changes
  • 73d48d0: fix(provider/openai): correlate rotating Responses API item IDs by output index
  • bbd9b31: chore: rename *TranslationModel and its related types to *SpeechTranslationModel for consistency

v4.0.33

Compare Source

Patch Changes
  • e6a93c4: feat(openai): support batch APIs with experimental_startTextBatch

v4.0.32

Compare Source

Patch Changes

v4.0.31

Compare Source

Patch Changes

v4.0.30

Compare Source

Patch Changes

v4.0.29

Compare Source

Patch Changes

v4.0.28

Compare Source

Patch Changes

v4.0.27

Compare Source

Patch Changes

v4.0.26

Compare Source

Patch Changes

v4.0.25

Compare Source

Patch Changes
  • beaecb3: fix(provider/openai): resolve responses doStream at response.in_progress instead of first output token

    The early-stream-error peek treated response.in_progress as an unknown chunk, so doStream did not resolve until the first output item arrived — delaying stream availability (and downstream TTFB for proxies/gateways) by the model's full time-to-first-token. response.in_progress is now modeled in the chunk schema and marks the request as accepted: the peek keeps watching for error frames for a short grace window (50ms) so quota/rate-limit errors flushed alongside response.in_progress still throw as retryable APICallErrors, while healthy streams become available right after upstream acknowledges the request.

  • b192878: feat: add experimental_toolCaller routing to generateText for code mode

  • Updated dependencies [d8210b6]

  • Updated dependencies [b192878]

v4.0.24

Compare Source

Patch Changes

v4.0.23

Compare Source

Patch Changes
  • 96a237d: Add blocked domain filters to the OpenAI and Azure Responses API web search tools.

v4.0.22

Compare Source

Patch Changes
  • c49380c: feat: add experimental streaming speech translation models (openai.translation('gpt-realtime-translate') over the OpenAI Realtime translations WebSocket and google.translation('gemini-3.5-live-translate-preview') over the Gemini Live API). connectToWebSocket in @ai-sdk/provider-utils now passes close code and reason to onClose (additive, optional parameter).
  • Updated dependencies [0c464d9]
  • Updated dependencies [c49380c]

v4.0.21

Compare Source

Patch Changes

v4.0.20

Compare Source

Patch Changes
  • 1f6dd3a: Add OpenAI Responses Programmatic Tool Calling with hosted program tools, function caller controls, structured output schemas, and multi-step continuation support.

v4.0.19

Compare Source

Patch Changes
  • 34c53c0: Apply reasoning, service tier, and image defaults to recognizable future OpenAI model family versions.

v4.0.18

Compare Source

Patch Changes
  • bc43dc2: Preserve stored tool search output item IDs from provider metadata.

v4.0.17

Compare Source

Patch Changes

v4.0.16

Compare Source

Patch Changes
  • 75f86f4: fix(provider/openai, provider/open-responses): throw

Note

PR body was truncated to here.


Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "before 9am on Monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@dawsontoth dawsontoth left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. This is the AI SDK v4-spec bump done correctly — bumped as a set, which is what makes it safe.

What it does

ai                     ^6.0.79  -> ^7.0.0     (7.0.65)
@ai-sdk/google         ^3.0.24  -> ^4.0.0     (4.0.44)
@ai-sdk/openai         ^3.0.26  -> ^4.0.0     (4.0.41)
ollama-ai-provider-v2  ^3.3.0   -> ^4.0.0     (4.0.1)
@ai-sdk/anthropic      ^4.0.0   (unchanged, already v4)

The spec-version gate passes

This repo's real risk on any @ai-sdk/* bump is lifecycle/getModel.ts, which wraps every provider in aisdk() from @openai/agents-extensions/ai-sdk — and that bridge hard-throws on an unexpected specificationVersion. Unit tests can't see it, because getModel.test.ts mocks both @ai-sdk/anthropic and the bridge, so all 345 tests pass regardless. Checked it directly instead.

Before (main) — mixed, because @ai-sdk/anthropic@4 was already ahead of its siblings:

provider spec
anthropic v4
google / openai / ollama v3

That also left two copies of @ai-sdk/provider in the tree (3.0.14 hoisted + 4.0.7 nested under anthropic).

After (this branch) — uniform, one flattened provider copy:

provider spec
anthropic / google / openai / ollama v4

@ai-sdk/provider dedupes to a single 4.0.7. That's the shape you want.

@openai/agents-extensions@0.14.3 stays put and explicitly admits this combination:

"peerDependencies": {
  "@ai-sdk/provider": "^2.0.0 || ^3.0.0 || ^4.0.0",
  "ai": "^6.0.0 || ^7.0.0"
}

Verified past the type level, per the probe recipe — new Agent({ model: aisdk(...) }) + run() with invalid keys and OPENAI_AGENTS_DISABLE_TRACING=1:

anthropic  -> APICallError | invalid x-api-key                              PASS
google     -> APICallError | API key not valid. Please pass a valid API key. PASS

Reaching the provider's auth rejection is the pass signal — no Unsupported AI SDK specificationVersion. Same probe on main also passes, so to be clear: this is not fixing a live breakage, it's a clean forward move that removes the v3/v4 straddle and the duplicate @ai-sdk/provider.

Local verification

npm ci               # exit 0
npm run lint         # exit 0
npm run format       # exit 0
npm run build        # exit 0   (CI has no build job — checked manually)
npm run test         # exit 0   53 files, 345 tests passing

npm run build matters most here given agent#145 and agent#150 both broke the build behind green checks. It's clean on this branch.

Note on the sibling PRs

  • #148 (chore(deps): update ai sdk, lockfile-only, keeps ai on 6.x) is superseded by this — Renovate should auto-close it once this lands. Its contents are fine, just redundant.
  • #150 (@openai/agents 0.15) is independent and currently blocked on a build break; it does not interact with this PR. Merging this one does not depend on that being resolved.
  • ai itself has no direct import anywhere in the source — it's carried as a declared dependency to satisfy the agents-extensions peer range, so keeping it aligned (as this PR does) is the right maintenance move.

🤖 Verified locally by Claude Opus 5 via scheduled Renovate triage

@dawsontoth dawsontoth mentioned this pull request Aug 17, 2026
1 task
@dawsontoth
dawsontoth merged commit 10382b6 into main Aug 17, 2026
5 checks passed
@dawsontoth
dawsontoth deleted the renovate/major-ai-sdk branch August 17, 2026 16:37
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.16.40 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant