Toolkit versioning migration
Migrate to the new toolkit versioning system
Starting with Python SDK v0.9.0 and TypeScript SDK v0.2.0, manual tool execution requires explicit version specification. This is a breaking change from earlier versions where toolkit versioning was optional.
Breaking change
Manual tool execution now requires explicit version specification. The tools.execute() method will fail without a version.
Before (will fail)
After (required)
Choose one of three migration strategies:
Option 1: Configure version at SDK level
Option 2: Pass version with each execution
Option 3: Use environment variables
Migration checklist
- Audit your code: Find all
tools.execute()calls in your codebase - Choose a strategy: Select one of the three options above based on your needs
- Test thoroughly: Verify tools work correctly with pinned versions
- Deploy gradually: Roll out changes incrementally to minimize risk
Temporary workaround
During migration, you can temporarily skip version checks (not recommended for production):
The dangerouslySkipVersionCheck flag is only for migration or debugging. Never use in production.
Next steps
For complete documentation on toolkit versioning, including best practices and advanced configuration, see Toolkit versioning.