[DNM] Migrate from A2A v0 to v1 (part 3)#1936
Draft
supreme-gg-gg wants to merge 1 commit into
Draft
Conversation
6685367 to
4a76753
Compare
Signed-off-by: Jet Chiang <pokyuen.jetchiang-ext@solo.io>
0217efb to
7a29061
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:trpc-a2a-gocompletely from the codebaseAfter 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.