Release: update version #2077

haxzie · 2025-10-22T05:34:25Z

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

Releases

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Minor Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience

Patch Changes

Updated dependencies [157bf7b]
- @composio/[email protected]

@composio/[email protected]

Patch Changes

157bf7b: Fix array parsing

@composio/[email protected]

Patch Changes

157bf7b: ### Added
- Version validation for manual tool execution: Tools now require explicit toolkit version specification when executing manually to prevent unexpected behavior from latest version changes
- New dangerously_skip_version_check parameter (Python) / dangerouslySkipVersionCheck (TypeScript): Optional flag to bypass version validation (use with caution)
- ToolVersionRequiredError exception (Python): Raised when attempting to execute tools with latest version without skip flag, includes helpful error messages with 4 possible fixes
- ComposioToolVersionRequiredError error (TypeScript): Parallel implementation for TypeScript SDK with detailed error context and resolution suggestions
- Comprehensive test coverage: Added 19 new test methods in Python covering all tool execution scenarios including version resolution, error handling, modifiers, and environment variables
Changed
- Tool execution behavior: Manual execution via tools.execute() now validates toolkit versions before API calls
- Agentic provider flows: Automatically set dangerously_skip_version_check=True internally to maintain backward compatibility for framework integrations
- Instance-level version resolution: Both execute() and _execute_tool() methods now consistently resolve versions from instance-level toolkit_versions configuration
- Modifier support: Added dangerously_skip_version_check to modifier parameter types for complete flow coverage
- Test version format: Updated all test files to use production date-based version format (20251201_XX) instead of semantic versioning
Fixed
- Consistent version handling: Removed toolkit_versions parameter from _execute_tool() in favor of instance-level configuration, ensuring consistent version resolution across the SDK
- Code formatting: Applied ruff formatting to all modified Python files
- Array parsing to ZodSchema: Fixes in json-schema-to-zod to parse array without properties and with properties
Migration Guide

When manually executing tools, you must now specify toolkit versions:

Option 1: Pass explicit version parameter
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    version="20251201_01"
)
```
Option 2: Configure at SDK initialization
```
tools = Tools(client, provider,
    toolkit_versions={"github": "20251201_01"}
)
```
Option 3: Use environment variables
```
export COMPOSIO_TOOLKIT_VERSION_GITHUB=20251201_01
```
Option 4: Skip validation (not recommended)
```
tools.execute("GITHUB_CREATE_ISSUE",
    arguments={...},
    dangerously_skip_version_check=True
)
```
Developer Notes
- Agentic framework integrations (LangChain, CrewAI, etc.) are not affected as they automatically use the skip flag
- The latest version can still be used with the skip flag, but specific versions are strongly recommended
- Error messages include all available resolution options for better developer experience
Updated dependencies [157bf7b]
- @composio/[email protected]

Note

Enforces explicit toolkit versions for manual tool execution with optional skip flags, adds error classes, improves TS SDK execution performance, and publishes coordinated package version bumps (incl. array parsing fix).

Core/SDK (@composio/[email protected]):
- Enforce toolkit version validation for manual tools.execute(); add dangerously_skip_version_check support and new error types (ToolVersionRequiredError/ComposioToolVersionRequiredError).
- Resolve versions from instance-level toolkit_versions; update modifier types; validate before API calls.
- Add extensive tests for execution flows.
TypeScript SDK performance:
- Remove redundant connected-account checks to speed up tool execution.
Providers:
- Bump @composio/{anthropic,cloudflare,google,langchain,llamaindex,mastra,openai,openai-agents} to 0.2.0; update peer deps to @composio/[email protected].
Utilities:
- @composio/[email protected]: fix array parsing.
Vercel Provider:
- Patch bump to 0.2.12; depends on @composio/[email protected].
Docs:
- Add fern/pages/src/changelog/10-22-25.md summarizing behavior, breaking change, and migration steps.

^{Written by Cursor Bugbot for commit c6827bb. This will update automatically on new commits. Configure here.}

ts/packages/providers/anthropic/package.json

github-actions · 2025-10-22T05:55:09Z

Preview your docs: https://composio-preview-a6ebe14d-7624-4823-a190-574d33d394a8.docs.buildwithfern.com

Release: update version

17720f3

This comment was marked as outdated.

Sign in to view

haxzie added 2 commits October 22, 2025 11:17

Fix package versioning

b1b4932

Add changelog

c6827bb

haxzie requested a review from Sushmithamallesh as a code owner October 22, 2025 05:50

cursor bot reviewed Oct 22, 2025

View reviewed changes

ts/packages/providers/anthropic/package.json Show resolved Hide resolved

haxzie merged commit 263936c into next Oct 22, 2025
9 checks passed

haxzie deleted the changeset-release/next branch October 22, 2025 05:55

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Release: update version #2077

Release: update version #2077

Uh oh!

haxzie commented Oct 22, 2025 •

edited

Loading

Uh oh!

This comment was marked as outdated.

Uh oh!

Uh oh!

github-actions bot commented Oct 22, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Release: update version #2077

Release: update version #2077

Uh oh!

Conversation

haxzie commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Releases

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Minor Changes

Changed

Fixed

Migration Guide

Developer Notes

Patch Changes

@composio/[email protected]

Patch Changes

@composio/[email protected]

Patch Changes

Changed

Fixed

Migration Guide

Developer Notes

Uh oh!

This comment was marked as outdated.

haxzie commented Oct 22, 2025 •

edited

Loading