Changelog

September 16, 2025

Toolkit Versioning in SDKs

Composio Toolkit Versioning provides granular control over tool versions across all your integrations. Instead of always using the latest version of tools, developers can now specify exact toolkit versions, ensuring consistent behavior and controlled updates in production environments.

Why Use Toolkit Versioning?

  • Version Stability: Pin specific toolkit versions to avoid unexpected changes in production
  • Controlled Updates: Test new toolkit versions before deploying to production
  • Environment Consistency: Ensure the same toolkit versions across development, staging, and production
  • Rollback Capability: Easily revert to previous toolkit versions if issues arise
  • Fine-grained Control: Set different versions for different toolkits based on your needs

Python SDK (v0.8.11)

Added

  • Toolkit Versioning Support: New toolkit_versions parameter for controlling tool versions
    • Added toolkit_versions parameter to Composio class initialization
    • Support for global version setting (e.g., 'latest')
    • Support for per-toolkit version mapping (e.g., {'github': '20250902_00', 'slack': '20250902_00'})
    • Environment variable support with COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_NAME> pattern
    • New toolkit_version.py utility module for version resolution logic

Examples:

1# Global version for all toolkits, only `latest` is supported
2composio = Composio(toolkit_versions='latest')
3
4# Per-toolkit version mapping
5composio = Composio(toolkit_versions={
6    'github': '20250902_00',
7    'slack': '20250902_00',
8    'gmail': '20250901_01'
9})
10
11# Using environment variables
12# Set COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
13composio = Composio()  # Automatically picks up env vars
14
15# Get tools with specific versions
16tools = composio.tools.get('default', {'toolkits': ['github']})

TypeScript SDK (v0.1.52)

Added

  • Toolkit Versioning Support: Added toolkitVersions configuration option
    • New toolkitVersions parameter in Composio class constructor
    • Support for global version string or per-toolkit version mapping
    • Environment variable parsing with getToolkitVersionsFromEnv() utility
    • Enhanced getRawComposioToolBySlug() method for version-specific tool retrieval
    • Version-aware tool filtering and search capabilities

Examples:

1// Global version for all toolkits
2const composio = new Composio({
3  toolkitVersions: '20250902_00'
4});
5
6// Per-toolkit version mapping
7const composio = new Composio({
8  toolkitVersions: {
9    'github': '20250902_00',
10    'slack': '20250902_00',
11    'gmail': '20250901_01'
12  }
13});
14
15// Using environment variables
16// Set COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
17const composio = new Composio(); // Automatically picks up env vars
18
19// Get specific tool version
20const tool = await composio.tools.getRawComposioToolBySlug(
21  'GITHUB_GET_REPO', 
22);
23
24// Get tools with version-aware filtering
25const tools = await composio.tools.get('default', {
26  toolkits: ['github'],
27  limit: 10
28});

Key Benefits

  • Environment Variables: Set COMPOSIO_TOOLKIT_VERSION_<TOOLKIT_NAME>=<VERSION> for automatic version resolution
  • Flexible Configuration: Choose between global versions or per-toolkit version mapping
  • Backward Compatibility: Existing code works unchanged - versioning is opt-in
  • Version Fallback: Automatically falls back to ‘latest’ when no version is specified
  • Cross-Platform Consistency: Identical developer experience across Python and TypeScript

Version Format

Toolkit versions follow the format: YYYYMMDD_NN (e.g., 20250902_00) or use 'latest' for the most recent version only supported at global scope and not individual toolkit level.

Environment Variables

$# Set specific versions for different toolkits
>export COMPOSIO_TOOLKIT_VERSION_GITHUB=20250902_00
>export COMPOSIO_TOOLKIT_VERSION_SLACK=20250902_00
>export COMPOSIO_TOOLKIT_VERSION_GMAIL=20250901_01

Migration Note

This feature is fully backward compatible. Existing code will continue to work without changes, using the latest versions by default. To enable versioning, simply add the toolkit_versions parameter during SDK initialization.

Additional Updates

  • Package Updates: Bumped all Python provider packages to v0.8.10
  • Documentation: Enhanced API documentation with versioning examples
  • Testing: Added comprehensive test coverage (400+ new test cases) for versioning functionality
  • Examples: New versioning examples demonstrating practical usage patterns