ci(changesets): version packages

[voltagent-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@voltagent/core@1.1.7

Patch Changes

• #571 b801a8d Thanks @omeraplak! - feat: add Zod v4 support (backwards-compatible with v3)

  What’s new

  • Core + server now support zod v4 while keeping v3 working.
  • Peer ranges expanded to "zod": "^3.25.0 || ^4.0.0".
  • JSON Schema → Zod conversion handles both versions:
    • Uses zod-from-json-schema@^0.5.0 when Zod v4 is detected.
    • Falls back to zod-from-json-schema@^0.0.5 via alias zod-from-json-schema-v3 for Zod v3.
  • Implemented in MCP client (core) and object handlers (server-core).

  Why

  • Zod v4 introduces changes that require a version-aware conversion path. This update adds seamless compatibility for both major versions.

  Impact

  • No breaking changes. Projects on Zod v3 continue to work unchanged. Projects can upgrade to Zod v4 without code changes.

  Notes

  • If your bundler disallows npm aliasing, ensure it can resolve zod-from-json-schema-v3 (alias to zod-from-json-schema@^0.0.5).

@voltagent/docs-mcp@1.0.2

Patch Changes

• #571 b801a8d Thanks @omeraplak! - feat: add Zod v4 support (backwards-compatible with v3)

  What’s new

  • Core + server now support zod v4 while keeping v3 working.
  • Peer ranges expanded to "zod": "^3.25.0 || ^4.0.0".
  • JSON Schema → Zod conversion handles both versions:
    • Uses zod-from-json-schema@^0.5.0 when Zod v4 is detected.
    • Falls back to zod-from-json-schema@^0.0.5 via alias zod-from-json-schema-v3 for Zod v3.
  • Implemented in MCP client (core) and object handlers (server-core).

  Why

  • Zod v4 introduces changes that require a version-aware conversion path. This update adds seamless compatibility for both major versions.

  Impact

  • No breaking changes. Projects on Zod v3 continue to work unchanged. Projects can upgrade to Zod v4 without code changes.

  Notes

  • If your bundler disallows npm aliasing, ensure it can resolve zod-from-json-schema-v3 (alias to zod-from-json-schema@^0.0.5).

@voltagent/server-core@1.0.7

Patch Changes

• #571 b801a8d Thanks @omeraplak! - feat: add Zod v4 support (backwards-compatible with v3)

  What’s new

  • Core + server now support zod v4 while keeping v3 working.
  • Peer ranges expanded to "zod": "^3.25.0 || ^4.0.0".
  • JSON Schema → Zod conversion handles both versions:
    • Uses zod-from-json-schema@^0.5.0 when Zod v4 is detected.
    • Falls back to zod-from-json-schema@^0.0.5 via alias zod-from-json-schema-v3 for Zod v3.
  • Implemented in MCP client (core) and object handlers (server-core).

  Why

  • Zod v4 introduces changes that require a version-aware conversion path. This update adds seamless compatibility for both major versions.

  Impact

  • No breaking changes. Projects on Zod v3 continue to work unchanged. Projects can upgrade to Zod v4 without code changes.

  Notes

  • If your bundler disallows npm aliasing, ensure it can resolve zod-from-json-schema-v3 (alias to zod-from-json-schema@^0.0.5).

@voltagent/server-hono@1.0.5

Patch Changes

• #571 b801a8d Thanks @omeraplak! - fix: add Zod v3/v4 compatibility layer for @hono/zod-openapi

  • Added dynamic detection of Zod version using toJSONSchema method check
  • Conditionally loads correct @hono/zod-openapi version based on installed Zod
  • Fixed route definitions to use enhanced z from zod-openapi-compat instead of extending base schemas
  • Resolves .openapi() method not found errors when using Zod v4

• #571 b801a8d Thanks @omeraplak! - feat: add Zod v4 support (backwards-compatible with v3)

  What’s new

  • Core + server now support zod v4 while keeping v3 working.
  • Peer ranges expanded to "zod": "^3.25.0 || ^4.0.0".
  • JSON Schema → Zod conversion handles both versions:
    • Uses zod-from-json-schema@^0.5.0 when Zod v4 is detected.
    • Falls back to zod-from-json-schema@^0.0.5 via alias zod-from-json-schema-v3 for Zod v3.
  • Implemented in MCP client (core) and object handlers (server-core).

  Why

  • Zod v4 introduces changes that require a version-aware conversion path. This update adds seamless compatibility for both major versions.

  Impact

  • No breaking changes. Projects on Zod v3 continue to work unchanged. Projects can upgrade to Zod v4 without code changes.

  Notes

  • If your bundler disallows npm aliasing, ensure it can resolve zod-from-json-schema-v3 (alias to zod-from-json-schema@^0.0.5).

• Updated dependencies [b801a8d]:

  • @voltagent/server-core@1.0.7

@voltagent/langfuse-exporter@1.1.1

@voltagent/libsql@1.0.3

@voltagent/postgres@1.0.3

@voltagent/supabase@1.0.2

@voltagent/vercel-ai-exporter@1.0.1

@voltagent/voice@1.0.1

with-jwt-auth@1.0.2

Patch Changes

• Updated dependencies [b801a8d, b801a8d, b801a8d]:
  • @voltagent/server-hono@1.0.5
  • @voltagent/core@1.1.7
  • @voltagent/libsql@1.0.3

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	07feb74
Status:	✅  Deploy successful!
Preview URL:	https://51982537.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs