@devries-cameron20 / composio Mirror · read-only / commits / 9764ce33f
Fork 0

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

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 21, 19:45 UTC

Release: update version (#3616)

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.12.0 ### Minor Changes - a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`. - dfd7a08: Add per-request cancellation to public SDK methods via a new `ComposioRequestOptions` (`{ signal?: AbortSignal }`) trailing argument, plus a typed `ComposioRequestCancelledError` for detecting caller-initiated aborts. Without this, a slow `tools.get` or `tools.execute` had no way to be cancelled — a 100s search would block the calling agent indefinitely. The new shape: ```typescript try { const tools = await composio.tools.get( 'user_1', { search: 'send email', limit: 50 }, { signal: AbortSignal.timeout(5_000) } ); } catch (err) { if (err instanceof ComposioRequestCancelledError) { return; } throw err; } ``` The signal is forwarded to the underlying `@composio/client` fetch. Any abort error (`APIUserAbortError`, `AbortError`, or `DOMException(name='AbortError')`) coming back is normalized to `ComposioRequestCancelledError` so callers can `instanceof`-detect cancellation without unwrapping nested causes. Catch-and-wrap paths in `tools.execute` / `tools.getRawComposioToolBySlug` / `toolkits.get` re-throw the cancellation error rather than remapping it to `ComposioToolExecutionError` / `ComposioToolNotFoundError` / `ComposioToolkitFetchError`. Wired through on: - **Tools**: `get`, `getRawComposioTools`, `getRawComposioToolBySlug`, `getRawToolRouterSessionTools`, `execute`, `executeSessionTool`, `getToolsEnum`, `getInput`, `proxyExecute` - **Toolkits**: `get`, `listCategories` - **AuthConfigs**: `list`, `create`, `get`, `update`, `delete`, `updateStatus`, `enable`, `disable` - **ConnectedAccounts**: `list`, `get`, `delete`, `refresh`, `updateStatus`, `enable`, `disable`, `update` - **Triggers**: `listActive`, `create`, `update`, `delete`, `enable`, `disable`, `listTypes`, `getType`, `listEnum` - **MCP**: `create`, `list`, `get`, `delete`, `update`, `generate` - **ToolRouter** (`composio.create` / `composio.use`, `composio.toolRouter.create` / `.use`) — long-running session-creation paths - **ToolRouterSession**: `authorize`, `toolkits`, `search`, `execute`, `proxyExecute`, `update` ### Custom-tool cooperative cancellation Native tool execution is cancelled by the SDK (the underlying `fetch` is aborted). Custom tools are different — the SDK can't preempt user-supplied JavaScript. Two affordances are added so callers get sensible behavior anyway: 1. **Pre-execute signal check**: if `signal.aborted` is true before the user's `execute` runs, the SDK throws `ComposioRequestCancelledError` and never invokes user code. 2. **Cooperative signal forwarding**: the same `AbortSignal` is exposed via `SessionContext.signal` for Tool Router custom tools. Long-running implementations can wire `ctx.signal` into their own `fetch` (or any abortable IO) to abort mid-execution; the resulting `AbortError` is normalized to `ComposioRequestCancelledError` by the SDK. ```typescript import { experimental_createTool } from '@composio/core'; const longRunningFetch = experimental_createTool('LONG_RUNNING_FETCH', { name: 'Long-running fetch', description: 'Fetches a URL with cooperative cancellation', inputParams: z.object({ url: z.string() }), execute: async (input, ctx) => { // Pass ctx.signal into fetch so a session.execute(...) abort cancels // the in-flight HTTP request mid-flight. const resp = await fetch(input.url, { signal: ctx.signal }); return { result: await resp.json() }; }, }); ``` - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. - 4b76dbf: Remove the deprecated `uuid` field from the auth config retrieve/list response type. The platform has removed the deprecated V1/V2 UUID-mirror field from V3 API responses (it was a mirror of the canonical nanoid `id`). The SDK no longer reads or re-exposes `uuid` on `AuthConfigRetrieveResponse` (and therefore on the items of `AuthConfigListResponse`). This is technically a breaking change to the SDK response type: consumers should use `id` instead of `uuid`. The `expectedInputFields` field is unaffected — it remains a top-level field on the API response. ### Patch Changes - 552859a: Expose `search` and `showDisabled` filters on `authConfigs.list()`. - 23f9053: Replace `chalk` with `picocolors` for colored error and log output. The two render identically, but `picocolors` is a fraction of the size (~0.8 kB gzipped vs chalk's much larger footprint), shrinking the bundled package. - 507318d: Add a provider-agnostic JSON-schema property-key sanitizer: `sanitizeSchemaPropertyKeys(schema, policy)`, `restoreOriginalKeys(value, mapping)`, `mappingHasRenames(mapping)`, and the `KeyMapping` / `KeySanitizationPolicy` types. Some providers constrain the characters and length of tool `input_schema` property keys and reject the whole request on a single violation. This utility rewrites offending keys to conforming aliases (recursing through `properties`, array `items`/`prefixItems`, the composition keywords `allOf`/`anyOf`/`oneOf` and `not`/`if`/`then`/`else`, plus `additionalProperties`/`patternProperties`/`$defs`/`contains`) and records a schema-shaped reverse mapping so the original parameter names can be restored before execution. The _constraint_ is injected as a `KeySanitizationPolicy`, so the traversal, collision handling, prototype safety, and depth cap stay provider-agnostic. The `@composio/anthropic` provider now consumes it. - 6a4cb54: Preserve root `$defs` / `definitions` blocks on tool parameter schemas and dereference them in the Node file modifier, so auto file upload/download detection works when `file_uploadable` or `file_downloadable` is hidden behind an internal `$ref`. - cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it. - Updated dependencies [025a657] - @composio/json-schema-to-zod@0.2.0 ## @composio/json-schema-to-zod@0.2.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/anthropic@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ### Patch Changes - 507318d: Harden the Anthropic tool property-key sanitizer: - **Broader schema coverage.** Illegal keys are now sanitized wherever they appear in a tool schema — under the composition keywords (`allOf`/`anyOf`/`oneOf`, `not`/`if`/`then`/`else`), `prefixItems` tuples, `additionalProperties`/`patternProperties`, and `$defs`/`definitions` — not just top-level `properties` and array `items`. Previously a single illegal key under one of these would still 400 the entire request. Renames inside composition keywords are restored correctly (they fold into the value level they share). - **`$ref` keys restored.** `wrapTool` now dereferences internal `$ref`/`$defs` (leniently — a dangling ref degrades to a permissive schema instead of throwing) before sanitizing, so keys reachable only through a reference are both made compliant and restored. Only genuinely dynamic positions (`additionalProperties`, `patternProperties`, `contains`) remain rewrite-only. - **Shared core implementation.** The traversal/restoration mechanism now lives in `@composio/core` (`sanitizeSchemaPropertyKeys` / `restoreOriginalKeys`); this provider supplies only the Anthropic key constraint as a policy, reusing core's prototype-pollution guard and depth cap. - **Prototype-safe key restoration.** Reverse-mapping lookups and the rebuilt argument object are now prototype-free, so a tool call whose arguments use a key matching an `Object.prototype` member (`__proto__`, `constructor`, `toString`, `hasOwnProperty`, …) no longer throws or silently corrupts the payload sent to the backend. `Object.prototype` is never mutated. - **Depth cap.** Schema sanitization and key restoration now bound recursion (matching core's JSON-schema walker) so a pathologically deep schema or argument object fails with a clear error instead of overflowing the stack. - **Empty / all-illegal keys.** A property key that is empty (or made entirely of stripped characters) now becomes a deterministic non-empty alias instead of an empty string, which would itself have violated Anthropic's `{1,64}` length bound. - **Collision loop.** Replaced a latent non-terminating fixed point in the alias collision resolver with a counter that always makes progress. - **Observability.** The provider now emits `debug` logs when it rewrites a tool's schema keys and when it restores them at execution time, and the wrap-then-execute (same provider instance) contract for key restoration is documented. - c90ae95: Sanitize tool `input_schema` property keys that violate Anthropic's `^[a-zA-Z0-9_.-]{1,64}$` constraint before sending tools to the Messages API, then restore the original names when the tool is executed. A single non-conforming key previously made Anthropic reject the entire `tools` array with HTTP 400, taking down every other tool in the same request. This commonly happened with OneDrive's Microsoft Graph OData parameters (`$top`, `$filter`, `@microsoft.graph.conflictBehavior`) and with over-long flattened keys from tools such as Zoom. Offending keys are now rewritten to conforming aliases (`$` → `dollar_`, `@` → `at_`, any other illegal character → `_`, keys longer than 64 characters truncated with a deterministic suffix), recursing through nested object `properties` and array `items` schemas. The original parameter names are restored before the call reaches the Composio backend, so the model sees `dollar_top` while the backend still receives `$top`. Schemas whose keys already conform are left unchanged. ## @composio/claude-agent-sdk@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ### Patch Changes - cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it. ## @composio/cloudflare@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/google@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/langchain@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/llamaindex@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/mastra@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ### Patch Changes - aaabf5e: Relax the Mastra provider output schema so real third-party API responses are no longer rejected by Mastra's output validation (which dropped the data and substituted an error). Before compilation the output schema is made lenient: every typed node becomes nullable, objects allow extra keys (`additionalProperties: true`), `enum`/`const` are widened to also admit `null`, and `required` is dropped (APIs omit unset fields rather than returning `null` for them). All of these only widen what validates, so previously-valid output is unaffected. ## @composio/openai@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/openai-agents@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/vercel@0.10.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/ts-builders@0.2.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/cli@0.3.0 ### Minor Changes - a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`. - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ### Patch Changes - 5f004ff: Drop `COMPOSIO_UPSERT_RECIPE` and `COMPOSIO_GET_RECIPE` from the CLI meta-tool list. These slugs were removed from `@composio/client` (alpha.74), so listing them broke the type-checked CLI build. - 23f9053: Remove the unused `ansis` dependency from the CLI. Colored output is already handled by `picocolors`, so `ansis` was a dead production dependency that shipped with the package. - 446c6f6: Fix virtual TypeScript file resolution used by CLI type generation so in-memory imports resolve consistently during transpilation and validation. - Updated dependencies [552859a] - Updated dependencies [a0bef5d] - Updated dependencies [23f9053] - Updated dependencies [dfd7a08] - Updated dependencies [507318d] - Updated dependencies [025a657] - Updated dependencies [6a4cb54] - Updated dependencies [4b76dbf] - Updated dependencies [cbbad15] - @composio/core@0.12.0 - @composio/json-schema-to-zod@0.2.0 - @composio/ts-builders@0.2.0 - @composio/cli-keyring@0.2.0 - @composio/cli-local-tools@0.1.0 ## @composio/cli-keyring@0.2.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ## @composio/cli-local-tools@0.1.0 ### Minor Changes - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts. ### Patch Changes - Updated dependencies [552859a] - Updated dependencies [a0bef5d] - Updated dependencies [23f9053] - Updated dependencies [dfd7a08] - Updated dependencies [507318d] - Updated dependencies [025a657] - Updated dependencies [6a4cb54] - Updated dependencies [4b76dbf] - Updated dependencies [cbbad15] - @composio/core@0.12.0 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

sdkrelease[bot] committed Jun 25, 2026 at 04:38 UTC 9764ce33ff63060e9f8b80e4fdb9b16fb4bd60da
47 files changed +246 -177
.changeset/anthropic-sanitize-keys-hardening.md deleted
-14
@@ -1,14 +0,0 @@
1 ----
2 -'@composio/anthropic': patch
3 ----
4 -
5 -Harden the Anthropic tool property-key sanitizer:
6 -
7 -- **Broader schema coverage.** Illegal keys are now sanitized wherever they appear in a tool schema — under the composition keywords (`allOf`/`anyOf`/`oneOf`, `not`/`if`/`then`/`else`), `prefixItems` tuples, `additionalProperties`/`patternProperties`, and `$defs`/`definitions` — not just top-level `properties` and array `items`. Previously a single illegal key under one of these would still 400 the entire request. Renames inside composition keywords are restored correctly (they fold into the value level they share).
8 -- **`$ref` keys restored.** `wrapTool` now dereferences internal `$ref`/`$defs` (leniently — a dangling ref degrades to a permissive schema instead of throwing) before sanitizing, so keys reachable only through a reference are both made compliant and restored. Only genuinely dynamic positions (`additionalProperties`, `patternProperties`, `contains`) remain rewrite-only.
9 -- **Shared core implementation.** The traversal/restoration mechanism now lives in `@composio/core` (`sanitizeSchemaPropertyKeys` / `restoreOriginalKeys`); this provider supplies only the Anthropic key constraint as a policy, reusing core's prototype-pollution guard and depth cap.
10 -- **Prototype-safe key restoration.** Reverse-mapping lookups and the rebuilt argument object are now prototype-free, so a tool call whose arguments use a key matching an `Object.prototype` member (`__proto__`, `constructor`, `toString`, `hasOwnProperty`, …) no longer throws or silently corrupts the payload sent to the backend. `Object.prototype` is never mutated.
11 -- **Depth cap.** Schema sanitization and key restoration now bound recursion (matching core's JSON-schema walker) so a pathologically deep schema or argument object fails with a clear error instead of overflowing the stack.
12 -- **Empty / all-illegal keys.** A property key that is empty (or made entirely of stripped characters) now becomes a deterministic non-empty alias instead of an empty string, which would itself have violated Anthropic's `{1,64}` length bound.
13 -- **Collision loop.** Replaced a latent non-terminating fixed point in the alias collision resolver with a counter that always makes progress.
14 -- **Observability.** The provider now emits `debug` logs when it rewrites a tool's schema keys and when it restores them at execution time, and the wrap-then-execute (same provider instance) contract for key restoration is documented.
.changeset/anthropic-sanitize-tool-property-keys.md deleted
-7
@@ -1,7 +0,0 @@
1 ----
2 -'@composio/anthropic': patch
3 ----
4 -
5 -Sanitize tool `input_schema` property keys that violate Anthropic's `^[a-zA-Z0-9_.-]{1,64}$` constraint before sending tools to the Messages API, then restore the original names when the tool is executed.
6 -
7 -A single non-conforming key previously made Anthropic reject the entire `tools` array with HTTP 400, taking down every other tool in the same request. This commonly happened with OneDrive's Microsoft Graph OData parameters (`$top`, `$filter`, `@microsoft.graph.conflictBehavior`) and with over-long flattened keys from tools such as Zoom. Offending keys are now rewritten to conforming aliases (`$` → `dollar_`, `@` → `at_`, any other illegal character → `_`, keys longer than 64 characters truncated with a deterministic suffix), recursing through nested object `properties` and array `items` schemas. The original parameter names are restored before the call reaches the Composio backend, so the model sees `dollar_top` while the backend still receives `$top`. Schemas whose keys already conform are left unchanged.
.changeset/auth-config-list-search.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Expose `search` and `showDisabled` filters on `authConfigs.list()`.
.changeset/bump-composio-client-alpha74.md deleted
-6
@@ -1,6 +0,0 @@
1 ----
2 -'@composio/core': minor
3 -'@composio/cli': minor
4 ----
5 -
6 -Bump `@composio/client` to `0.1.0-alpha.74`.
.changeset/cli-drop-recipe-meta-tool-slugs.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/cli': patch
3 ----
4 -
5 -Drop `COMPOSIO_UPSERT_RECIPE` and `COMPOSIO_GET_RECIPE` from the CLI meta-tool list. These slugs were removed from `@composio/client` (alpha.74), so listing them broke the type-checked CLI build.
.changeset/cli-remove-unused-ansis.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/cli': patch
3 ----
4 -
5 -Remove the unused `ansis` dependency from the CLI. Colored output is already handled by `picocolors`, so `ansis` was a dead production dependency that shipped with the package.
.changeset/core-chalk-to-picocolors.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Replace `chalk` with `picocolors` for colored error and log output. The two render identically, but `picocolors` is a fraction of the size (~0.8 kB gzipped vs chalk's much larger footprint), shrinking the bundled package.
.changeset/core-request-options-signal-timeout.md deleted
-57
@@ -1,57 +0,0 @@
1 ----
2 -"@composio/core": minor
3 ----
4 -
5 -Add per-request cancellation to public SDK methods via a new `ComposioRequestOptions` (`{ signal?: AbortSignal }`) trailing argument, plus a typed `ComposioRequestCancelledError` for detecting caller-initiated aborts.
6 -
7 -Without this, a slow `tools.get` or `tools.execute` had no way to be cancelled — a 100s search would block the calling agent indefinitely. The new shape:
8 -
9 -```typescript
10 -try {
11 - const tools = await composio.tools.get(
12 - 'user_1',
13 - { search: 'send email', limit: 50 },
14 - { signal: AbortSignal.timeout(5_000) }
15 - );
16 -} catch (err) {
17 - if (err instanceof ComposioRequestCancelledError) {
18 - return;
19 - }
20 - throw err;
21 -}
22 -```
23 -
24 -The signal is forwarded to the underlying `@composio/client` fetch. Any abort error (`APIUserAbortError`, `AbortError`, or `DOMException(name='AbortError')`) coming back is normalized to `ComposioRequestCancelledError` so callers can `instanceof`-detect cancellation without unwrapping nested causes. Catch-and-wrap paths in `tools.execute` / `tools.getRawComposioToolBySlug` / `toolkits.get` re-throw the cancellation error rather than remapping it to `ComposioToolExecutionError` / `ComposioToolNotFoundError` / `ComposioToolkitFetchError`.
25 -
26 -Wired through on:
27 -- **Tools**: `get`, `getRawComposioTools`, `getRawComposioToolBySlug`, `getRawToolRouterSessionTools`, `execute`, `executeSessionTool`, `getToolsEnum`, `getInput`, `proxyExecute`
28 -- **Toolkits**: `get`, `listCategories`
29 -- **AuthConfigs**: `list`, `create`, `get`, `update`, `delete`, `updateStatus`, `enable`, `disable`
30 -- **ConnectedAccounts**: `list`, `get`, `delete`, `refresh`, `updateStatus`, `enable`, `disable`, `update`
31 -- **Triggers**: `listActive`, `create`, `update`, `delete`, `enable`, `disable`, `listTypes`, `getType`, `listEnum`
32 -- **MCP**: `create`, `list`, `get`, `delete`, `update`, `generate`
33 -- **ToolRouter** (`composio.create` / `composio.use`, `composio.toolRouter.create` / `.use`) — long-running session-creation paths
34 -- **ToolRouterSession**: `authorize`, `toolkits`, `search`, `execute`, `proxyExecute`, `update`
35 -
36 -### Custom-tool cooperative cancellation
37 -
38 -Native tool execution is cancelled by the SDK (the underlying `fetch` is aborted). Custom tools are different — the SDK can't preempt user-supplied JavaScript. Two affordances are added so callers get sensible behavior anyway:
39 -
40 -1. **Pre-execute signal check**: if `signal.aborted` is true before the user's `execute` runs, the SDK throws `ComposioRequestCancelledError` and never invokes user code.
41 -2. **Cooperative signal forwarding**: the same `AbortSignal` is exposed via `SessionContext.signal` for Tool Router custom tools. Long-running implementations can wire `ctx.signal` into their own `fetch` (or any abortable IO) to abort mid-execution; the resulting `AbortError` is normalized to `ComposioRequestCancelledError` by the SDK.
42 -
43 -```typescript
44 -import { experimental_createTool } from '@composio/core';
45 -
46 -const longRunningFetch = experimental_createTool('LONG_RUNNING_FETCH', {
47 - name: 'Long-running fetch',
48 - description: 'Fetches a URL with cooperative cancellation',
49 - inputParams: z.object({ url: z.string() }),
50 - execute: async (input, ctx) => {
51 - // Pass ctx.signal into fetch so a session.execute(...) abort cancels
52 - // the in-flight HTTP request mid-flight.
53 - const resp = await fetch(input.url, { signal: ctx.signal });
54 - return { result: await resp.json() };
55 - },
56 -});
57 -```
.changeset/core-schema-property-key-sanitizer.md deleted
-7
@@ -1,7 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Add a provider-agnostic JSON-schema property-key sanitizer: `sanitizeSchemaPropertyKeys(schema, policy)`, `restoreOriginalKeys(value, mapping)`, `mappingHasRenames(mapping)`, and the `KeyMapping` / `KeySanitizationPolicy` types.
6 -
7 -Some providers constrain the characters and length of tool `input_schema` property keys and reject the whole request on a single violation. This utility rewrites offending keys to conforming aliases (recursing through `properties`, array `items`/`prefixItems`, the composition keywords `allOf`/`anyOf`/`oneOf` and `not`/`if`/`then`/`else`, plus `additionalProperties`/`patternProperties`/`$defs`/`contains`) and records a schema-shaped reverse mapping so the original parameter names can be restored before execution. The _constraint_ is injected as a `KeySanitizationPolicy`, so the traversal, collision handling, prototype safety, and depth cap stay provider-agnostic. The `@composio/anthropic` provider now consumes it.
.changeset/drop-commonjs-entrypoints.md deleted
-20
@@ -1,20 +0,0 @@
1 ----
2 -'@composio/core': minor
3 -'@composio/json-schema-to-zod': minor
4 -'@composio/ts-builders': minor
5 -'@composio/cli': minor
6 -'@composio/cli-keyring': minor
7 -'@composio/cli-local-tools': minor
8 -'@composio/anthropic': minor
9 -'@composio/claude-agent-sdk': minor
10 -'@composio/cloudflare': minor
11 -'@composio/google': minor
12 -'@composio/langchain': minor
13 -'@composio/llamaindex': minor
14 -'@composio/mastra': minor
15 -'@composio/openai': minor
16 -'@composio/openai-agents': minor
17 -'@composio/vercel': minor
18 ----
19 -
20 -Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
.changeset/file-modifier-dereference-ref.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/core': patch
3 ----
4 -
5 -Preserve root `$defs` / `definitions` blocks on tool parameter schemas and dereference them in the Node file modifier, so auto file upload/download detection works when `file_uploadable` or `file_downloadable` is hidden behind an internal `$ref`.
.changeset/mastra-output-schema-nullable.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/mastra': patch
3 ----
4 -
5 -Relax the Mastra provider output schema so real third-party API responses are no longer rejected by Mastra's output validation (which dropped the data and substituted an error). Before compilation the output schema is made lenient: every typed node becomes nullable, objects allow extra keys (`additionalProperties: true`), `enum`/`const` are widened to also admit `null`, and `required` is dropped (APIs omit unset fields rather than returning `null` for them). All of these only widen what validates, so previously-valid output is unaffected.
.changeset/quiet-rules-cheer.md deleted
-9
@@ -1,9 +0,0 @@
1 ----
2 -'@composio/core': minor
3 ----
4 -
5 -Remove the deprecated `uuid` field from the auth config retrieve/list response type.
6 -
7 -The platform has removed the deprecated V1/V2 UUID-mirror field from V3 API responses (it was a mirror of the canonical nanoid `id`). The SDK no longer reads or re-exposes `uuid` on `AuthConfigRetrieveResponse` (and therefore on the items of `AuthConfigListResponse`).
8 -
9 -This is technically a breaking change to the SDK response type: consumers should use `id` instead of `uuid`. The `expectedInputFields` field is unaffected — it remains a top-level field on the API response.
.changeset/virtual-compiler-host-resolution.md deleted
-5
@@ -1,5 +0,0 @@
1 ----
2 -'@composio/cli': patch
3 ----
4 -
5 -Fix virtual TypeScript file resolution used by CLI type generation so in-memory imports resolve consistently during transpilation and validation.
.changeset/zod-schema-compat.md deleted
-6
@@ -1,6 +0,0 @@
1 ----
2 -'@composio/core': patch
3 -'@composio/claude-agent-sdk': patch
4 ----
5 -
6 -Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it.
ts/packages/cli-keyring/CHANGELOG.md new
+7
@@ -0,0 +1,7 @@
1 +# @composio/cli-keyring
2 +
3 +## 0.2.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
ts/packages/cli-keyring/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/cli-keyring",
3 - "version": "0.1.0",
3 + "version": "0.2.0",
4 "description": "Cross-platform OS credential store access for the Composio CLI (macOS Keychain, Linux Secret Service).",
5 "main": "src/index.ts",
6 "private": true,
ts/packages/cli-local-tools/CHANGELOG.md
+19
@@ -1,5 +1,24 @@
1 # @composio/cli-local-tools
2
3 +## 0.1.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 +### Patch Changes
10 +
11 +- Updated dependencies [552859a]
12 +- Updated dependencies [a0bef5d]
13 +- Updated dependencies [23f9053]
14 +- Updated dependencies [dfd7a08]
15 +- Updated dependencies [507318d]
16 +- Updated dependencies [025a657]
17 +- Updated dependencies [6a4cb54]
18 +- Updated dependencies [4b76dbf]
19 +- Updated dependencies [cbbad15]
20 + - @composio/core@0.12.0
21 +
22 ## 0.0.5
23
24 ### Patch Changes
ts/packages/cli-local-tools/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/cli-local-tools",
3 - "version": "0.0.5",
3 + "version": "0.1.0",
4 "private": true,
5 "description": "Local tool and toolkit declarations for the Composio CLI.",
6 "type": "module",
ts/packages/cli/CHANGELOG.md
+27
@@ -1,5 +1,32 @@
1 # @composio/cli
2
3 +## 0.3.0
4 +
5 +### Minor Changes
6 +
7 +- a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.
8 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
9 +
10 +### Patch Changes
11 +
12 +- 5f004ff: Drop `COMPOSIO_UPSERT_RECIPE` and `COMPOSIO_GET_RECIPE` from the CLI meta-tool list. These slugs were removed from `@composio/client` (alpha.74), so listing them broke the type-checked CLI build.
13 +- 23f9053: Remove the unused `ansis` dependency from the CLI. Colored output is already handled by `picocolors`, so `ansis` was a dead production dependency that shipped with the package.
14 +- 446c6f6: Fix virtual TypeScript file resolution used by CLI type generation so in-memory imports resolve consistently during transpilation and validation.
15 +- Updated dependencies [552859a]
16 +- Updated dependencies [a0bef5d]
17 +- Updated dependencies [23f9053]
18 +- Updated dependencies [dfd7a08]
19 +- Updated dependencies [507318d]
20 +- Updated dependencies [025a657]
21 +- Updated dependencies [6a4cb54]
22 +- Updated dependencies [4b76dbf]
23 +- Updated dependencies [cbbad15]
24 + - @composio/core@0.12.0
25 + - @composio/json-schema-to-zod@0.2.0
26 + - @composio/ts-builders@0.2.0
27 + - @composio/cli-keyring@0.2.0
28 + - @composio/cli-local-tools@0.1.0
29 +
30 ## 0.2.32
31
32 ### Patch Changes
ts/packages/cli/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/cli",
3 - "version": "0.2.32",
3 + "version": "0.3.0",
4 "description": "Composio CLI",
5 "main": "./dist/bin.mjs",
6 "private": true,
ts/packages/core/CHANGELOG.md
+79
@@ -1,5 +1,84 @@
1 # @composio/core
2
3 +## 0.12.0
4 +
5 +### Minor Changes
6 +
7 +- a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.
8 +- dfd7a08: Add per-request cancellation to public SDK methods via a new `ComposioRequestOptions` (`{ signal?: AbortSignal }`) trailing argument, plus a typed `ComposioRequestCancelledError` for detecting caller-initiated aborts.
9 +
10 + Without this, a slow `tools.get` or `tools.execute` had no way to be cancelled — a 100s search would block the calling agent indefinitely. The new shape:
11 +
12 + ```typescript
13 + try {
14 + const tools = await composio.tools.get(
15 + 'user_1',
16 + { search: 'send email', limit: 50 },
17 + { signal: AbortSignal.timeout(5_000) }
18 + );
19 + } catch (err) {
20 + if (err instanceof ComposioRequestCancelledError) {
21 + return;
22 + }
23 + throw err;
24 + }
25 + ```
26 +
27 + The signal is forwarded to the underlying `@composio/client` fetch. Any abort error (`APIUserAbortError`, `AbortError`, or `DOMException(name='AbortError')`) coming back is normalized to `ComposioRequestCancelledError` so callers can `instanceof`-detect cancellation without unwrapping nested causes. Catch-and-wrap paths in `tools.execute` / `tools.getRawComposioToolBySlug` / `toolkits.get` re-throw the cancellation error rather than remapping it to `ComposioToolExecutionError` / `ComposioToolNotFoundError` / `ComposioToolkitFetchError`.
28 +
29 + Wired through on:
30 + - **Tools**: `get`, `getRawComposioTools`, `getRawComposioToolBySlug`, `getRawToolRouterSessionTools`, `execute`, `executeSessionTool`, `getToolsEnum`, `getInput`, `proxyExecute`
31 + - **Toolkits**: `get`, `listCategories`
32 + - **AuthConfigs**: `list`, `create`, `get`, `update`, `delete`, `updateStatus`, `enable`, `disable`
33 + - **ConnectedAccounts**: `list`, `get`, `delete`, `refresh`, `updateStatus`, `enable`, `disable`, `update`
34 + - **Triggers**: `listActive`, `create`, `update`, `delete`, `enable`, `disable`, `listTypes`, `getType`, `listEnum`
35 + - **MCP**: `create`, `list`, `get`, `delete`, `update`, `generate`
36 + - **ToolRouter** (`composio.create` / `composio.use`, `composio.toolRouter.create` / `.use`) — long-running session-creation paths
37 + - **ToolRouterSession**: `authorize`, `toolkits`, `search`, `execute`, `proxyExecute`, `update`
38 +
39 + ### Custom-tool cooperative cancellation
40 +
41 + Native tool execution is cancelled by the SDK (the underlying `fetch` is aborted). Custom tools are different — the SDK can't preempt user-supplied JavaScript. Two affordances are added so callers get sensible behavior anyway:
42 +
43 + 1. **Pre-execute signal check**: if `signal.aborted` is true before the user's `execute` runs, the SDK throws `ComposioRequestCancelledError` and never invokes user code.
44 + 2. **Cooperative signal forwarding**: the same `AbortSignal` is exposed via `SessionContext.signal` for Tool Router custom tools. Long-running implementations can wire `ctx.signal` into their own `fetch` (or any abortable IO) to abort mid-execution; the resulting `AbortError` is normalized to `ComposioRequestCancelledError` by the SDK.
45 +
46 + ```typescript
47 + import { experimental_createTool } from '@composio/core';
48 +
49 + const longRunningFetch = experimental_createTool('LONG_RUNNING_FETCH', {
50 + name: 'Long-running fetch',
51 + description: 'Fetches a URL with cooperative cancellation',
52 + inputParams: z.object({ url: z.string() }),
53 + execute: async (input, ctx) => {
54 + // Pass ctx.signal into fetch so a session.execute(...) abort cancels
55 + // the in-flight HTTP request mid-flight.
56 + const resp = await fetch(input.url, { signal: ctx.signal });
57 + return { result: await resp.json() };
58 + },
59 + });
60 + ```
61 +
62 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
63 +- 4b76dbf: Remove the deprecated `uuid` field from the auth config retrieve/list response type.
64 +
65 + The platform has removed the deprecated V1/V2 UUID-mirror field from V3 API responses (it was a mirror of the canonical nanoid `id`). The SDK no longer reads or re-exposes `uuid` on `AuthConfigRetrieveResponse` (and therefore on the items of `AuthConfigListResponse`).
66 +
67 + This is technically a breaking change to the SDK response type: consumers should use `id` instead of `uuid`. The `expectedInputFields` field is unaffected — it remains a top-level field on the API response.
68 +
69 +### Patch Changes
70 +
71 +- 552859a: Expose `search` and `showDisabled` filters on `authConfigs.list()`.
72 +- 23f9053: Replace `chalk` with `picocolors` for colored error and log output. The two render identically, but `picocolors` is a fraction of the size (~0.8 kB gzipped vs chalk's much larger footprint), shrinking the bundled package.
73 +- 507318d: Add a provider-agnostic JSON-schema property-key sanitizer: `sanitizeSchemaPropertyKeys(schema, policy)`, `restoreOriginalKeys(value, mapping)`, `mappingHasRenames(mapping)`, and the `KeyMapping` / `KeySanitizationPolicy` types.
74 +
75 + Some providers constrain the characters and length of tool `input_schema` property keys and reject the whole request on a single violation. This utility rewrites offending keys to conforming aliases (recursing through `properties`, array `items`/`prefixItems`, the composition keywords `allOf`/`anyOf`/`oneOf` and `not`/`if`/`then`/`else`, plus `additionalProperties`/`patternProperties`/`$defs`/`contains`) and records a schema-shaped reverse mapping so the original parameter names can be restored before execution. The _constraint_ is injected as a `KeySanitizationPolicy`, so the traversal, collision handling, prototype safety, and depth cap stay provider-agnostic. The `@composio/anthropic` provider now consumes it.
76 +
77 +- 6a4cb54: Preserve root `$defs` / `definitions` blocks on tool parameter schemas and dereference them in the Node file modifier, so auto file upload/download detection works when `file_uploadable` or `file_downloadable` is hidden behind an internal `$ref`.
78 +- cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it.
79 +- Updated dependencies [025a657]
80 + - @composio/json-schema-to-zod@0.2.0
81 +
82 ## 0.11.0
83
84 ### Minor Changes
ts/packages/core/package.json
+1 -1
@@ -1,7 +1,7 @@
1 {
2 "name": "@composio/core",
3 "type": "module",
4 - "version": "0.11.0",
4 + "version": "0.12.0",
5 "description": "",
6 "main": "src/index.ts",
7 "publishConfig": {
ts/packages/json-schema-to-zod/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/json-schema-to-zod
2
3 +## 0.2.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.1.20
10
11 ### Patch Changes
ts/packages/json-schema-to-zod/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/json-schema-to-zod",
3 - "version": "0.1.20",
3 + "version": "0.2.0",
4 "description": "",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/anthropic/CHANGELOG.md
+23
@@ -1,5 +1,28 @@
1 # @composio/anthropic
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 +### Patch Changes
10 +
11 +- 507318d: Harden the Anthropic tool property-key sanitizer:
12 +
13 + - **Broader schema coverage.** Illegal keys are now sanitized wherever they appear in a tool schema — under the composition keywords (`allOf`/`anyOf`/`oneOf`, `not`/`if`/`then`/`else`), `prefixItems` tuples, `additionalProperties`/`patternProperties`, and `$defs`/`definitions` — not just top-level `properties` and array `items`. Previously a single illegal key under one of these would still 400 the entire request. Renames inside composition keywords are restored correctly (they fold into the value level they share).
14 + - **`$ref` keys restored.** `wrapTool` now dereferences internal `$ref`/`$defs` (leniently — a dangling ref degrades to a permissive schema instead of throwing) before sanitizing, so keys reachable only through a reference are both made compliant and restored. Only genuinely dynamic positions (`additionalProperties`, `patternProperties`, `contains`) remain rewrite-only.
15 + - **Shared core implementation.** The traversal/restoration mechanism now lives in `@composio/core` (`sanitizeSchemaPropertyKeys` / `restoreOriginalKeys`); this provider supplies only the Anthropic key constraint as a policy, reusing core's prototype-pollution guard and depth cap.
16 + - **Prototype-safe key restoration.** Reverse-mapping lookups and the rebuilt argument object are now prototype-free, so a tool call whose arguments use a key matching an `Object.prototype` member (`__proto__`, `constructor`, `toString`, `hasOwnProperty`, …) no longer throws or silently corrupts the payload sent to the backend. `Object.prototype` is never mutated.
17 + - **Depth cap.** Schema sanitization and key restoration now bound recursion (matching core's JSON-schema walker) so a pathologically deep schema or argument object fails with a clear error instead of overflowing the stack.
18 + - **Empty / all-illegal keys.** A property key that is empty (or made entirely of stripped characters) now becomes a deterministic non-empty alias instead of an empty string, which would itself have violated Anthropic's `{1,64}` length bound.
19 + - **Collision loop.** Replaced a latent non-terminating fixed point in the alias collision resolver with a counter that always makes progress.
20 + - **Observability.** The provider now emits `debug` logs when it rewrites a tool's schema keys and when it restores them at execution time, and the wrap-then-execute (same provider instance) contract for key restoration is documented.
21 +
22 +- c90ae95: Sanitize tool `input_schema` property keys that violate Anthropic's `^[a-zA-Z0-9_.-]{1,64}$` constraint before sending tools to the Messages API, then restore the original names when the tool is executed.
23 +
24 + A single non-conforming key previously made Anthropic reject the entire `tools` array with HTTP 400, taking down every other tool in the same request. This commonly happened with OneDrive's Microsoft Graph OData parameters (`$top`, `$filter`, `@microsoft.graph.conflictBehavior`) and with over-long flattened keys from tools such as Zoom. Offending keys are now rewritten to conforming aliases (`$` → `dollar_`, `@` → `at_`, any other illegal character → `_`, keys longer than 64 characters truncated with a deterministic suffix), recursing through nested object `properties` and array `items` schemas. The original parameter names are restored before the call reaches the Composio backend, so the model sees `dollar_top` while the backend still receives `$top`. Schemas whose keys already conform are left unchanged.
25 +
26 ## 0.9.3
27
28 ### Patch Changes
ts/packages/providers/anthropic/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/anthropic",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "Non-Agentic Provider for Anthropic in Composio SDK",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/claude-agent-sdk/CHANGELOG.md
+10
@@ -1,5 +1,15 @@
1 # @composio/claude-code-agents
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 +### Patch Changes
10 +
11 +- cbbad15: Improve Zod compatibility at the SDK schema boundary. Custom tools now convert both `zod/v3` and Zod v4 schemas to JSON Schema correctly instead of degrading Zod v4 object schemas to empty schemas. `@composio/core` now exposes `jsonSchemaToZodShape` via `@composio/core/utils/json-schema`, and the Claude Agent SDK provider uses that core subpath instead of converting to a full Zod object and casting `.shape` out of it.
12 +
13 ## 0.9.3
14
15 ### Patch Changes
ts/packages/providers/claude-agent-sdk/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/claude-agent-sdk",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "Composio provider for Claude Agent SDK",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/cloudflare/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/cloudflare
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/cloudflare/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/cloudflare",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/google/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/google
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/google/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/google",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "Google GenAI Provider for Composio SDK",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/langchain/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/langchain
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/langchain/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/langchain",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "",
5 "main": "dist/index.js",
6 "type": "module",
ts/packages/providers/llamaindex/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/llamaindex
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/llamaindex/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/llamaindex",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "Agentic Provider for llamaindex in Composio SDK",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/mastra/CHANGELOG.md
+10
@@ -1,5 +1,15 @@
1 # @composio/mastra
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 +### Patch Changes
10 +
11 +- aaabf5e: Relax the Mastra provider output schema so real third-party API responses are no longer rejected by Mastra's output validation (which dropped the data and substituted an error). Before compilation the output schema is made lenient: every typed node becomes nullable, objects allow extra keys (`additionalProperties: true`), `enum`/`const` are widened to also admit `null`, and `required` is dropped (APIs omit unset fields rather than returning `null` for them). All of these only widen what validates, so previously-valid output is unaffected.
12 +
13 ## 0.9.3
14
15 ### Patch Changes
ts/packages/providers/mastra/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/mastra",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "Agentic Provider for mastra in Composio SDK",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/openai-agents/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/openai-agents
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/openai-agents/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/openai-agents",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/openai/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/openai
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/openai/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/openai",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/providers/vercel/CHANGELOG.md
+6
@@ -1,5 +1,11 @@
1 # @composio/vercel
2
3 +## 0.10.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
8 +
9 ## 0.9.3
10
11 ### Patch Changes
ts/packages/providers/vercel/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/vercel",
3 - "version": "0.9.3",
3 + "version": "0.10.0",
4 "description": "",
5 "main": "src/index.ts",
6 "type": "module",
ts/packages/ts-builders/CHANGELOG.md new
+7
@@ -0,0 +1,7 @@
1 +# @composio/ts-builders
2 +
3 +## 0.2.0
4 +
5 +### Minor Changes
6 +
7 +- 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
ts/packages/ts-builders/package.json
+1 -1
@@ -1,6 +1,6 @@
1 {
2 "name": "@composio/ts-builders",
3 - "version": "0.1.24",
3 + "version": "0.2.0",
4 "description": "Fork of @prisma/ts-builders",
5 "main": "dist/index.mjs",
6 "type": "module",