@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
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
@ai-sdk/voyage is the official provider package within the Vercel AI SDK dedicated to Voyage AI embedding models
Timeline (last 90 days)
The release notes for @ai-sdk/voyage@2.0.71 carry limited information, listing only dependency changes without any migration guide or description of behavior changes.
@ai-sdk/voyage@2.0.71 introduces no new features.
The commit that released 1.0.40 was completed automatically by the github-actions bot, with commit hash 165a954, and came with GitHub's verified signature.
The third digit in 1.0.40 corresponds to the patch position in Semantic Versioning (SemVer), which by convention contains only backward-compatible bug fixes.
@ai-sdk/voyage wraps Voyage AI's text embedding and rerank services, and is commonly used in the retrieval stage of RAG.
After upgrading @ai-sdk/voyage to 2.0.70, behavior is highly likely to remain unchanged, but underlying dependency fixes may bring subtle differences, so it is recommended to run existing tests after updating the lockfile.
Commit e729d58 adjusted README.md with the aim of unifying the documentation format and eliminating duplicate content.
The responsibility of adapter packages is protocol translation and parameter mapping, so maintenance changes at the documentation and dependency level will not change the model's actual coding capability.
@ai-sdk/tui@1.0.147 contains 2 commits, and the release notes list three dependency update commits: 0c2a9de, 3785b2e, and ab8eb61.
In the npm ecosystem, @ai-sdk/voyage does not itself directly implement HTTP requests and parameter validation; instead it relies on the interface conventions provided by @ai-sdk/provider and the shared utilities provided by @ai-sdk/provider-utils.
40 more timeline events
All Facts (20)
The 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%VerifiedThe Vercel AI SDK's unified multi-vendor abstraction layer is implemented based on a Provider plugin mechanism, where each vendor adapter is responsible for converting that vendor's raw HTTP API into the SDK's internal standard LanguageModelV1 interface.
80%VerifiedThe release of @ai-sdk/workflow@2.0.77 was completed automatically by the github-actions bot, contains 3 commits, was merged into the main branch, and has commit hash be27bec.
75%VerifiedIt is recommended to upgrade related @ai-sdk/* packages as a group, since provider-utils has been synchronized to 5.0.49.
75%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%VerifiedPatch versions can generally be upgraded directly with very low risk.
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%VerifiedUpgrading to @ai-sdk/voyage 2.0.44 is generally a low-risk operation and will not change existing calling patterns.
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%VerifiedIt is recommended to run the full test suite after upgrading, especially when the project simultaneously locks the versions of related dependencies such as ai and @ai-sdk/provider.
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%Verified@ai-sdk/voyage has released version 2.0.62, a patch update marked as Patch Changes, released on October 16.
80%Verified@ai-sdk/svelte released version 5.0.93.
90%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%UnverifiedThe commit that released 1.0.40 was completed automatically by the github-actions bot, with commit hash 165a954, and came with GitHub's verified signature.
70%