Skip to content

Commit 7f9e179

Browse files
committed
Remove duplicated disclaimers
1 parent 924c3f9 commit 7f9e179

1 file changed

Lines changed: 0 additions & 11 deletions

File tree

  • docs/migrations/v0_3_to_v1_0/database

docs/migrations/v0_3_to_v1_0/database/README.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,4 @@ The v1.0 database migration involves:
2121
1. **Schema Updates**: Adding `protocol_version`, `owner`, and `last_updated` columns to the `tasks` and `push_notification_configs` tables.
2222
2. **Storage Model**: Transitioning from Pydantic-based JSON to Protobuf-based JSON serialization for better interoperability and performance.
2323

24-
### Rollback & Safety
25-
> [!IMPORTANT]
26-
>
27-
> **Data Backup**: Always perform a full snapshot of your database before starting the migration.
28-
> **Rollback**: To revert the schema, use `uv run a2a-db downgrade -1`.
29-
30-
### Verification
31-
To verify the migration was successful:
32-
- Tables should be updated with new columns: owner, protocol_version, last_updated.
33-
- Inspect the `protocol_version` column in the `tasks` table; entries created before the migration should have `protocol_version` set to `NULL`, entries created during the migration should have `protocol_version` set to `0.3` (if using the zero-downtime migration strategy) and entries created after the migration should have `protocol_version` set to `1.0`.
34-
3524
---

0 commit comments

Comments
 (0)