Skip to content

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

Closed
supreme-gg-gg wants to merge 20 commits into
jetc/feat/a2a-v1-migration-bfrom
jetc/feat/a2a-v1-migration-c
Closed

supreme-gg-gg wants to merge 20 commits into
jetc/feat/a2a-v1-migration-bfrom
jetc/feat/a2a-v1-migration-c

Conversation

@supreme-gg-gg

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

Copy link
Copy Markdown
Contributor

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.

Signed-off-by: Jet Chiang <[email protected]>
Signed-off-by: Jet Chiang <[email protected]>
Signed-off-by: Jet Chiang <[email protected]>
Signed-off-by: Jet Chiang <[email protected]>
Signed-off-by: Jet Chiang <[email protected]>

review and update UI changes

Signed-off-by: Jet Chiang <[email protected]>

pkg lock

Signed-off-by: Jet Chiang <[email protected]>

fixes to ui

Signed-off-by: Jet Chiang <[email protected]>
Signed-off-by: Jet Chiang <[email protected]>

update migration cmd tests from archived branch

Signed-off-by: Jet Chiang <[email protected]>
@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
@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
@supreme-gg-gg
supreme-gg-gg force-pushed the jetc/feat/a2a-v1-migration-b branch 2 times, most recently from fa045c2 to 60a1f05 Compare May 29, 2026 16:17
@github-actions

Copy link
Copy Markdown

This pull request has been marked as stale because of no activity in the last 15 days. It will be closed in the next 5 days unless it is tagged "no stalebot" or other activity occurs.

@github-actions github-actions Bot added the stale This issue or PR has become stale label Jun 14, 2026
@github-actions

Copy link
Copy Markdown

This pull request has been closed after 15 days of inactivity and an additional 5 days after being marked as stale.

@github-actions github-actions Bot closed this Jun 19, 2026
EItanya added a commit that referenced this pull request Aug 7, 2026
## Summary

Close #1941 

This PR combines the changes of #1929 and #1936 and migrates all
Kagent's A2A integration surfaces (UI a2a-js client, CLI a2a-go client,
DB and REST API interfaces, declarative ADK in go and python, BYO
frameworks in python) from 0.3 and 1.0 dual-compatible (introduced in
#1921) to strictly v1.0. This paves the way for future work to
consolidate our A2A integration and develop the Kagent v1 APIs.

**This migration is not zero downtime and is not backward compatible,
and is intended to go into the next major version.** There is no
compatibility matrix for this. Your UI/CLI/custom client and all agents
must **ALL** be in v1.0 to work properly.

## Testing

Unit, integration, and E2E tests have been updated and ran successfully.
I have manually tested: using UI and CLI with Go declarative, Python
declarative, and BYO agents on K8s and Substrate.

For context, the A2A migration doc is
[here](https://github.com/a2aproject/a2a-python/tree/main/docs/migrations/v1_0)
(written for python sdk but generally applicable to go and js)

---------

Signed-off-by: Jet Chiang <[email protected]>
@EItanya
EItanya deleted the jetc/feat/a2a-v1-migration-c branch November 10, 2026 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale This issue or PR has become stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant