@ai-sdk/zai
An official provider package within the Vercel AI SDK ecosystem for integrating Zhipu (Z.ai) models. Built on the @ai-sdk/openai-compatible compatibility layer, it supports connectivity with Zhipu's GLM series of language models.
Core Facts
The main changes in @ai-sdk/togetherai@3.0.51 are focused on dependency upgrades and contain no breaking changes.
@ai-sdk/vue is the adapter layer for the Vercel AI SDK within the Vue ecosystem.
A patch version update (1.0.104 → 1.0.105) signifies backward-compatible bug fixes or dependency updates, without introducing breaking changes.
Timeline (last 90 days)
Version 3.0.41 contains only one commit (e197b50) and is a standard Patch Changes release.
Version 3.0.40 contains documentation maintenance commit e729d58, which updates README.md to unify formatting and avoid duplicate content.
The release was triggered by the github-actions bot on October 24 at 18:01.
@ai-sdk/zai 3.0.39 is a patch release that only synchronizes the versions of three upstream dependency packages, with no new features or API changes.
Transitive updates in the dependency chain may indirectly introduce behavioral changes from upstream packages; after upgrading, it is recommended to run the existing tests, especially scenarios involving streaming output.
In a dependency chain, patch versions can still introduce behavioral changes through upgraded transitive dependencies, so it is recommended to run the test suite even for patch updates.
These release notes do not disclose the specific code changes and only give the dependency version numbers.
For production environments, if the current version runs stably there is no need to rush to follow this patch; if you are investigating behavioral differences at the provider layer, it is worth including in the comparison.
The core change in version 1.0.8 is deferred validation mode construction, to reduce the provider's import time.
Before 1.0.8, importing @ai-sdk/zai would immediately execute validation logic, even if the current call did not involve any data path requiring validation.
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%Verified@ai-sdk/vue is the adapter layer for the Vercel AI SDK within the Vue ecosystem.
90%VerifiedA patch version update (1.0.104 → 1.0.105) signifies backward-compatible bug fixes or dependency updates, without introducing breaking changes.
90%VerifiedThis release record was completed by a GitHub Actions automated workflow and carries an official GitHub verified signature (Verified).
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%VerifiedThe upgrade method is to run npm install @ai-sdk/openai@4.0.60.
90%Verified@ai-sdk/zai is the official Provider in the Vercel AI SDK for Zhipu AI models.
90%Verified@ai-sdk/zai@3.0.8 introduces no breaking changes and no new features.
90%Verified@ai-sdk/zai@3.0.8 synchronously updated upstream dependencies: @ai-sdk/provider@4.0.12, @ai-sdk/openai-compatible@3.0.46, and @ai-sdk/provider-utils@5.0.38.
90%VerifiedThe zai provider depends on @ai-sdk/openai-compatible, indicating it is most likely built on top of an OpenAI-compatible interface.
85%Verified@ai-sdk/zai depends on @ai-sdk/openai-compatible, indicating that Zhipu GLM's API interface is largely compatible with OpenAI's calling conventions.
85%Verified@ai-sdk/openai-compatible's core responsibilities include: converting the AI SDK's unified call parameters into OpenAI format, parsing responses and mapping them back to the AI SDK's standardized results, and handling chunking and errors in streaming responses.
80%VerifiedWithin the AI SDK ecosystem, there exists an adapter package @ai-sdk/zod similar to @ai-sdk/valibot, with both providing the same public interface.
80%VerifiedThis update upgrades the dependency ai to 7.0.102 and @ai-sdk/provider-utils to 5.0.41.
80%VerifiedThe @ai-sdk/zai module depends on foundational modules such as provider, openai-compatible, and provider-utils.
80%VerifiedYou can upgrade via the command npm install @ai-sdk/zai@1.0.3 or yarn add @ai-sdk/zai@1.0.3.
80%VerifiedIn a dependency chain, patch versions can still introduce behavioral changes through upgraded transitive dependencies, so it is recommended to run the test suite even for patch updates.
75%Verified@ai-sdk/zai, as the Provider implementation for Z.ai, reuses the communication and protocol handling logic of the OpenAI compatibility layer at its foundation.
75%VerifiedFor projects using @ai-sdk/zai, upgrading to 3.0.25 is generally safe and recommended, as patch versions follow SemVer and do not introduce breaking changes.
75%Verified@ai-sdk/mcp@1.0.86 is a pure bug fix and does not involve any breaking API changes.
75%