Skip to content

[DNM] Migrate from A2A v0 to v1 (part 3)#1936

Draft
supreme-gg-gg wants to merge 1 commit into
jetc/feat/a2a-v1-migration-bfrom
jetc/feat/a2a-v1-migration-c
Draft

[DNM] Migrate from A2A v0 to v1 (part 3)#1936
supreme-gg-gg wants to merge 1 commit into
jetc/feat/a2a-v1-migration-bfrom
jetc/feat/a2a-v1-migration-c

Conversation

@supreme-gg-gg
Copy link
Copy Markdown
Contributor

@supreme-gg-gg supreme-gg-gg commented May 27, 2026

The 3rd of 3 PRs for A2A v0 to v1 zero downtime migration. This will go into release 0.12.0. In release 0.11.0, we have added full support for A2A v1 in UI, agent runtimes, CLI, controller, DB writes and read, so in this PR we will cleanup v0 artifacts in go/core:

  • Removes conversion code between v0 and v1 data
  • Removes migration CLI
  • Removes trpc-a2a-go completely from the codebase
  • Switches database write and read to v1 strict and handler routes to v1 strict, advertise only v1 agent card and routes

After upgrading to 0.12.0, kagent will be A2A v1 only.

Do not upgrade to this release from versions earlier than 0.11.0. Do not upgrade to this release if you have legacy v0 data and have not yet run the migration CLI in 0.11.0.

@supreme-gg-gg supreme-gg-gg force-pushed the jetc/feat/a2a-v1-migration-b branch from 6685367 to 4a76753 Compare May 27, 2026 16:59
Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>
@supreme-gg-gg supreme-gg-gg force-pushed the jetc/feat/a2a-v1-migration-c branch from 0217efb to 7a29061 Compare May 27, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant