chore(docs): update migration README.md#1003
Merged
msampathkumar merged 18 commits intoa2aproject:mainfrom Apr 22, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the v1.0 migration guide for the A2A Python SDK, adding a 'Why Upgrade' section and expanding documentation for server setup and helper utilities. It also clarifies the transition from Pydantic to Protobuf. Review feedback pointed out factual errors regarding the version 0.3 structure of AgentCard and an incorrect statement about the renaming of the capabilities field.
Expanded explanation of types migration to include alignment with A2A spec and ProtoJSON standard.
… v1.0 migration guide" This reverts commit b70018e.
sokoliva
approved these changes
Apr 22, 2026
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.
Description
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
fix:which represents bug fixes, and correlates to a SemVer patch.feat:represents a new feature, and correlates to a SemVer minor.feat!:, orfix!:,refactor!:, etc., which represent a breaking change (indicated by the!) and will result in a SemVer major.bash scripts/format.shfrom the repository root to format)Fixes #<issue_number_goes_here> 🦕