Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Release: update version (#4104)

sdkrelease[bot]02196de0b5df
diff --git a/.changeset/claude-agent-sdk-complete-schema-registration.md b/.changeset/claude-agent-sdk-complete-schema-registration.md
deleted file mode 100644
index 02225446f..000000000
--- a/.changeset/claude-agent-sdk-complete-schema-registration.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-'@composio/claude-agent-sdk': minor
----
-
-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: '[email protected]', 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.
diff --git a/.changeset/ensure-object-type-on-properties.md b/.changeset/ensure-object-type-on-properties.md
deleted file mode 100644
index 6bc3ab9ba..000000000
--- a/.changeset/ensure-object-type-on-properties.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@composio/core': patch
----
-
-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.
diff --git a/.changeset/fix-property-less-object-conversion.md b/.changeset/fix-property-less-object-conversion.md
deleted file mode 100644
index 936a55f5e..000000000
--- a/.changeset/fix-property-less-object-conversion.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-'@composio/json-schema-to-zod': minor
----
-
-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.
diff --git a/.changeset/normalize-google-object-types.md b/.changeset/normalize-google-object-types.md
deleted file mode 100644
index b5d9ccc23..000000000
--- a/.changeset/normalize-google-object-types.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@composio/google': patch
----
-
-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.
diff --git a/.changeset/preserve-root-dynamic-key-constraints.md b/.changeset/preserve-root-dynamic-key-constraints.md
deleted file mode 100644
index 083cd81c9..000000000
--- a/.changeset/preserve-root-dynamic-key-constraints.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-'@composio/core': minor
----
-
-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.
diff --git a/.changeset/reuse-provider-tool-schemas.md b/.changeset/reuse-provider-tool-schemas.md
deleted file mode 100644
index 8e17bca90..000000000
--- a/.changeset/reuse-provider-tool-schemas.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'@composio/core': patch
----
-
-Reuse fetched tool schemas when provider-wrapped tools execute to avoid a redundant retrieval request.
diff --git a/ts/packages/core/CHANGELOG.md b/ts/packages/core/CHANGELOG.md
index 4fdc47bc7..fb552c082 100644
--- a/ts/packages/core/CHANGELOG.md
+++ b/ts/packages/core/CHANGELOG.md
@@ -1,5 +1,49 @@
# @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/[email protected]
+
## 0.15.0
### Minor Changes
diff --git a/ts/packages/core/package.json b/ts/packages/core/package.json
index f8c5de0aa..949aa8d9a 100644
--- a/ts/packages/core/package.json
+++ b/ts/packages/core/package.json
@@ -1,7 +1,7 @@
{
"name": "@composio/core",
"type": "module",
- "version": "0.15.0",
+ "version": "0.16.0",
"description": "",
"main": "src/index.ts",
"publishConfig": {
diff --git a/ts/packages/json-schema-to-zod/CHANGELOG.md b/ts/packages/json-schema-to-zod/CHANGELOG.md
index b9c9a5e97..a20ecbe87 100644
--- a/ts/packages/json-schema-to-zod/CHANGELOG.md
+++ b/ts/packages/json-schema-to-zod/CHANGELOG.md
@@ -1,5 +1,39 @@
# @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.
+
## 0.2.2
### Patch Changes
diff --git a/ts/packages/json-schema-to-zod/package.json b/ts/packages/json-schema-to-zod/package.json
index 267c90973..fd15cb866 100644
--- a/ts/packages/json-schema-to-zod/package.json
+++ b/ts/packages/json-schema-to-zod/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/json-schema-to-zod",
- "version": "0.2.2",
+ "version": "0.3.0",
"description": "",
"main": "src/index.ts",
"type": "module",
diff --git a/ts/packages/providers/claude-agent-sdk/CHANGELOG.md b/ts/packages/providers/claude-agent-sdk/CHANGELOG.md
index dbe2edf20..fdb5924cf 100644
--- a/ts/packages/providers/claude-agent-sdk/CHANGELOG.md
+++ b/ts/packages/providers/claude-agent-sdk/CHANGELOG.md
@@ -1,5 +1,47 @@
# @composio/claude-code-agents
+## 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: '[email protected]', 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.
+
## 0.10.1
### Patch Changes
diff --git a/ts/packages/providers/claude-agent-sdk/package.json b/ts/packages/providers/claude-agent-sdk/package.json
index 59cb899cf..eac77ac68 100644
--- a/ts/packages/providers/claude-agent-sdk/package.json
+++ b/ts/packages/providers/claude-agent-sdk/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/claude-agent-sdk",
- "version": "0.10.1",
+ "version": "0.11.0",
"description": "Composio provider for Claude Agent SDK",
"main": "src/index.ts",
"type": "module",
diff --git a/ts/packages/providers/google/CHANGELOG.md b/ts/packages/providers/google/CHANGELOG.md
index 2eeb820aa..f081fdcec 100644
--- a/ts/packages/providers/google/CHANGELOG.md
+++ b/ts/packages/providers/google/CHANGELOG.md
@@ -1,5 +1,11 @@
# @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.
+
## 0.10.1
### Patch Changes
diff --git a/ts/packages/providers/google/package.json b/ts/packages/providers/google/package.json
index 2e197d182..c22821aba 100644
--- a/ts/packages/providers/google/package.json
+++ b/ts/packages/providers/google/package.json
@@ -1,6 +1,6 @@
{
"name": "@composio/google",
- "version": "0.10.1",
+ "version": "0.10.2",
"description": "Google GenAI Provider for Composio SDK",
"main": "src/index.ts",
"type": "module",
diff --git a/ts/packages/slim/CHANGELOG.md b/ts/packages/slim/CHANGELOG.md
index 29046b4ba..6ed03b3b0 100644
--- a/ts/packages/slim/CHANGELOG.md
+++ b/ts/packages/slim/CHANGELOG.md
@@ -1,5 +1,12 @@
# @composio/slim
+## 0.16.0
+
+### Patch Changes
+
+- Updated dependencies [5e57815]
+ - @composio/[email protected]
+
## 0.15.0
### Patch Changes
diff --git a/ts/packages/slim/package.json b/ts/packages/slim/package.json
index 9a16576e5..9a3affa31 100644
--- a/ts/packages/slim/package.json
+++ b/ts/packages/slim/package.json
@@ -1,7 +1,7 @@
{
"name": "@composio/slim",
"type": "module",
- "version": "0.15.0",
+ "version": "0.16.0",
"description": "Slim Composio core package without packaged source or docs",
"main": "dist/index.mjs",
"publishConfig": {