mirror of
https://github.com/ComposioHQ/composio.git
synced 2026-09-22 11:46:35 +08:00
sdkrelease[bot]
02196de0b5
This PR was opened by the [Changesets release](https://github.com/changesets/action) 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 next, this PR will be updated. # Releases ## @composio/core@0.16.0 ### Minor Changes -5e57815: Keep free-form object roots, `patternProperties`, and `additionalProperties` when parsing a tool schema. `ToolSchema.parse` used to reject a bare `{ "type": "object" }` root, drop root `patternProperties` as an unknown key, and reject a root `additionalProperties` written as a schema instead of a boolean. Free-form roots now parse successfully, and both constraints survive parsing exactly as written. The public `ToolSchema` type now makes `properties` optional to reflect those valid property-less object schemas. This matters downstream. Every provider reads `inputParameters` after parsing, so a tool that declares dynamic keys had those rules stripped before the model ever saw them. An omitted `additionalProperties` still stays omitted. The parser does not invent a value, because each converter decides its own default. **What no longer works** Parsing no longer fails on a schema-valued root `additionalProperties`. ```ts const tool = ToolSchema.parse({ slug: 'MY_TOOL', inputParameters: { type: 'object', properties: { name: { type: 'string' } }, additionalProperties: { type: 'number' }, }, // ... }); // before: parsing failed, because only a boolean was accepted // now: tool.inputParameters.additionalProperties is { type: 'number' } ``` **What to do instead** Nothing, if you only ever passed boolean values. That case is unchanged. If your code assumed `inputParameters` never carries `patternProperties`, or that `additionalProperties` is always a boolean, widen that assumption. Both keywords can now appear, and `additionalProperties` can be a boolean or a schema object. ### Patch Changes -a2f6b96: Add `type: "object"` to nested JSON Schema nodes that carry `properties` without an explicit type, so tool schemas work with strict OpenAPI 3.0 consumers like Google Gemini. -c625edc: Reuse fetched tool schemas when provider-wrapped tools execute to avoid a redundant retrieval request. - Updated dependencies [5e57815] - @composio/json-schema-to-zod@0.3.0 ## @composio/json-schema-to-zod@0.3.0 ### Minor Changes -5e57815: Keep the content of free-form object arguments, and apply dynamic key rules only where they belong. An object schema with no named properties, written as `{ "type": "object" }` or `{ "properties": {} }`, used to become a strict empty object. The only value that passed was `{}`. Any real payload was rejected. Such an object is now open, so arbitrary content is accepted and preserved. This works at the root, nested inside another object, and inside array items. Dynamic keys are now routed to the schemas that actually claim them. Every matching `patternProperties` entry validates its key. A schema-valued `additionalProperties` applies only to keys that no declared property and no pattern matches. Before this change a key could pass by satisfying an unrelated pattern instead of its own. **What no longer works** Converting a property-less object no longer gives you a schema that rejects everything. ```ts const schema = jsonSchemaToZod({ type: 'object' }); schema.parse({ anything: 1 }); // before: threw, because the result was z.object({}).strict() // now: returns { anything: 1 } ``` **What to do instead** If you want a property-less object to stay closed, say so in the JSON Schema: ```ts const schema = jsonSchemaToZod({ type: 'object', additionalProperties: false }); schema.parse({ anything: 1 }); // throws, as before ``` Objects that name at least one property are unchanged. They still reject unknown keys when `additionalProperties` is omitted. ## @composio/claude-agent-sdk@0.11.0 ### Minor Changes -ac6bbab: Register each tool with its complete schema, so root rules reach the Claude Agent SDK. The provider used to register a raw property shape. A raw shape is only the map of named properties, so it cannot carry any root rule. `additionalProperties` and `patternProperties` were dropped before the SDK saw them. Two things went wrong because of that. Free-form object arguments lost their content. An argument the tool never declared was quietly removed, and the tool ran anyway. Both are fixed. The provider now registers the whole object schema. **What no longer works** An undeclared argument no longer passes silently. ```ts // The tool declares `to` and nothing else. The model also sends `hallucinated`. { to: 'someone@example.com', hallucinated: 'value' } // before: `hallucinated` was stripped, and the tool ran with { to: '...' } // now: the caller receives an error result, and the tool does not run ``` Tools with no input parameters behave the same way. They stay closed and reject every argument. **What to do instead** If the model should be allowed to send extra keys, say so in the tool schema: ```json { "type": "object", "properties": { "to": { "type": "string" } }, "additionalProperties": true } ``` If an argument is one the tool really accepts, declare it in `properties`. Rejection is usually the better outcome, because the agent sees the error and can correct itself instead of running with a silently dropped argument. This brings the provider in line with `@composio/vercel`, `@composio/langchain`, and `@composio/llamaindex`, which already registered complete schemas. ## @composio/google@0.10.2 ### Patch Changes -a2f6b96: Add missing object types to nested Google GenAI tool schemas so Gemini accepts function declarations with property maps. This release requires `@composio/core >=0.16.0 <1.0.0` for the shared schema normalizer. ## @composio/slim@0.16.0 ### Patch Changes - Updated dependencies [5e57815] - @composio/json-schema-to-zod@0.3.0 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Changesets
Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works
with multi-package repos, or single-package repos to help you version and publish your code. You can
find the full documentation for it in our repository
We have a quick list of common questions to get you started engaging with this project in our documentation