Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 14 commits
- 155 files changed
- 7 contributors
Commits on Feb 12, 2026
-
chore(examples): remove obsolete useSearchGrounding in google examples (
#12494) ## Background `useSearchGrounding` is an obsolete provider option for the Google (and Vertex) providers that was deprecated a long time ago. v5 migration guides already include documentation how to migrate away from it, but several examples and e2e tests still referenced it. ## Summary Replaced all `useSearchGrounding` providerOption usages with the current `googleSearch` tool API. The only remaining `useSearchGrounding` reference is in the v5 migration guide, which is correct since it documents historical behavior. ## Manual Verification N/A — example-only changes, verified via `pnpm type-check:full` and running the examples. ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review) ## Future Work N/A ## Related Issues Fixes #12438
-
test(provider/gladia): migrate tests to fixture-based pattern (#12490)
## background gladia tests used inline `prepareJsonResponse` with hand-constructed mock data. this migrates to the fixture-based pattern used across other providers ## summary - add 3 fixture files for gladia's 3-step API flow (upload, initiate, poll result) - rewrite tests to load fixtures from `__fixtures__/` directory - add full snapshot test for `doGenerate` response - add standalone response headers and response metadata tests - all 5 original test cases preserved + 1 new snapshot test ## verification <details> <summary>test output</summary> ``` ✓ src/gladia-transcription-model.test.ts (6 tests) 35ms Test Files 2 passed (2) Tests 7 passed (7) ``` </details> -
fix(vertex): add fallback for providerOptions key (#12403)
## Background multi step tool calls fail because the `thoughtSignature` gets lost due to a key mismatch in providerOptions. if the `thoughtSignature` is passed under the google key, the vertex provider silently drops it. the api then rejects the request and we see the errors as observed in #12351 ## Summary fallback check to see if `vertex` key doesn't have a `thoughtSignature`, we check if it's passed within the google key ## Manual Verification verified via the repro code given in the original issue, which is resolved after the fix ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [ ] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review) ## Related Issues fixes #12351
-
chore(examples): update vulnerable mcp dependency version (#12469)
## Background reported in #12326 but needed some extra changes ## Summary updated dependency version and pnpm lock file
-
docs: use
presentImagesin single image generation example that was……n't using it yet (#12498) ## Background The `registry/generate-image.ts` example was the only image-generating example in `ai-functions` that manually wrote images with `fs.writeFileSync` instead of using the shared `presentImages` helper. ## Summary Replaced the manual `fs.writeFileSync` + `console.log` with a call to `presentImages([image])`, matching other image generation examples.
-
feat(provider/google-vertex): allow using Gemini image models with `g…
…enerateImage` (#12502) ## Background Follow-up to #12252 (which added Gemini image generation to the `google` provider). This wasn't yet wired up for the `google-vertex` provider. ## Summary - Adds Gemini image model support to `google-vertex`'s `generateImage()`. When a `gemini-*` model ID is detected, the image model internally delegates to `GoogleGenerativeAILanguageModel` with `responseModalities: ['IMAGE']`, matching the approach used in the `google` provider. Existing Imagen model behavior is unchanged. - Includes docs for this new `generateImage` capability for `google-vertex` - Also improves provider options typing in both `google` and `google-vertex` image models to use `satisfies GoogleLanguageModelOptions` ## Manual Verification Ran `google-vertex-gemini-image.ts` and `google-vertex-gemini-editing.ts` examples against Vertex AI with real credentials. Both image generation and image editing produce correct results. ## Checklist - [x] Tests have been added / updated (for bug fixes / features) - [x] Documentation has been added / updated (for bug fixes / features) - [x] A _patch_ changeset for relevant packages has been added (for bug fixes / features - run `pnpm changeset` in the project root) - [x] I have reviewed this pull request (self-review) ## Future Work N/A ## Related Issues Fixes #12452
-
refactor(provider/amazon-bedrock): finish fixture migration for doGen…
…erate tests (#12503) ## background amazon-bedrock was partially migrated to the fixture-based test pattern - doStream and some doGenerate tests already used `prepareJsonFixtureResponse` / `prepareChunksFixtureResponse`, but the doGenerate section still had an inline `prepareJsonResponse` helper used by ~29 tests ## summary - remove 2 duplicate tests (`should extract text response` and `should extract usage`) that were identical to existing fixture-based tests in the `describe('text')` block - replace `prepareJsonResponse({})` calls with `prepareJsonFixtureResponse('bedrock-text')` for tests that only check request body/headers - replace `prepareJsonResponse({...specific fields...})` calls with direct `server.urls[generateUrl].response` assignment for tests that need specific response content - delete the `prepareJsonResponse` helper function and unused `BedrockReasoningContentBlock` / `BedrockRedactedReasoningContentBlock` imports no new fixtures were needed - all existing fixtures were already recorded from real API calls ## verification - `grep -c prepareJsonResponse` returns 0 - test count: 103 → 101 (2 duplicates removed) - 290/290 tests pass
-
docs(contribting): correct provider method names for v3 spec and clar…
…ity (#12507) ## Background The contributing docs were outdated, referring to v2 provider spec. ## Summary Updated to v3 spec requirements. Also included a note to focus on clarity for developers and agents - higher priority than brevity.
-
fix/unbounded download dos (#12445)
- Replace unbounded `arrayBuffer()`/`blob()` calls in `download()` and `downloadBlob()` with streaming reads that enforce a **2 GiB default size limit** - Add `abortSignal` passthrough from callers (`transcribe`, `generateVideo`) to `fetch()` - Check `Content-Length` header for early rejection before reading body - Track bytes incrementally via `ReadableStream.getReader()`, abort with `DownloadError` when limit exceeded - Expose configurable `download` parameter on `transcribe()` and `experimental_generateVideo()` (instead of adding a new `maxDownloadSize` argument) — keeps download config separate from API function signatures - Export `createDownload({ maxBytes })` factory from `ai` for custom size limits closes #9481 / addresses #9481 (comment) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>3 people authoredFeb 12, 2026
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff ai@6.0.83...ai@6.0.84