@mastra/schema-compat 1.3.7-alpha.0 → 1.3.8-alpha.0

package/CHANGELOG.md

@@ -1,1007 +0,0 @@
-# @mastra/schema-compat
-
-## 1.3.7-alpha.0
-
-### Patch Changes
-
-- Optional nested JSON Schema properties with multiple types no longer produce exponentially large OpenAI tool payloads. Payload growth now remains linear as these schemas become more deeply nested. ([#21190](https://github.com/mastra-ai/mastra/pull/21190))
-
-## 1.3.6
-
-### Patch Changes
-
-- Fixed OpenAI structured output requests failing when a schema uses `z.record()`. The OpenAI compatibility layer now removes the `propertyNames` keyword, which OpenAI strict mode does not permit. Requests that used to fail with "Invalid schema ... 'propertyNames' is not permitted" are now accepted. ([#20977](https://github.com/mastra-ai/mastra/pull/20977))
-
-  **Known limitation.** OpenAI strict mode cannot express an open-ended map. A `z.record()` field is still sent as a plain object with no value schema, so the model is not told what keys or values to produce. Use an explicit `z.object({ ... })` shape when you need the model to fill a map. See [#19273](https://github.com/mastra-ai/mastra/issues/19273).
-
-- Fix supervisor agent tool schemas for Gemini via OpenRouter. Properties with no Gemini-compatible type — most commonly `z.any()`, which serializes to an empty schema — are now rewritten into a permissive `anyOf` instead of being dropped. This resolves the misleading `required[N]: property is not defined` error when using Gemini models through OpenRouter as a supervisor agent (fixes #17325), while keeping fields the model is expected to fill (such as `resumeData` for tool suspend/resume) present in the tool contract. ([#17386](https://github.com/mastra-ai/mastra/pull/17386))
-
-- Fixed Zod v3 schema conversion for CommonJS consumers. ([#21147](https://github.com/mastra-ai/mastra/pull/21147))
-
-- Fixed tool execute-time input validation for Zod tools on Anthropic Claude 3.5 Haiku. The compat layer now skips string min/max checks that were removed from the model-facing JSON Schema, while preserving refinements, defaults, and other validation semantics. ([#19701](https://github.com/mastra-ai/mastra/pull/19701))
-
-## 1.3.6-alpha.3
-
-### Patch Changes
-
-- Fixed Zod v3 schema conversion for CommonJS consumers. ([#21147](https://github.com/mastra-ai/mastra/pull/21147))
-
-## 1.3.6-alpha.2
-
-### Patch Changes
-
-- Fixed OpenAI structured output requests failing when a schema uses `z.record()`. The OpenAI compatibility layer now removes the `propertyNames` keyword, which OpenAI strict mode does not permit. Requests that used to fail with "Invalid schema ... 'propertyNames' is not permitted" are now accepted. ([#20977](https://github.com/mastra-ai/mastra/pull/20977))
-
-  **Known limitation.** OpenAI strict mode cannot express an open-ended map. A `z.record()` field is still sent as a plain object with no value schema, so the model is not told what keys or values to produce. Use an explicit `z.object({ ... })` shape when you need the model to fill a map. See [#19273](https://github.com/mastra-ai/mastra/issues/19273).
-
-## 1.3.6-alpha.1
-
-### Patch Changes
-
-- Fixed tool execute-time input validation for Zod tools on Anthropic Claude 3.5 Haiku. The compat layer now skips string min/max checks that were removed from the model-facing JSON Schema, while preserving refinements, defaults, and other validation semantics. ([#19701](https://github.com/mastra-ai/mastra/pull/19701))
-
-## 1.3.6-alpha.0
-
-### Patch Changes
-
-- Fix supervisor agent tool schemas for Gemini via OpenRouter. Properties with no Gemini-compatible type — most commonly `z.any()`, which serializes to an empty schema — are now rewritten into a permissive `anyOf` instead of being dropped. This resolves the misleading `required[N]: property is not defined` error when using Gemini models through OpenRouter as a supervisor agent (fixes #17325), while keeping fields the model is expected to fill (such as `resumeData` for tool suspend/resume) present in the tool contract. ([#17386](https://github.com/mastra-ai/mastra/pull/17386))
-
-## 1.3.5
-
-### Patch Changes
-
-- Fixed Claude requests failing when tool inputs use a top-level union of object schemas. ([#20724](https://github.com/mastra-ai/mastra/pull/20724))
-
-## 1.3.5-alpha.0
-
-### Patch Changes
-
-- Fixed Claude requests failing when tool inputs use a top-level union of object schemas. ([#20724](https://github.com/mastra-ai/mastra/pull/20724))
-
-## 1.3.4
-
-### Patch Changes
-
-- test(schema-compat): fix 'successful' typo in provider e2e test descriptions ([#19167](https://github.com/mastra-ai/mastra/pull/19167))
-
-- Fixed a crash when converting Zod v4 schemas containing `z.record(...)` through `applyCompatLayer` with any provider compat layer attached (e.g. `GoogleSchemaCompatLayer`, `OpenAISchemaCompatLayer`). ([#17052](https://github.com/mastra-ai/mastra/pull/17052))
-
-  The record patch is now applied in `toStandardSchema` before the `StandardSchemaWithJSON` short-circuit, so it covers Zod >= 4.2 (which natively exposes `~standard.jsonSchema` and bypasses the Zod v4 adapter) as well as older Zod v4 versions that go through the adapter. Affects Zod 4.0.0–4.3.x; the underlying `z.record()` bug is fixed upstream in Zod 4.4.0.
-
-  Fixes [#17051](https://github.com/mastra-ai/mastra/issues/17051).
-
-- Fixed Meta (Llama) and DeepSeek schemas leaking raw number bounds to the model. A field like `z.number().int()` was sent to the model with bogus `minimum: -9007199254740991` / `maximum: 9007199254740991` values, and `z.number().min(1).max(50)` leaked `minimum`/`maximum` keywords, even though OpenAI, Google, and Anthropic already strip these. Numeric constraints are now moved into the field description for Meta and DeepSeek too, matching the other providers. ([#19073](https://github.com/mastra-ai/mastra/pull/19073))
-
-  **Before** (Meta/DeepSeek, `z.object({ age: z.number().min(0).max(120) })`):
-
-  ```json
-  { "age": { "type": "number", "minimum": 0, "maximum": 120 } }
-  ```
-
-  **After**:
-
-  ```json
-  { "age": { "type": "number", "description": "constraints: greater than or equal to 0, lower than or equal to 120" } }
-  ```
-
-  Closes #19072.
-
-## 1.3.4-alpha.2
-
-### Patch Changes
-
-- Fixed a crash when converting Zod v4 schemas containing `z.record(...)` through `applyCompatLayer` with any provider compat layer attached (e.g. `GoogleSchemaCompatLayer`, `OpenAISchemaCompatLayer`). ([#17052](https://github.com/mastra-ai/mastra/pull/17052))
-
-  The record patch is now applied in `toStandardSchema` before the `StandardSchemaWithJSON` short-circuit, so it covers Zod >= 4.2 (which natively exposes `~standard.jsonSchema` and bypasses the Zod v4 adapter) as well as older Zod v4 versions that go through the adapter. Affects Zod 4.0.0–4.3.x; the underlying `z.record()` bug is fixed upstream in Zod 4.4.0.
-
-  Fixes [#17051](https://github.com/mastra-ai/mastra/issues/17051).
-
-## 1.3.4-alpha.1
-
-### Patch Changes
-
-- test(schema-compat): fix 'successful' typo in provider e2e test descriptions ([#19167](https://github.com/mastra-ai/mastra/pull/19167))
-
-## 1.3.4-alpha.0
-
-### Patch Changes
-
-- Fixed Meta (Llama) and DeepSeek schemas leaking raw number bounds to the model. A field like `z.number().int()` was sent to the model with bogus `minimum: -9007199254740991` / `maximum: 9007199254740991` values, and `z.number().min(1).max(50)` leaked `minimum`/`maximum` keywords, even though OpenAI, Google, and Anthropic already strip these. Numeric constraints are now moved into the field description for Meta and DeepSeek too, matching the other providers. ([#19073](https://github.com/mastra-ai/mastra/pull/19073))
-
-  **Before** (Meta/DeepSeek, `z.object({ age: z.number().min(0).max(120) })`):
-
-  ```json
-  { "age": { "type": "number", "minimum": 0, "maximum": 120 } }
-  ```
-
-  **After**:
-
-  ```json
-  { "age": { "type": "number", "description": "constraints: greater than or equal to 0, lower than or equal to 120" } }
-  ```
-
-  Closes #19072.
-
-## 1.3.3
-
-### Patch Changes
-
-- Fix the Zod v4 nullable and optional handlers gating on the wrapper type instead of the wrapped inner type. They checked `value.constructor.name` (always `"ZodNullable"`/`"ZodOptional"`), so the inner type was always processed. A nullable/optional wrapping an unsupported inner type (such as a tuple) is now passed through unchanged, matching the v3 handler, instead of being processed and rejected. Closes #18687. ([#18688](https://github.com/mastra-ai/mastra/pull/18688))
-
-## 1.3.3-alpha.0
-
-### Patch Changes
-
-- Fix the Zod v4 nullable and optional handlers gating on the wrapper type instead of the wrapped inner type. They checked `value.constructor.name` (always `"ZodNullable"`/`"ZodOptional"`), so the inner type was always processed. A nullable/optional wrapping an unsupported inner type (such as a tuple) is now passed through unchanged, matching the v3 handler, instead of being processed and rejected. Closes #18687. ([#18688](https://github.com/mastra-ai/mastra/pull/18688))
-
-## 1.3.2
-
-### Patch Changes
-
-- Fix the Zod v4 string handler silently dropping unrecognized `string_format` checks. Formats without a textual description (such as `ipv4`, `ipv6`, `datetime`, `date`, `time`, `base64`, `cuid2`, `ulid`, `nanoid`, `jwt`) are now preserved as validation instead of being removed, so schemas using them keep rejecting invalid input. Closes #18634. ([#18673](https://github.com/mastra-ai/mastra/pull/18673))
-
-- Fix inverted date constraint descriptions in the Zod v4 schema handler. `z.date().min()` and `z.date().max()` were described with their bounds swapped (a lower bound was labelled "older than" and an upper bound "newer than"), so the schema sent to the model stated the opposite and impossible constraint. The handler now matches Zod semantics and the existing v3 handler. Closes #18581. ([#18582](https://github.com/mastra-ai/mastra/pull/18582))
-
-- Fixed 'Type instantiation is excessively deep' (TS2589) errors that occurred when defining workflows with Zod schemas. Workflow and step type inference is now significantly faster and no longer causes TypeScript to crash or report depth errors. ([#18608](https://github.com/mastra-ai/mastra/pull/18608))
-
-## 1.3.2-alpha.1
-
-### Patch Changes
-
-- Fix the Zod v4 string handler silently dropping unrecognized `string_format` checks. Formats without a textual description (such as `ipv4`, `ipv6`, `datetime`, `date`, `time`, `base64`, `cuid2`, `ulid`, `nanoid`, `jwt`) are now preserved as validation instead of being removed, so schemas using them keep rejecting invalid input. Closes #18634. ([#18673](https://github.com/mastra-ai/mastra/pull/18673))
-
-## 1.3.2-alpha.0
-
-### Patch Changes
-
-- Fix inverted date constraint descriptions in the Zod v4 schema handler. `z.date().min()` and `z.date().max()` were described with their bounds swapped (a lower bound was labelled "older than" and an upper bound "newer than"), so the schema sent to the model stated the opposite and impossible constraint. The handler now matches Zod semantics and the existing v3 handler. Closes #18581. ([#18582](https://github.com/mastra-ai/mastra/pull/18582))
-
-- Fixed 'Type instantiation is excessively deep' (TS2589) errors that occurred when defining workflows with Zod schemas. Workflow and step type inference is now significantly faster and no longer causes TypeScript to crash or report depth errors. ([#18608](https://github.com/mastra-ai/mastra/pull/18608))
-
-## 1.3.1
-
-### Patch Changes
-
-- Fixed createTool type error when passing jsonSchema() or a Schema object from @ai-sdk/provider-utils as inputSchema — no more cast needed ([#17435](https://github.com/mastra-ai/mastra/pull/17435))
-
-## 1.3.1-alpha.0
-
-### Patch Changes
-
-- Fixed createTool type error when passing jsonSchema() or a Schema object from @ai-sdk/provider-utils as inputSchema — no more cast needed ([#17435](https://github.com/mastra-ai/mastra/pull/17435))
-
-## 1.3.0
-
-### Minor Changes
-
-- Random bump ([#18178](https://github.com/mastra-ai/mastra/pull/18178))
-
-## 1.3.0-alpha.0
-
-### Minor Changes
-
-- Random bump ([#18178](https://github.com/mastra-ai/mastra/pull/18178))
-
-## 1.2.14
-
-### Patch Changes
-
-- Security remediation for the 2026-06-17 "easy-day-js" supply-chain incident. Patch bump to publish clean versions and move the `latest` dist-tag forward, superseding the compromised versions that declared the malicious `easy-day-js` dependency. ([#18056](https://github.com/mastra-ai/mastra/pull/18056))
-
-## 1.2.14-alpha.0
-
-### Patch Changes
-
-- Security remediation for the 2026-06-17 "easy-day-js" supply-chain incident. Patch bump to publish clean versions and move the `latest` dist-tag forward, superseding the compromised versions that declared the malicious `easy-day-js` dependency. ([#18056](https://github.com/mastra-ai/mastra/pull/18056))
-
-## 1.2.12
-
-### Patch Changes
-
-- Fixed schema compatibility type declarations so JSON Schema types are bundled correctly. ([#17877](https://github.com/mastra-ai/mastra/pull/17877))
-
-## 1.2.11
-
-### Patch Changes
-
-- Fixed Gemini REST tool calls failing for `z.discriminatedUnion`, `z.lazy`, and `z.tuple` inputs. `GoogleSchemaCompatLayer` now rewrites JSON Schema 2020-12 keywords into the OpenAPI 3.0 Schema Object subset that Gemini expects: `oneOf` → `anyOf`, `const` → `enum`, tuple `items: [array]` → `items: { anyOf: [...] }`, nullable `anyOf` collapse, `$ref` inlining with recursive schema support, and stripping of `$schema`/`additionalProperties`/`propertyNames`. Fixes #17057. ([#17179](https://github.com/mastra-ai/mastra/pull/17179))
-
-- Fixed Zod 4 schemas with `.transform()` producing the wrong JSON Schema for structured output and tool calling. The generated schema now describes the pre-transform input the model must produce instead of the post-transform output, so a field like `z.string().transform(JSON.parse)` is advertised as a `string` rather than `string | number | boolean | null`. ([#17357](https://github.com/mastra-ai/mastra/pull/17357))
-
-## 1.2.11-alpha.0
-
-### Patch Changes
-
-- Fixed Gemini REST tool calls failing for `z.discriminatedUnion`, `z.lazy`, and `z.tuple` inputs. `GoogleSchemaCompatLayer` now rewrites JSON Schema 2020-12 keywords into the OpenAPI 3.0 Schema Object subset that Gemini expects: `oneOf` → `anyOf`, `const` → `enum`, tuple `items: [array]` → `items: { anyOf: [...] }`, nullable `anyOf` collapse, `$ref` inlining with recursive schema support, and stripping of `$schema`/`additionalProperties`/`propertyNames`. Fixes #17057. ([#17179](https://github.com/mastra-ai/mastra/pull/17179))
-
-- Fixed Zod 4 schemas with `.transform()` producing the wrong JSON Schema for structured output and tool calling. The generated schema now describes the pre-transform input the model must produce instead of the post-transform output, so a field like `z.string().transform(JSON.parse)` is advertised as a `string` rather than `string | number | boolean | null`. ([#17357](https://github.com/mastra-ai/mastra/pull/17357))
-
-## 1.2.10
-
-### Patch Changes
-
-- Fixed Google-compatible schema conversion so Gemini accepts broad nullable tool parameters. ([#16129](https://github.com/mastra-ai/mastra/pull/16129))
-
-## 1.2.10-alpha.0
-
-### Patch Changes
-
-- Fixed Google-compatible schema conversion so Gemini accepts broad nullable tool parameters. ([#16129](https://github.com/mastra-ai/mastra/pull/16129))
-
-## 1.2.9
-
-### Patch Changes
-
-- Fixed MCP tool validation failures when tools use JSON Schema draft 2020-12. Tools from providers like Firecrawl that declare `$schema: "https://json-schema.org/draft/2020-12/schema"` now validate correctly instead of throwing "no schema with key or ref" errors. ([#14530](https://github.com/mastra-ai/mastra/pull/14530))
-
-- Fixed MCP tools with recursive JSON Schema refs so they stay serializable when loaded. ([#15400](https://github.com/mastra-ai/mastra/pull/15400))
-
-## 1.2.9-alpha.1
-
-### Patch Changes
-
-- Fixed MCP tool validation failures when tools use JSON Schema draft 2020-12. Tools from providers like Firecrawl that declare `$schema: "https://json-schema.org/draft/2020-12/schema"` now validate correctly instead of throwing "no schema with key or ref" errors. ([#14530](https://github.com/mastra-ai/mastra/pull/14530))
-
-## 1.2.9-alpha.0
-
-### Patch Changes
-
-- Fixed MCP tools with recursive JSON Schema refs so they stay serializable when loaded. ([#15400](https://github.com/mastra-ai/mastra/pull/15400))
-
-## 1.2.8
-
-### Patch Changes
-
-- --- ([#14624](https://github.com/mastra-ai/mastra/pull/14624))
-  `@mastra/schema-compat`: patch
-
-  ***
-
-  Improved provider schema compatibility for structured outputs and tool calls.
-  Fixed validation for optional, nullable, and defaulted fields, and for ISO date strings returned for date fields.
-
-## 1.2.8-alpha.0
-
-### Patch Changes
-
-- --- ([#14624](https://github.com/mastra-ai/mastra/pull/14624))
-  `@mastra/schema-compat`: patch
-
-  ***
-
-  Improved provider schema compatibility for structured outputs and tool calls.
-  Fixed validation for optional, nullable, and defaulted fields, and for ISO date strings returned for date fields.
-
-## 1.2.7
-
-### Patch Changes
-
-- Fixed schema-compat ESM imports for Zod JSON Schema helpers. ([#14617](https://github.com/mastra-ai/mastra/pull/14617))
-
-  @mastra/schema-compat no longer uses createRequire in its Zod v4 adapter or runtime eval tests, which avoids createRequire-related ESM issues while preserving support for zod/v3 and zod/v4.
-
-- Fix Zod v3 and Zod v4 compatibility across public structured-output APIs. ([#14464](https://github.com/mastra-ai/mastra/pull/14464))
-
-  Mastra agent and client APIs accept schemas from either `zod/v3` or `zod/v4`, matching the documented peer dependency range and preserving TypeScript compatibility for both Zod versions.
-
-## 1.2.7-alpha.1
-
-### Patch Changes
-
-- Fixed schema-compat ESM imports for Zod JSON Schema helpers. ([#14617](https://github.com/mastra-ai/mastra/pull/14617))
-
-  @mastra/schema-compat no longer uses createRequire in its Zod v4 adapter or runtime eval tests, which avoids createRequire-related ESM issues while preserving support for zod/v3 and zod/v4.
-
-## 1.2.7-alpha.0
-
-### Patch Changes
-
-- Fix Zod v3 and Zod v4 compatibility across public structured-output APIs. ([#14464](https://github.com/mastra-ai/mastra/pull/14464))
-
-  Mastra agent and client APIs accept schemas from either `zod/v3` or `zod/v4`, matching the documented peer dependency range and preserving TypeScript compatibility for both Zod versions.
-
-## 1.2.6
-
-### Patch Changes
-
-- fix(schema-compat): map Mastra draft target names to Zod v4 format ([#14401](https://github.com/mastra-ai/mastra/pull/14401))
-
-  Zod v4's `z.toJSONSchema()` expects `"draft-7"` / `"draft-4"` while
-  Mastra uses `"draft-07"` / `"draft-04"`. The mismatch caused repeated
-  `Invalid target: draft-07` console warnings and suppressed the `$schema`
-  field in generated JSON Schemas.
-
-  Adds `ZOD_V4_TARGET_MAP` in the zod-v4 adapter to translate target names
-  before calling `z.toJSONSchema()`. `"draft-2020-12"` is unchanged as both
-  sides already agree on that name.
-
-  Fixes `#14399`
-
-- Add support for `draft-2020-12` and `draft-04` JSON Schema targets in the Zod v3 adapter, and fix the `toJSONSchema` target mapping to properly translate all `zod-to-json-schema` target names (like `openApi3`) to standard-schema target names. Fixes "Unsupported JSON Schema target" errors when serializing tool schemas. ([#14471](https://github.com/mastra-ai/mastra/pull/14471))
-
-## 1.2.6-alpha.1
-
-### Patch Changes
-
-- Add support for `draft-2020-12` and `draft-04` JSON Schema targets in the Zod v3 adapter, and fix the `toJSONSchema` target mapping to properly translate all `zod-to-json-schema` target names (like `openApi3`) to standard-schema target names. Fixes "Unsupported JSON Schema target" errors when serializing tool schemas. ([#14471](https://github.com/mastra-ai/mastra/pull/14471))
-
-## 1.2.6-alpha.0
-
-### Patch Changes
-
-- fix(schema-compat): map Mastra draft target names to Zod v4 format ([#14401](https://github.com/mastra-ai/mastra/pull/14401))
-
-  Zod v4's `z.toJSONSchema()` expects `"draft-7"` / `"draft-4"` while
-  Mastra uses `"draft-07"` / `"draft-04"`. The mismatch caused repeated
-  `Invalid target: draft-07` console warnings and suppressed the `$schema`
-  field in generated JSON Schemas.
-
-  Adds `ZOD_V4_TARGET_MAP` in the zod-v4 adapter to translate target names
-  before calling `z.toJSONSchema()`. `"draft-2020-12"` is unchanged as both
-  sides already agree on that name.
-
-  Fixes `#14399`
-
-## 1.2.5
-
-### Patch Changes
-
-- Added ZodIntersection support so that MCP tools using allOf in their JSON Schema no longer throw 'does not support zod type: ZodIntersection'. Intersection types are flattened and merged into a single object schema across all provider compatibility layers (Anthropic, Google, OpenAI, OpenAI Reasoning, DeepSeek, Meta). ([#14255](https://github.com/mastra-ai/mastra/pull/14255))
-
-## 1.2.5-alpha.0
-
-### Patch Changes
-
-- Added ZodIntersection support so that MCP tools using allOf in their JSON Schema no longer throw 'does not support zod type: ZodIntersection'. Intersection types are flattened and merged into a single object schema across all provider compatibility layers (Anthropic, Google, OpenAI, OpenAI Reasoning, DeepSeek, Meta). ([#14255](https://github.com/mastra-ai/mastra/pull/14255))
-
-## 1.2.4
-
-### Patch Changes
-
-- Lazily load createRequire to fix 'Uncaught (in promise) TypeError: lzt.createRequire is not a function' error ([#14275](https://github.com/mastra-ai/mastra/pull/14275))
-
-## 1.2.4-alpha.0
-
-### Patch Changes
-
-- Lazily load createRequire to fix 'Uncaught (in promise) TypeError: lzt.createRequire is not a function' error ([#14275](https://github.com/mastra-ai/mastra/pull/14275))
-
-## 1.2.3
-
-### Patch Changes
-
-- Fixed "Dynamic require of zod/v4 is not supported" error when schema-compat is consumed by ESM bundles (e.g. via npx mastracode). The dynamic require fallback was incorrectly selecting esbuild's require shim instead of Node.js createRequire. ([#14268](https://github.com/mastra-ai/mastra/pull/14268))
-
-## 1.2.2
-
-### Patch Changes
-
-- `@mastra/schema-compat`: patch ([#14195](https://github.com/mastra-ai/mastra/pull/14195))
-
-  Fixed published `@mastra/schema-compat` types so AI SDK v5 schemas resolve correctly for consumers
-
-- Fixed false `z.toJSONSchema is not available` errors for compatible Zod versions. ([#14264](https://github.com/mastra-ai/mastra/pull/14264))
-
-  **What changed**
-  - Improved Zod schema conversion detection so JSON Schema generation works more reliably across different runtime setups.
-
-## 1.2.2-alpha.0
-
-### Patch Changes
-
-- `@mastra/schema-compat`: patch ([#14195](https://github.com/mastra-ai/mastra/pull/14195))
-
-  Fixed published `@mastra/schema-compat` types so AI SDK v5 schemas resolve correctly for consumers
-
-- Fixed false `z.toJSONSchema is not available` errors for compatible Zod versions. ([#14264](https://github.com/mastra-ai/mastra/pull/14264))
-
-  **What changed**
-  - Improved Zod schema conversion detection so JSON Schema generation works more reliably across different runtime setups.
-
-## 1.2.1
-
-### Patch Changes
-
-- dependencies updates: ([#14119](https://github.com/mastra-ai/mastra/pull/14119))
-  - Updated dependency [`zod-from-json-schema@^0.5.2` ↗︎](https://www.npmjs.com/package/zod-from-json-schema/v/0.5.2) (from `^0.5.0`, in `dependencies`)
-
-- Fixed Zod v4 schema conversion when `zod/v4` compat layer from Zod 3.25.x is used. Schemas like `ask_user` and other harness tools were not being properly converted to JSON Schema when `~standard.jsonSchema` was absent, causing `type: "None"` errors from the Anthropic API. ([#14157](https://github.com/mastra-ai/mastra/pull/14157))
-
-## 1.2.1-alpha.1
-
-### Patch Changes
-
-- dependencies updates: ([#14119](https://github.com/mastra-ai/mastra/pull/14119))
-  - Updated dependency [`zod-from-json-schema@^0.5.2` ↗︎](https://www.npmjs.com/package/zod-from-json-schema/v/0.5.2) (from `^0.5.0`, in `dependencies`)
-
-## 1.2.1-alpha.0
-
-### Patch Changes
-
-- Fixed Zod v4 schema conversion when `zod/v4` compat layer from Zod 3.25.x is used. Schemas like `ask_user` and other harness tools were not being properly converted to JSON Schema when `~standard.jsonSchema` was absent, causing `type: "None"` errors from the Anthropic API. ([#14157](https://github.com/mastra-ai/mastra/pull/14157))
-
-## 1.2.0
-
-### Minor Changes
-
-- Add Zod v4 and Standard Schema support ([#12238](https://github.com/mastra-ai/mastra/pull/12238))
-
-  ## Zod v4 Breaking Changes
-  - Fix all `z.record()` calls to use 2-argument form (key + value schema) as required by Zod v4
-  - Update `ZodError.errors` to `ZodError.issues` (Zod v4 API change)
-  - Update `@ai-sdk/provider` versions for Zod v4 compatibility
-
-  ## Standard Schema Integration
-  - Add `packages/core/src/schema/` module that re-exports from `@mastra/schema-compat`
-  - Migrate codebase to use `PublicSchema` type for schema parameters
-  - Use `toStandardSchema()` for normalizing schemas across Zod v3, Zod v4, AI SDK Schema, and JSON Schema
-  - Use `standardSchemaToJSONSchema()` for JSON Schema conversion
-
-  ## Schema Compatibility (@mastra/schema-compat)
-  - Add new adapter exports: `@mastra/schema-compat/adapters/ai-sdk`, `@mastra/schema-compat/adapters/zod-v3`, `@mastra/schema-compat/adapters/json-schema`
-  - Enhance test coverage with separate v3 and v4 test suites
-  - Improve zod-to-json conversion with `unrepresentable: 'any'` support
-
-  ## TypeScript Fixes
-  - Resolve deep instantiation errors in client-js and model.ts
-  - Add proper type assertions where Zod v4 inference differs
-
-  **BREAKING CHANGE**: Minimum Zod version is now `^3.25.0` for v3 compatibility or `^4.0.0` for v4
-
-### Patch Changes
-
-- Fixed Gemini supervisor agent tool calls failing with `INVALID_ARGUMENT` when delegated tool schemas include nullable fields. Fixes `#13988`. ([#14012](https://github.com/mastra-ai/mastra/pull/14012))
-
-- Fixed OpenAI and OpenAI Reasoning compat layers to ensure all properties appear in the JSON Schema required array when using processToJSONSchema. This prevents OpenAI strict mode rejections for schemas with optional, default, or nullish fields. (Fixes #12284) ([#13695](https://github.com/mastra-ai/mastra/pull/13695))
-
-## 1.2.0-alpha.0
-
-### Minor Changes
-
-- Add Zod v4 and Standard Schema support ([#12238](https://github.com/mastra-ai/mastra/pull/12238))
-
-  ## Zod v4 Breaking Changes
-  - Fix all `z.record()` calls to use 2-argument form (key + value schema) as required by Zod v4
-  - Update `ZodError.errors` to `ZodError.issues` (Zod v4 API change)
-  - Update `@ai-sdk/provider` versions for Zod v4 compatibility
-
-  ## Standard Schema Integration
-  - Add `packages/core/src/schema/` module that re-exports from `@mastra/schema-compat`
-  - Migrate codebase to use `PublicSchema` type for schema parameters
-  - Use `toStandardSchema()` for normalizing schemas across Zod v3, Zod v4, AI SDK Schema, and JSON Schema
-  - Use `standardSchemaToJSONSchema()` for JSON Schema conversion
-
-  ## Schema Compatibility (@mastra/schema-compat)
-  - Add new adapter exports: `@mastra/schema-compat/adapters/ai-sdk`, `@mastra/schema-compat/adapters/zod-v3`, `@mastra/schema-compat/adapters/json-schema`
-  - Enhance test coverage with separate v3 and v4 test suites
-  - Improve zod-to-json conversion with `unrepresentable: 'any'` support
-
-  ## TypeScript Fixes
-  - Resolve deep instantiation errors in client-js and model.ts
-  - Add proper type assertions where Zod v4 inference differs
-
-  **BREAKING CHANGE**: Minimum Zod version is now `^3.25.0` for v3 compatibility or `^4.0.0` for v4
-
-### Patch Changes
-
-- Fixed Gemini supervisor agent tool calls failing with `INVALID_ARGUMENT` when delegated tool schemas include nullable fields. Fixes `#13988`. ([#14012](https://github.com/mastra-ai/mastra/pull/14012))
-
-- Fixed OpenAI and OpenAI Reasoning compat layers to ensure all properties appear in the JSON Schema required array when using processToJSONSchema. This prevents OpenAI strict mode rejections for schemas with optional, default, or nullish fields. (Fixes #12284) ([#13695](https://github.com/mastra-ai/mastra/pull/13695))
-
-## 1.1.3
-
-### Patch Changes
-
-- Fix `ZodNull` throwing "does not support zod type: ZodNull" for Anthropic and OpenAI reasoning models. MCP tools with nullable properties in their JSON Schema produce `z.null()` which was unhandled by these provider compat layers. ([#13496](https://github.com/mastra-ai/mastra/pull/13496))
-
-## 1.1.3-alpha.0
-
-### Patch Changes
-
-- Fix `ZodNull` throwing "does not support zod type: ZodNull" for Anthropic and OpenAI reasoning models. MCP tools with nullable properties in their JSON Schema produce `z.null()` which was unhandled by these provider compat layers. ([#13496](https://github.com/mastra-ai/mastra/pull/13496))
-
-## 1.1.2
-
-### Patch Changes
-
-- Fixed Groq provider not receiving schema compatibility transformations, which caused HTTP 400 errors when AI models omitted optional parameters from workspace tool calls (e.g. list_files). Groq now correctly gets the same optional-to-nullable schema handling as OpenAI. ([#13303](https://github.com/mastra-ai/mastra/pull/13303))
-
-## 1.1.2-alpha.0
-
-### Patch Changes
-
-- Fixed Groq provider not receiving schema compatibility transformations, which caused HTTP 400 errors when AI models omitted optional parameters from workspace tool calls (e.g. list_files). Groq now correctly gets the same optional-to-nullable schema handling as OpenAI. ([#13303](https://github.com/mastra-ai/mastra/pull/13303))
-
-## 1.1.1
-
-### Patch Changes
-
-- fix(schema-compat): fix zodToJsonSchema routing for v3/v4 Zod schemas ([#13253](https://github.com/mastra-ai/mastra/pull/13253))
-
-  The `zodToJsonSchema` function now reliably detects and routes Zod v3 vs v4 schemas regardless of which version the ambient `zod` import resolves to. Previously, the detection relied on checking `'toJSONSchema' in z` against the ambient `z` import, which could resolve to either v3 or v4 depending on the environment (monorepo vs global install). This caused v3 schemas to be passed to v4's `toJSONSchema()` (crashing with "Cannot read properties of undefined (reading 'def')") or v4 schemas to be passed to the v3 converter (producing schemas missing the `type` field).
-
-  The fix explicitly imports `z as zV4` from `zod/v4` and routes based on the schema's own `_zod` property, making the behavior environment-independent.
-
-  Also migrates all mastracode tool files from `zod/v3` to `zod` imports now that the schema-compat fix supports both versions correctly.
-
-## 1.1.1-alpha.0
-
-### Patch Changes
-
-- fix(schema-compat): fix zodToJsonSchema routing for v3/v4 Zod schemas ([#13253](https://github.com/mastra-ai/mastra/pull/13253))
-
-  The `zodToJsonSchema` function now reliably detects and routes Zod v3 vs v4 schemas regardless of which version the ambient `zod` import resolves to. Previously, the detection relied on checking `'toJSONSchema' in z` against the ambient `z` import, which could resolve to either v3 or v4 depending on the environment (monorepo vs global install). This caused v3 schemas to be passed to v4's `toJSONSchema()` (crashing with "Cannot read properties of undefined (reading 'def')") or v4 schemas to be passed to the v3 converter (producing schemas missing the `type` field).
-
-  The fix explicitly imports `z as zV4` from `zod/v4` and routes based on the schema's own `_zod` property, making the behavior environment-independent.
-
-  Also migrates all mastracode tool files from `zod/v3` to `zod` imports now that the schema-compat fix supports both versions correctly.
-
-## 1.1.0
-
-### Minor Changes
-
-- Added [Standard Schema](https://github.com/standard-schema/standard-schema) support to `@mastra/schema-compat`. This enables interoperability with any schema library that implements the Standard Schema specification. ([#12527](https://github.com/mastra-ai/mastra/pull/12527))
-
-  **New exports:**
-  - `toStandardSchema()` - Convert Zod, JSON Schema, or AI SDK schemas to Standard Schema format
-  - `StandardSchemaWithJSON` - Type for schemas implementing both validation and JSON Schema conversion
-  - `InferInput`, `InferOutput` - Utility types for type inference
-
-  **Example usage:**
-
-  ```typescript
-  import { toStandardSchema } from '@mastra/schema-compat/schema';
-  import { z } from 'zod';
-
-  // Convert a Zod schema to Standard Schema
-  const zodSchema = z.object({ name: z.string(), age: z.number() });
-  const standardSchema = toStandardSchema(zodSchema);
-
-  // Use validation
-  const result = standardSchema['~standard'].validate({ name: 'John', age: 30 });
-
-  // Get JSON Schema
-  const jsonSchema = standardSchema['~standard'].jsonSchema.output({ target: 'draft-07' });
-  ```
-
-## 1.1.0-alpha.0
-
-### Minor Changes
-
-- Added [Standard Schema](https://github.com/standard-schema/standard-schema) support to `@mastra/schema-compat`. This enables interoperability with any schema library that implements the Standard Schema specification. ([#12527](https://github.com/mastra-ai/mastra/pull/12527))
-
-  **New exports:**
-  - `toStandardSchema()` - Convert Zod, JSON Schema, or AI SDK schemas to Standard Schema format
-  - `StandardSchemaWithJSON` - Type for schemas implementing both validation and JSON Schema conversion
-  - `InferInput`, `InferOutput` - Utility types for type inference
-
-  **Example usage:**
-
-  ```typescript
-  import { toStandardSchema } from '@mastra/schema-compat/schema';
-  import { z } from 'zod';
-
-  // Convert a Zod schema to Standard Schema
-  const zodSchema = z.object({ name: z.string(), age: z.number() });
-  const standardSchema = toStandardSchema(zodSchema);
-
-  // Use validation
-  const result = standardSchema['~standard'].validate({ name: 'John', age: 30 });
-
-  // Get JSON Schema
-  const jsonSchema = standardSchema['~standard'].jsonSchema.output({ target: 'draft-07' });
-  ```
-
-## 1.0.0
-
-### Major Changes
-
-- Bump minimum required Node.js version to 22.13.0 ([#9706](https://github.com/mastra-ai/mastra/pull/9706))
-
-- Mark as stable ([`83d5942`](https://github.com/mastra-ai/mastra/commit/83d5942669ce7bba4a6ca4fd4da697a10eb5ebdc))
-
-### Patch Changes
-
-- Fix Zod v4 toJSONSchema bug with z.record() single-argument form ([#9265](https://github.com/mastra-ai/mastra/pull/9265))
-
-  Zod v4 has a bug in the single-argument form of `z.record(valueSchema)` where it incorrectly assigns the value schema to `keyType` instead of `valueType`, leaving `valueType` undefined. This causes `toJSONSchema()` to throw "Cannot read properties of undefined (reading '\_zod')" when processing schemas containing `z.record()` fields.
-
-  This fix patches affected schemas before conversion by detecting records with missing `valueType` and correctly assigning the schema to `valueType` while setting `keyType` to `z.string()` (the default). The patch recursively handles nested schemas including those wrapped in `.optional()`, `.nullable()`, arrays, unions, and objects.
-
-- Embed AI types to fix peerdeps mismatches ([`9650cce`](https://github.com/mastra-ai/mastra/commit/9650cce52a1d917ff9114653398e2a0f5c3ba808))
-
-- Fixed agent network mode failing with "Cannot read properties of undefined" error when tools or workflows don't have an `inputSchema` defined. ([#12063](https://github.com/mastra-ai/mastra/pull/12063))
-  - **@mastra/core:** Fixed `getRoutingAgent()` to handle tools and workflows without `inputSchema` by providing a default empty schema fallback.
-  - **@mastra/schema-compat:** Fixed Zod v4 optional/nullable fields producing invalid JSON schema for OpenAI structured outputs. OpenAI now correctly receives `type: ["string", "null"]` instead of `anyOf` patterns that were rejected with "must have a 'type' key" error.
-
-- Fixed OpenAI schema validation error when using passthrough schemas with tools like `vectorQueryTool`. ([#11846](https://github.com/mastra-ai/mastra/pull/11846))
-
-  **What was happening:** Tools using `.passthrough()` or `z.looseObject()` schemas (like the RAG `vectorQueryTool`) would fail with OpenAI models, returning the error: "Invalid schema for function: In context=('additionalProperties',), schema must have a 'type' key."
-
-  **What changed:** The OpenAI schema compatibility layer now converts passthrough schemas to strict object schemas, producing valid `additionalProperties: false` instead of the invalid empty object `{}` that Zod v4 generates.
-
-  Fixes #11823
-
-- Fixed "Transforms cannot be represented in JSON Schema" error when using Zod v4 with structuredOutput ([#11466](https://github.com/mastra-ai/mastra/pull/11466))
-
-  When using schemas with `.optional()`, `.nullable()`, `.default()`, or `.nullish().default("")` patterns with `structuredOutput` and Zod v4, users would encounter an error because OpenAI schema compatibility layer adds transforms that Zod v4's native `toJSONSchema()` cannot handle.
-
-  The fix uses Mastra's transform-safe `zodToJsonSchema` function which gracefully handles transforms by using the `unrepresentable: 'any'` option.
-
-  Also exported `isZodType` utility from `@mastra/schema-compat` and updated it to detect both Zod v3 (`_def`) and Zod v4 (`_zod`) schemas.
-
-- Improved reliability of string field types in tool schema compatibility ([#9266](https://github.com/mastra-ai/mastra/pull/9266))
-
-- Fix OpenAI structured output compatibility for fields with `.default()` values ([#11434](https://github.com/mastra-ai/mastra/pull/11434))
-
-  When using Zod schemas with `.default()` fields (e.g., `z.number().default(1)`), OpenAI's structured output API was failing with errors like `Missing '<field>' in required`. This happened because `zod-to-json-schema` doesn't include fields with defaults in the `required` array, but OpenAI requires all properties to be required.
-
-  This fix converts `.default()` fields to `.nullable()` with a transform that returns the default value when `null` is received, ensuring compatibility with OpenAI's strict mode while preserving the original default value semantics.
-
-- fix(schema-compat): handle undefined values in optional fields for OpenAI compat layers ([#11469](https://github.com/mastra-ai/mastra/pull/11469))
-
-  When a Zod schema has nested objects with `.partial()`, the optional fields would fail validation with "expected string, received undefined" errors. This occurred because the OpenAI schema compat layer converted `.optional()` to `.nullable()`, which only accepts `null` values, not `undefined`.
-
-  Changed `.nullable()` to `.nullish()` so that optional fields now accept both `null` (when explicitly provided by the LLM) and `undefined` (when fields are omitted entirely).
-
-  Fixes #11457
-
-- Fix discriminatedUnion schema information lost when json schema is converted to zod ([#10500](https://github.com/mastra-ai/mastra/pull/10500))
-
-- Fix oneOf schema conversion generating invalid JavaScript ([#11626](https://github.com/mastra-ai/mastra/pull/11626))
-
-  The upstream json-schema-to-zod library generates TypeScript syntax (`reduce<z.ZodError[]>`) when converting oneOf schemas. This TypeScript generic annotation fails when evaluated at runtime with Function(), causing schema resolution to fail.
-
-  The fix removes TypeScript generic syntax from the generated output, producing valid JavaScript that can be evaluated at runtime. This resolves issues where MCP tools with oneOf in their output schemas would fail validation.
-
-- Fixed OpenAI schema compatibility when using `agent.generate()` or `agent.stream()` with `structuredOutput`. ([#10366](https://github.com/mastra-ai/mastra/pull/10366))
-
-  **Changes**
-  - **Automatic transformation**: Zod schemas are now automatically transformed for OpenAI strict mode compatibility when using OpenAI models (including reasoning models like o1, o3, o4)
-  - **Optional field handling**: `.optional()` fields are converted to `.nullable()` with a transform that converts `null` → `undefined`, preserving optional semantics while satisfying OpenAI's strict mode requirements
-  - **Preserves nullable fields**: Intentionally `.nullable()` fields remain unchanged
-  - **Deep transformation**: Handles `.optional()` fields at any nesting level (objects, arrays, unions, etc.)
-  - **JSON Schema objects**: Not transformed, only Zod schemas
-
-  **Example**
-
-  ```typescript
-  const agent = new Agent({
-    name: 'data-extractor',
-    model: { provider: 'openai', modelId: 'gpt-4o' },
-    instructions: 'Extract user information',
-  });
-
-  const schema = z.object({
-    name: z.string(),
-    age: z.number().optional(),
-    deletedAt: z.date().nullable(),
-  });
-
-  // Schema is automatically transformed for OpenAI compatibility
-  const result = await agent.generate('Extract: John, deleted yesterday', {
-    structuredOutput: { schema },
-  });
-
-  // Result: { name: 'John', age: undefined, deletedAt: null }
-  ```
-
-## 1.0.0-beta.8
-
-### Patch Changes
-
-- Fixed agent network mode failing with "Cannot read properties of undefined" error when tools or workflows don't have an `inputSchema` defined. ([#12063](https://github.com/mastra-ai/mastra/pull/12063))
-  - **@mastra/core:** Fixed `getRoutingAgent()` to handle tools and workflows without `inputSchema` by providing a default empty schema fallback.
-  - **@mastra/schema-compat:** Fixed Zod v4 optional/nullable fields producing invalid JSON schema for OpenAI structured outputs. OpenAI now correctly receives `type: ["string", "null"]` instead of `anyOf` patterns that were rejected with "must have a 'type' key" error.
-
-## 1.0.0-beta.7
-
-### Patch Changes
-
-- Fixed OpenAI schema validation error when using passthrough schemas with tools like `vectorQueryTool`. ([#11846](https://github.com/mastra-ai/mastra/pull/11846))
-
-  **What was happening:** Tools using `.passthrough()` or `z.looseObject()` schemas (like the RAG `vectorQueryTool`) would fail with OpenAI models, returning the error: "Invalid schema for function: In context=('additionalProperties',), schema must have a 'type' key."
-
-  **What changed:** The OpenAI schema compatibility layer now converts passthrough schemas to strict object schemas, producing valid `additionalProperties: false` instead of the invalid empty object `{}` that Zod v4 generates.
-
-  Fixes #11823
-
-## 1.0.0-beta.6
-
-### Patch Changes
-
-- Fix oneOf schema conversion generating invalid JavaScript ([#11626](https://github.com/mastra-ai/mastra/pull/11626))
-
-  The upstream json-schema-to-zod library generates TypeScript syntax (`reduce<z.ZodError[]>`) when converting oneOf schemas. This TypeScript generic annotation fails when evaluated at runtime with Function(), causing schema resolution to fail.
-
-  The fix removes TypeScript generic syntax from the generated output, producing valid JavaScript that can be evaluated at runtime. This resolves issues where MCP tools with oneOf in their output schemas would fail validation.
-
-## 1.0.0-beta.5
-
-### Patch Changes
-
-- Fixed "Transforms cannot be represented in JSON Schema" error when using Zod v4 with structuredOutput ([#11466](https://github.com/mastra-ai/mastra/pull/11466))
-
-  When using schemas with `.optional()`, `.nullable()`, `.default()`, or `.nullish().default("")` patterns with `structuredOutput` and Zod v4, users would encounter an error because OpenAI schema compatibility layer adds transforms that Zod v4's native `toJSONSchema()` cannot handle.
-
-  The fix uses Mastra's transform-safe `zodToJsonSchema` function which gracefully handles transforms by using the `unrepresentable: 'any'` option.
-
-  Also exported `isZodType` utility from `@mastra/schema-compat` and updated it to detect both Zod v3 (`_def`) and Zod v4 (`_zod`) schemas.
-
-- fix(schema-compat): handle undefined values in optional fields for OpenAI compat layers ([#11469](https://github.com/mastra-ai/mastra/pull/11469))
-
-  When a Zod schema has nested objects with `.partial()`, the optional fields would fail validation with "expected string, received undefined" errors. This occurred because the OpenAI schema compat layer converted `.optional()` to `.nullable()`, which only accepts `null` values, not `undefined`.
-
-  Changed `.nullable()` to `.nullish()` so that optional fields now accept both `null` (when explicitly provided by the LLM) and `undefined` (when fields are omitted entirely).
-
-  Fixes #11457
-
-## 1.0.0-beta.4
-
-### Patch Changes
-
-- Fix OpenAI structured output compatibility for fields with `.default()` values ([#11434](https://github.com/mastra-ai/mastra/pull/11434))
-
-  When using Zod schemas with `.default()` fields (e.g., `z.number().default(1)`), OpenAI's structured output API was failing with errors like `Missing '<field>' in required`. This happened because `zod-to-json-schema` doesn't include fields with defaults in the `required` array, but OpenAI requires all properties to be required.
-
-  This fix converts `.default()` fields to `.nullable()` with a transform that returns the default value when `null` is received, ensuring compatibility with OpenAI's strict mode while preserving the original default value semantics.
-
-## 1.0.0-beta.3
-
-### Patch Changes
-
-- Embed AI types to fix peerdeps mismatches ([`9650cce`](https://github.com/mastra-ai/mastra/commit/9650cce52a1d917ff9114653398e2a0f5c3ba808))
-
-## 1.0.0-beta.2
-
-### Patch Changes
-
-- Fix discriminatedUnion schema information lost when json schema is converted to zod ([#10500](https://github.com/mastra-ai/mastra/pull/10500))
-
-## 1.0.0-beta.1
-
-### Patch Changes
-
-- Fixed OpenAI schema compatibility when using `agent.generate()` or `agent.stream()` with `structuredOutput`. ([#10366](https://github.com/mastra-ai/mastra/pull/10366))
-
-  ## Changes
-  - **Automatic transformation**: Zod schemas are now automatically transformed for OpenAI strict mode compatibility when using OpenAI models (including reasoning models like o1, o3, o4)
-  - **Optional field handling**: `.optional()` fields are converted to `.nullable()` with a transform that converts `null` → `undefined`, preserving optional semantics while satisfying OpenAI's strict mode requirements
-  - **Preserves nullable fields**: Intentionally `.nullable()` fields remain unchanged
-  - **Deep transformation**: Handles `.optional()` fields at any nesting level (objects, arrays, unions, etc.)
-  - **JSON Schema objects**: Not transformed, only Zod schemas
-
-  ## Example
-
-  ```typescript
-  const agent = new Agent({
-    name: 'data-extractor',
-    model: { provider: 'openai', modelId: 'gpt-4o' },
-    instructions: 'Extract user information',
-  });
-
-  const schema = z.object({
-    name: z.string(),
-    age: z.number().optional(),
-    deletedAt: z.date().nullable(),
-  });
-
-  // Schema is automatically transformed for OpenAI compatibility
-  const result = await agent.generate('Extract: John, deleted yesterday', {
-    structuredOutput: { schema },
-  });
-
-  // Result: { name: 'John', age: undefined, deletedAt: null }
-  ```
-
-## 1.0.0-beta.0
-
-### Major Changes
-
-- Bump minimum required Node.js version to 22.13.0 ([#9706](https://github.com/mastra-ai/mastra/pull/9706))
-
-- Mark as stable ([`83d5942`](https://github.com/mastra-ai/mastra/commit/83d5942669ce7bba4a6ca4fd4da697a10eb5ebdc))
-
-### Patch Changes
-
-- Fix Zod v4 toJSONSchema bug with z.record() single-argument form ([#9265](https://github.com/mastra-ai/mastra/pull/9265))
-
-  Zod v4 has a bug in the single-argument form of `z.record(valueSchema)` where it incorrectly assigns the value schema to `keyType` instead of `valueType`, leaving `valueType` undefined. This causes `toJSONSchema()` to throw "Cannot read properties of undefined (reading '\_zod')" when processing schemas containing `z.record()` fields.
-
-  This fix patches affected schemas before conversion by detecting records with missing `valueType` and correctly assigning the schema to `valueType` while setting `keyType` to `z.string()` (the default). The patch recursively handles nested schemas including those wrapped in `.optional()`, `.nullable()`, arrays, unions, and objects.
-
-- Improved reliability of string field types in tool schema compatibility ([#9266](https://github.com/mastra-ai/mastra/pull/9266))
-
-## 0.11.4
-
-### Patch Changes
-
-- Fixes an issue when the OpenAI reasoning schema compatibility layer was calling defaultValue() as a function, which works in Zod v3 but fails in Zod v4 where defaultValue is stored directly as a value. ([#8090](https://github.com/mastra-ai/mastra/pull/8090))
-
-## 0.11.4-alpha.0
-
-### Patch Changes
-
-- Fixes an issue when the OpenAI reasoning schema compatibility layer was calling defaultValue() as a function, which works in Zod v3 but fails in Zod v4 where defaultValue is stored directly as a value. ([#8090](https://github.com/mastra-ai/mastra/pull/8090))
-
-## 0.11.3
-
-### Patch Changes
-
-- Change SchemaCompat zodToJsonSchema ref strategy from none to relative, leading to less schema warnings and smaller converted schema sizes ([#7697](https://github.com/mastra-ai/mastra/pull/7697))
-
-## 0.11.3-alpha.0
-
-### Patch Changes
-
-- Change SchemaCompat zodToJsonSchema ref strategy from none to relative, leading to less schema warnings and smaller converted schema sizes ([#7697](https://github.com/mastra-ai/mastra/pull/7697))
-
-## 0.11.2
-
-### Patch Changes
-
-- ab48c97: dependencies updates:
-  - Updated dependency [`zod-to-json-schema@^3.24.6` ↗︎](https://www.npmjs.com/package/zod-to-json-schema/v/3.24.6) (from `^3.24.5`, in `dependencies`)
-- 637f323: Fix issue with some compilers and calling zod v4's toJSONSchema function
-- de3cbc6: Update the `package.json` file to include additional fields like `repository`, `homepage` or `files`.
-- 45e4d39: Try fixing the `Attempted import error: 'z'.'toJSONSchema' is not exported from 'zod'` error by tricking the compiler
-
-## 0.11.2-alpha.3
-
-### Patch Changes
-
-- [#7350](https://github.com/mastra-ai/mastra/pull/7350) [`45e4d39`](https://github.com/mastra-ai/mastra/commit/45e4d391a2a09fc70c48e4d60f505586ada1ba0e) Thanks [@LekoArts](https://github.com/LekoArts)! - Try fixing the `Attempted import error: 'z'.'toJSONSchema' is not exported from 'zod'` error by tricking the compiler
-
-## 0.11.2-alpha.2
-
-### Patch Changes
-
-- [#7343](https://github.com/mastra-ai/mastra/pull/7343) [`de3cbc6`](https://github.com/mastra-ai/mastra/commit/de3cbc61079211431bd30487982ea3653517278e) Thanks [@LekoArts](https://github.com/LekoArts)! - Update the `package.json` file to include additional fields like `repository`, `homepage` or `files`.
-
-## 0.11.2-alpha.1
-
-### Patch Changes
-
-- [#5816](https://github.com/mastra-ai/mastra/pull/5816) [`ab48c97`](https://github.com/mastra-ai/mastra/commit/ab48c979098ea571faf998a55d3a00e7acd7a715) Thanks [@dane-ai-mastra](https://github.com/apps/dane-ai-mastra)! - dependencies updates:
-  - Updated dependency [`zod-to-json-schema@^3.24.6` ↗︎](https://www.npmjs.com/package/zod-to-json-schema/v/3.24.6) (from `^3.24.5`, in `dependencies`)
-
-## 0.11.2-alpha.0
-
-### Patch Changes
-
-- [#7121](https://github.com/mastra-ai/mastra/pull/7121) [`637f323`](https://github.com/mastra-ai/mastra/commit/637f32371d79a8f78c52c0d53411af0915fcec67) Thanks [@DanielSLew](https://github.com/DanielSLew)! - Fix issue with some compilers and calling zod v4's toJSONSchema function
-
-## 0.11.1
-
-### Patch Changes
-
-- [`c6113ed`](https://github.com/mastra-ai/mastra/commit/c6113ed7f9df297e130d94436ceee310273d6430) Thanks [@wardpeet](https://github.com/wardpeet)! - Fix peerdpes for @mastra/core
-
-## 0.11.0
-
-### Minor Changes
-
-- [#7032](https://github.com/mastra-ai/mastra/pull/7032) [`1191ce9`](https://github.com/mastra-ai/mastra/commit/1191ce946b40ed291e7877a349f8388e3cff7e5c) Thanks [@wardpeet](https://github.com/wardpeet)! - Bump zod peerdep to 3.25.0 to support both v3/v4
-
-### Patch Changes
-
-- [#7028](https://github.com/mastra-ai/mastra/pull/7028) [`da58ccc`](https://github.com/mastra-ai/mastra/commit/da58ccc1f2ac33da0cb97b00443fc6208b45bdec) Thanks [@wardpeet](https://github.com/wardpeet)! - Fix exportsmap
-
-- [#6982](https://github.com/mastra-ai/mastra/pull/6982) [`94e9f54`](https://github.com/mastra-ai/mastra/commit/94e9f547d66ef7cd01d9075ab53b5ca9a1cae100) Thanks [@wardpeet](https://github.com/wardpeet)! - Fix AI peerdeps for NPM install
-
-- [#6944](https://github.com/mastra-ai/mastra/pull/6944) [`a93f3ba`](https://github.com/mastra-ai/mastra/commit/a93f3ba05eef4cf17f876d61d29cf0841a9e70b7) Thanks [@wardpeet](https://github.com/wardpeet)! - Add support for zod v4
-
-## 0.11.0-alpha.2
-
-### Minor Changes
-
-- [#7032](https://github.com/mastra-ai/mastra/pull/7032) [`1191ce9`](https://github.com/mastra-ai/mastra/commit/1191ce946b40ed291e7877a349f8388e3cff7e5c) Thanks [@wardpeet](https://github.com/wardpeet)! - Bump zod peerdep to 3.25.0 to support both v3/v4
-
-## 0.10.6-alpha.1
-
-### Patch Changes
-
-- [#7028](https://github.com/mastra-ai/mastra/pull/7028) [`da58ccc`](https://github.com/mastra-ai/mastra/commit/da58ccc1f2ac33da0cb97b00443fc6208b45bdec) Thanks [@wardpeet](https://github.com/wardpeet)! - Fix exportsmap
-
-## 0.10.6-alpha.0
-
-### Patch Changes
-
-- [#6982](https://github.com/mastra-ai/mastra/pull/6982) [`94e9f54`](https://github.com/mastra-ai/mastra/commit/94e9f547d66ef7cd01d9075ab53b5ca9a1cae100) Thanks [@wardpeet](https://github.com/wardpeet)! - Fix AI peerdeps for NPM install
-
-- [#6944](https://github.com/mastra-ai/mastra/pull/6944) [`a93f3ba`](https://github.com/mastra-ai/mastra/commit/a93f3ba05eef4cf17f876d61d29cf0841a9e70b7) Thanks [@wardpeet](https://github.com/wardpeet)! - Add support for zod v4
-
-## 0.10.7
-
-### Patch Changes
-
-- dd94a26: Dont rely on the full language model for schema compat
-- 2fff911: Fix vnext working memory tool schema when model is incompatible with schema
-- ae2eb63: Handle regex checks better, return description as a string rather than an object with pattern and flags.
-
-## 0.10.7-alpha.1
-
-### Patch Changes
-
-- ae2eb63: Handle regex checks better, return description as a string rather than an object with pattern and flags.
-
-## 0.10.7-alpha.0
-
-### Patch Changes
-
-- dd94a26: Dont rely on the full language model for schema compat
-- 2fff911: Fix vnext working memory tool schema when model is incompatible with schema
-
-## 0.10.6
-
-### Patch Changes
-
-- 4a406ec: fixes TypeScript declaration file imports to ensure proper ESM compatibility
-
-## 0.10.6-alpha.0
-
-### Patch Changes
-
-- 4a406ec: fixes TypeScript declaration file imports to ensure proper ESM compatibility
-
-## 0.10.5
-
-### Patch Changes
-
-- 4da943f: Fix Cannot read properties of undefined (reading 'typeName') in schema compat check
-
-## 0.10.5-alpha.0
-
-### Patch Changes
-
-- 4da943f: Fix Cannot read properties of undefined (reading 'typeName') in schema compat check
-
-## 0.10.4
-
-### Patch Changes
-
-- 0c85311: Fix Google models ZodNull tool schema handling
-
-## 0.10.4-alpha.0
-
-### Patch Changes
-
-- 0c85311: Fix Google models ZodNull tool schema handling
-
-## 0.10.3
-
-### Patch Changes
-
-- 98bbe5a: Claude cannot handle tuple schemas now.
-- a853c43: Allow for object.passthrough in schema compat (aka MCP tool support).
-
-## 0.10.3-alpha.1
-
-### Patch Changes
-
-- a853c43: Allow for object.passthrough in schema compat (aka MCP tool support).
-
-## 0.10.3-alpha.0
-
-### Patch Changes
-
-- 98bbe5a: Claude cannot handle tuple schemas now.
-
-## 0.10.2
-
-### Patch Changes
-
-- f6fd25f: Updates @mastra/schema-compat to allow all zod schemas. Uses @mastra/schema-compat to apply schema transformations to agent output schema.
-- f9816ae: Create @mastra/schema-compat package to extract the schema compatibility layer to be used outside of mastra
-
-## 0.10.2-alpha.3
-
-### Patch Changes
-
-- f6fd25f: Updates @mastra/schema-compat to allow all zod schemas. Uses @mastra/schema-compat to apply schema transformations to agent output schema.
-
-## 0.10.2-alpha.2
-
-### Patch Changes
-
-- f9816ae: Create @mastra/schema-compat package to extract the schema compatibility layer to be used outside of mastra