Expired50% confidenceDecision RuleExact time
For projects using @ai-sdk/typesafe-ai, 3.0.18 is a low-risk upgrade; it is advisable to check whether the provider-related package versions in the lock file are also bumped, to avoid type mismatches caused by multiple versions coexisting.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/12/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 10/26/2026(expired)
Sources
Related Entities
Related Claims
UnverifiedFor 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.76% similarUnverifiedUpgrading to @ai-sdk/voyage 2.0.44 is generally a low-risk operation and will not change existing calling patterns.74% similarUnverified使用 @ai-sdk/xai 调用 Grok 模型的项目建议跟随升级，锁死旧版 provider-utils 的风险通常不在 xAI 调用本身，而在与其他 @ai-sdk/* 包共存时出现的依赖版本漂移。73% similarUnverifiedFor projects that depend on the underlying packages and currently have locked versions spanning major version boundaries, it is necessary to review the changelog when upgrading rather than assessing risk level solely based on the @ai-sdk/zai patch number.72% similarUnverifiedMixing different versions of the workflow, ai, and provider packages may cause type mismatches or runtime exceptions; it is recommended to use a lock file to upgrade the entire SDK ecosystem uniformly.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1008748API
curl https://kongchang.com/api/v1/knowledge/claims/1008748MCP
get_claim(id=1008748)