The A2A SDK v1.0 introduces significant updates to the database persistence layer, including a new schema for tracking task ownership and protocol versions. This guide provides the necessary steps to migrate your database from v0.3 to the v1.0 persistence model without data loss.
Depending on your application's availability requirements, choose one of the following paths:
| Strategy | Downtime | Complexity | Best For |
|---|---|---|---|
| Simple Migration | Short (Restart) | Low | Single-instance apps, non-critical services. |
| Zero Downtime Migration | None | Medium | Multi-instance, high-availability production environments. |
The v1.0 database migration involves:
- Schema Updates: Adding the
protocol_version,owner, andlast_updatedcolumns to thetaskstable, and theprotocol_versionandownercolumns to thepush_notification_configstable. - Storage Model: Transitioning from Pydantic-based JSON to Protobuf-based JSON serialization for better interoperability and performance.