fix(core): upgrade Bedrock and Vertex providers to AI SDK v6

Merged
AR
17d ago
+223-204

PR Checklist

Bugs / Features

  • Related issue(s) linked
  • Docs have been added / updated
  • Changesets have been added

What is the current behavior?

Core bundles the AI SDK v5 releases of the Amazon Bedrock and Google Vertex providers. Their @ai-sdk/provider-utils@3 dependencies contribute the old undici@5 and @fastify/busboy@2 dependency chain.

What is the new behavior?

Upgrade @ai-sdk/amazon-bedrock and @ai-sdk/google-vertex from v3 to ^4.0.0, their AI SDK v6 releases, and update the lockfile.

Document that GOOGLE_VERTEX_API_KEY enables Vertex express mode and bypasses project, location, and application default credentials. Keep this note in the docs generator and both Vertex provider pages. The changeset also records Bedrock temperature clamping.

Ollama stays on ^1.5.3. Remove the core streaming-error workaround and the new provider spec file. The changeset records that Ollama's vulnerable dependency chain remains pending a follow-up upgrade.

Fixes issue: N/A.

Validation

  • Core suite with type checking passes. 110 test files, 1,400 tests passed, 2 skipped, and 1 todo.
  • pnpm --filter @voltagent/core typecheck passes.
  • Frozen, offline core dependency install passes.
  • Targeted Biome and Prettier checks pass.
  • Verified the docs generator emits the same Vertex note as both checked-in pages.
  • Verified only the Bedrock and Vertex dependency declarations differ from the base. The registry matches the base and the new spec file is absent.

Notes for reviewers

This PR does not remove every vulnerable dependency path from core. The Ollama upgrade and upstream streaming-error fix are deferred. Full monorepo tests, a fresh security scan, and live cloud-provider calls were not run for this revision.

Summary by CodeRabbit

  • Updates

    • Updated the Amazon Bedrock and Google Vertex integrations to their 4.x releases.
    • Bedrock temperatures outside the supported 0–1 range are clamped, with a warning.
    • Setting a Google Vertex API key selects express mode; project, location, and application credentials are ignored.
  • Documentation

    • Clarified Google Vertex express-mode behavior in the provider documentation.