@ai-sdk/voyage
A provider package within the Vercel AI SDK ecosystem that integrates Voyage AI's embedding and reranking model services, enabling developers to call Voyage model capabilities through a unified SDK interface.
Core Facts
This release aligns the toolchain versions to ai@7.0.130, @ai-sdk/provider@4.0.24, and @ai-sdk/provider-utils@5.0.56.
The main changes in @ai-sdk/togetherai@3.0.51 are focused on dependency upgrades and contain no breaking changes.
When upgrading @ai-sdk/voyage, it is recommended to simultaneously update @ai-sdk/provider and @ai-sdk/provider-utils to ensure dependency tree version alignment
Timeline (last 90 days)
@ai-sdk/voyage@2.0.62 will not change existing call methods, nor will it bring breaking behavioral changes.
@ai-sdk/voyage has released version 2.0.62, a patch update marked as Patch Changes, released on October 16.
Voyage is one of the providers focused on embedding models; @ai-sdk/voyage only needs to implement the embedding-related interfaces, making it smaller in size than language model adapter packages.
The public API of @ai-sdk/voyage did not change in version 1.0.38; the calling method, parameter structure and return format of Voyage embedding all remain the same.
In projects outside the monorepo, the recommended way to upgrade such patch packages is to explicitly run `npm update @ai-sdk/voyage` or `pnpm up`, so that the entire dependency subtree advances in sync.
When provider-utils is upgraded but the package.json of @ai-sdk/voyage still specifies a looser range (such as ^4.0.60) and the lockfile is not refreshed, the version actually installed may be an old provider-utils, causing a version mismatch problem.
Upgrading to @ai-sdk/voyage@2.0.60 is basically zero-risk, but behavior changes brought by the dependency upgrade (such as retry counts and error classification), while not breaking the API, may still affect runtime behavior in edge cases; in production environments it is recommended to run the existing test cases after upgrading.
Voyage AI's own model service (such as the voyage-3 series) and the npm package @ai-sdk/voyage are two different things: the former is a remote API, while the latter is merely an SDK adapter layer for calling it.
In AI SDK, @ai-sdk/voyage wraps the Voyage AI service into an interface consistent with providers such as OpenAI and Cohere, enabling developers to call different vendors' vector models with a unified embed/embedMany
The release notes of @ai-sdk/voyage@1.0.35 include an accumulation of 2864 commits since the previous version
39 more timeline events
All Facts (20)
This release aligns the toolchain versions to ai@7.0.130, @ai-sdk/provider@4.0.24, and @ai-sdk/provider-utils@5.0.56.
90%VerifiedThe main changes in @ai-sdk/togetherai@3.0.51 are focused on dependency upgrades and contain no breaking changes.
90%VerifiedWhen upgrading @ai-sdk/voyage, it is recommended to simultaneously update @ai-sdk/provider and @ai-sdk/provider-utils to ensure dependency tree version alignment
90%Verified@ai-sdk/voyage is the official provider package within the Vercel AI SDK dedicated to Voyage AI embedding models
90%VerifiedPatch version updates theoretically contain no breaking changes, making the upgrade risk low.
90%Verified@ai-sdk/vue is a high-level wrapper for the Vue framework, with underlying dependencies on the ai core package and @ai-sdk/provider-utils.
80%VerifiedPatch version upgrades generally do not require modifications to existing business code, but it is recommended to run integration tests after upgrading to confirm dependency version compatibility.
75%VerifiedThe Patch Changes for @ai-sdk/vue 2.0.262 this time only noted the dependency sync for ai@5.0.262, with no specific feature changes listed.
75%VerifiedThe core change in version 2.0.44 is following the upgrade of its underlying dependency @ai-sdk/provider-utils to version 5.0.44.
75%VerifiedEven for patch updates, it is recommended to run the full test suite in the CI pipeline to ensure consistent application behavior after upgrading.
75%Partially VerifiedThe core change in @ai-sdk/xai@5.0.13 is migrating the package build toolchain from tsup to tsdown.
90%UnverifiedVoyage's models can be called via its REST API, and @ai-sdk/voyage wraps that call into a provider conforming to the unified interface of the Vercel AI SDK.
70%Partially Verified@ai-sdk/voyage released version 2.0.59, marked as Patch Changes, containing 3 commits, belonging to the main branch, and automatically published by github-actions.
75%UnverifiedWhen provider-utils is upgraded but the package.json of @ai-sdk/voyage still specifies a looser range (such as ^4.0.60) and the lockfile is not refreshed, the version actually installed may be an old provider-utils, causing a version mismatch problem.
50%UnverifiedThe public API of @ai-sdk/voyage did not change in version 1.0.38; the calling method, parameter structure and return format of Voyage embedding all remain the same.
50%UnverifiedIn projects outside the monorepo, the recommended way to upgrade such patch packages is to explicitly run `npm update @ai-sdk/voyage` or `pnpm up`, so that the entire dependency subtree advances in sync.
50%UnverifiedVoyage is one of the providers focused on embedding models; @ai-sdk/voyage only needs to implement the embedding-related interfaces, making it smaller in size than language model adapter packages.
50%UnverifiedVoyage AI's own model service (such as the voyage-3 series) and the npm package @ai-sdk/voyage are two different things: the former is a remote API, while the latter is merely an SDK adapter layer for calling it.
50%UnverifiedUpgrading to @ai-sdk/voyage@2.0.60 is basically zero-risk, but behavior changes brought by the dependency upgrade (such as retry counts and error classification), while not breaking the API, may still affect runtime behavior in edge cases; in production environments it is recommended to run the existing test cases after upgrading.
50%UnverifiedThe release notes of @ai-sdk/voyage@1.0.35 include an accumulation of 2864 commits since the previous version
50%