Skip to content

Conversation

@Tehsmash
Copy link

@Tehsmash Tehsmash commented Nov 20, 2025

Description

This updates the SDK to be A2A v1.0 compliant, all types are generated from the v1.0 a2a.proto. JSONRPC/HTTP+JSON transports are converted to use the a2a types encoded using ProtoJSON directly from the generated types.

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:

  • Follow the CONTRIBUTING Guide.
  • Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
    • Important Prefixes for release-please:
      • fix: which represents bug fixes, and correlates to a SemVer patch.
      • feat: represents a new feature, and correlates to a SemVer minor.
      • feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
  • Ensure the tests and linter pass (Run bash scripts/format.sh from the repository root to format)
  • Appropriate docs were updated (if necessary)

Fixes #559

@holtskinner
Copy link
Member

This is a pretty good start on converting the types generation from the a2a.json to the a2a.proto. My main concern is that this is going to be a breaking change because the existing typing are based on Pydantic models, not Protobuf. This would need to be handled carefully to prevent breaking changes.

This updates the SDK to be A2A v1.0 compliant, all types are generated
from the v1.0 a2a.proto. JSONRPC/HTTP+JSON transports are converted to
use the a2a types encoded using ProtoJSON directly from the generated
types.
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.

[Feat]: Upgrade A2A to v1.0

2 participants