Migration Guide
Guide for upgrading between Kubiya Workflow SDK versions
Migration Guide
This guide helps you upgrade between major versions of the Kubiya Workflow SDK.
Migrating from 1.x to 2.0
Breaking Changes
Version 2.0 includes some breaking changes. Please review carefully before upgrading.
1. Default Runner Changed
The default runner has changed from core-testing-2
to auto
:
2. Client API Updates
New methods added to the Client class:
3. Streaming Format
SSE streaming now requires the native_sse
parameter:
New Features
AI-Powered Workflow Generation
SDK Server
Migration Steps
Update Dependencies
Update Runner References
Search for runner="core-testing-2"
and replace with runner="auto"
or remove the parameter.
Test Streaming
Test your streaming code to ensure it handles the new SSE format correctly.
Add API Keys
If using ADK provider, add the required API keys:
Migrating from 0.x to 1.0
Breaking Changes
- Workflow Definition: Changed from dict to object-based
- Step Dependencies: Now use explicit
depends
parameter - Execution API: New streaming interface
Example Migration
Best Practices
Test Thoroughly
Always test workflows in a staging environment before upgrading production
Backup Workflows
Export your workflow definitions before upgrading
Update Gradually
Migrate workflows one at a time rather than all at once
Monitor Execution
Watch for any changes in execution behavior after upgrade
Getting Help
If you encounter issues during migration:
- Check the Changelog for detailed changes
- Review the API Reference
- Join our Discord community
- Contact support at support@kubiya.ai