Skip to content

[FEATURE] A2A migration from v0 to v1Β #1941

Closed as not planned
Closed as not planned

Description

@supreme-gg-gg

πŸ“‹ Prerequisites

πŸ“ Feature Summary

A2A migration from v0 to v1

❓ Problem Statement / Motivation

Get rid of old deprecated A2A version (v0.3) and unofficial trpc-a2a-go library in go/core (see #1336) and replace everything with official A2A v1 SDKs in python, js, and go.

πŸ’‘ Proposed Solution

a2a-migration-plan.md

πŸ”„ Alternatives Considered

See above docs

🎯 Affected Service(s)

Controller, CLI, UI, Python and Go agent runtimes, Python BYO SDKs, CRDs, potentially helm charts

πŸ“š Additional Context

3 PRs for each release documented above

#1921
#1929
#1936

πŸ™‹ Are you willing to contribute?

  • I am willing to submit a PR for this feature

Activity

  1. iplay88keys commented on May 28, 2026

    @iplay88keys
    Contributor

    I think we should have the data migration be automatic as opposed to a manual process. It would be a better user experience.

  2. added a commit that references this issue on Aug 7, 2026
    e4c1078
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

staleThis issue or PR has become stale

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions