@ai-sdk/valibot
A validation adapter package in the Vercel AI SDK ecosystem. It serves as a bridge layer that translates the AI SDK's internal data structure conventions into schemas understood by the valibot validation library, and is used for structured validation of LLM output.
Core Facts
v0.40.5 was automatically released by GitHub Actions with a GPG-verified signature.
@ai-sdk/provider-utils, as the underlying shared utility package, is jointly depended upon by multiple upper-layer adapter packages such as @ai-sdk/valibot and @ai-sdk/zod.
The Vercel AI SDK adopts a Monorepo single-repository management model, with the core package ai and various framework adapter packages (such as @ai-sdk/vue, @ai-sdk/react, and @ai-sdk/svelte) released in coordination.
Timeline (last 90 days)
For projects using @ai-sdk/valibot, it is recommended to declare a ^3.0.70 range in package.json and pin the version with a lockfile.
After upgrading to 3.0.70, if you also depend on @ai-sdk/provider-utils, it is recommended to check whether its version has been aligned to 5.0.70, to avoid two different minor versions coexisting.
The `@ai-sdk/typesafe-ai` package released version 3.0.27, which is a Patch Changes version and introduces no new features or breaking changes.
When the version of provider-utils that an adapter depends on is inconsistent with that of the main package, hidden failures such as mismatched type definitions and differences in the behavior of runtime utility functions may occur.
Projects using Valibot can use @ai-sdk/valibot to perform type-safe validation of tool parameters in calls such as generateText and streamText.
Version 3.0.40 contains documentation maintenance commit e729d58, which updates README.md to unify formatting and avoid duplicate content.
When an upper-layer adapter package releases a patch together with the underlying utility package, it usually means the underlying utility fixed a broadly impactful bug that requires synchronized dependency versions, or that the upper package's validation-related type definitions need to stay consistent with provider-utils' new types.
@ai-sdk/valibot must be version-aligned with @ai-sdk/provider-utils; otherwise type mismatches or differences in validation behavior may occur.
After upgrading @ai-sdk/valibot to 3.0.64, existing code requires no changes and behavior is expected to remain consistent.
@ai-sdk/valibot 3.0.64 merged two related commits (0c2a9de and 200c47f).
40 more timeline events
All Facts (20)
v0.40.5 was automatically released by GitHub Actions with a GPG-verified signature.
90%Verified@ai-sdk/provider-utils, as the underlying shared utility package, is jointly depended upon by multiple upper-layer adapter packages such as @ai-sdk/valibot and @ai-sdk/zod.
90%VerifiedThe Vercel AI SDK adopts a Monorepo single-repository management model, with the core package ai and various framework adapter packages (such as @ai-sdk/vue, @ai-sdk/react, and @ai-sdk/svelte) released in coordination.
90%Verified@ai-sdk/valibot is a Valibot integration module provided by the Vercel AI SDK, allowing developers to use Valibot to define data structures and integrate them into the AI SDK's generation pipeline.
85%VerifiedAI SDK's framework adapter packages keep their patch version numbers aligned with the core package (for example, ai@7.0.140 corresponds to @ai-sdk/svelte@5.0.140).
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%VerifiedWhen a foundational package such as @ai-sdk/provider-utils that is depended upon by multiple packages is updated, Changeset automatically marks the packages that depend on it for a patch version bump, which is why @ai-sdk/valibot publishes a new version even though its own code has not changed.
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%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/valibot 3.0.59 is a Patch-level patch release that introduces no breaking changes and does not change the public API shape.
75%Partially VerifiedVersion 3.0.40 contains documentation maintenance commit e729d58, which updates README.md to unify formatting and avoid duplicate content.
90%UnverifiedAfter upgrading to 3.0.70, if you also depend on @ai-sdk/provider-utils, it is recommended to check whether its version has been aligned to 5.0.70, to avoid two different minor versions coexisting.
50%UnverifiedFor projects using @ai-sdk/valibot, it is recommended to declare a ^3.0.70 range in package.json and pin the version with a lockfile.
50%UnverifiedWhen the version of provider-utils that an adapter depends on is inconsistent with that of the main package, hidden failures such as mismatched type definitions and differences in the behavior of runtime utility functions may occur.
50%UnverifiedProjects using Valibot can use @ai-sdk/valibot to perform type-safe validation of tool parameters in calls such as generateText and streamText.
50%UnverifiedWhen an upper-layer adapter package releases a patch together with the underlying utility package, it usually means the underlying utility fixed a broadly impactful bug that requires synchronized dependency versions, or that the upper package's validation-related type definitions need to stay consistent with provider-utils' new types.
50%Unverified@ai-sdk/valibot 3.0.64 merged two related commits (0c2a9de and 200c47f).
50%Unverified@ai-sdk/valibot must be version-aligned with @ai-sdk/provider-utils; otherwise type mismatches or differences in validation behavior may occur.
50%Unverified@ai-sdk/valibot 3.0.63 introduces no new public API; the main change syncs the underlying dependency @ai-sdk/provider-utils to 5.0.63.
50%