Expired70% confidenceDecision RuleExact time
For projects pinned to @ai-sdk/xai, it is recommended to follow the upgrade to 3.0.141, because the value of a patch version lies in obtaining upstream fixes with minimal risk, and all changes in this release are at the dependencies level with no API signature changes, so the upgrade path should be smooth.
2
Sources
70%
Confidence
Short-term (~14 days)
Relevance
10/15/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 10/29/2026(expired)
Sources
Related Entities
Related Claims
UnverifiedFor 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.77% similarUnverifiedUpgrading to @ai-sdk/vue 4.0.139 usually does not introduce breaking changes, because the major version number remains at 4.x, indicating that the adapter layer's API remains stable.77% similarUnverifiedAs a patch update, upgrading to @ai-sdk/xai@2.0.99 is not mandatory unless a specific issue related to the dependency is encountered.77% similarUnverifiedSince no public API changes are involved, developers can generally upgrade @ai-sdk/zai to 3.0.28 with confidence and will typically not incur additional adaptation costs.76% 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.76% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1032889API
curl https://kongchang.com/api/v1/knowledge/claims/1032889MCP
get_claim(id=1032889)