[Feat]: Upgrade A2A to v1.0 #559
Copy link
Copy link
Description
Is your feature request related to a problem? Please describe.
A2A v1.0 is coming, we need to upgrade the SDK to support that specification
Describe the solution you'd like
Refactor the SDK to use the new v1.0 version of the specification
Describe alternatives you've considered
N/A
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
refactor!: upgrade SDK to A2A 1.0 specs (#572)
ishymko commentedon Feb 2, 2026
Hey @muscariello, @Tehsmash, wanted to check on #572 (great work BTW, thanks a lot!). If I understand correctly the next step is to merge 1.0-a2a_proto_refactor into 1.0-dev? Will you be able to take it? Please let me know if anything is needed and also send PRs my way.
Thank you!
FYI: I've merged
maininto1.0-devrecently (#658) and enabled linter and unit tests in CI.refactor!: upgrade SDK to A2A 1.0 specs (a2aproject#572)
refactor!: Update to Protocol v1.0.0-rc and fix all tests (#665)
ishymko commentedon Feb 17, 2026
Hey @muscariello FYI
1.0-devis updated and now contains proto refactor changes (see #696 and #697).I will be looking and testing further from
1.0-dev, will post updates here in the comments.fix: fix bad "list tasks" merge for JSON-RPC (#698)
chore: bring back removed files
8 remaining items
chore: regenerate latest types from A2A main (#712)
google.rpc.Statusformatted JSON objects for error response bodies in HTTP+JSON mapping #722fix: remove v1 from HTTP+REST/JSON paths (#765)
fix: use correct REST path for Get Extended Agent Card operation
fix: use correct REST path for Get Extended Agent Card operation (#769)
protocol_versioncolumn toTaskandPushNotificationConfigmodels and create a migration #787fix: incorporate latest 1.0 proto changes (#788)
protocol_versioncolumn toTaskandPushNotificationConfigmodels and create a migration #787build: use 1.0 tag in buf config (#841)