Support A2A 1.0
维护者通常 1 天内回复
@hemasekhar-p 已经在做这个了。
开始于 2026年5月13日。
评估
这个 Issue 还没有评估数据。
描述
🔴 Required Information
Is your feature request related to a specific problem?
Version 1.0 of the A2A spec was released back in March, which stabilizes the spec but also makes breaking changes from 0.3.x. It would be super helpful for the ADK to support this new spec so that new apps can be developed against it!
Describe the Solution You'd Like
a2aproject/a2a-java is currently in 1.0.0.Beta1 for new spec support. Adopting this new version requires updating calls to match the new API, although it appears most behaviour maps relatively cleanly. The main challenge will be whether the ADK continues to support 0.3.x, there's some discussion about adding compatibility to the new A2A version but it seems uncertain whether it will make it into the first stable version. Without compatibility, agents upgrading to the new ADK version would also break any older agents connecting to it until they upgraded to the new spec - I'm unsure if this is acceptable.
Impact on your work
We are building out a new agent using the ADK, and would like to support the new spec out of the gate, rather than having to update in future. In addition, the a2a-java:0.3.3 version has a bug where tools returning an RxJava Single which hop threads cause the stream to end after the tool call. This bug appears to be fixed with the new AgentEmitter in 1.0.
Willingness to contribute
Yes - I have some POC work updating the google-adk-a2a code to the new A2A version, and am willing to submit a PR if approved!
🟡 Recommended Information
Describe Alternatives You've Considered
- Continue with 0.3.x: need to reach out to the
a2a-javaproject regarding the bug found and see if they would be willing to backport a fix to 0.3. Eventually, the ADK will need to support v1.0 though.
Proposed API / Implementation
For the most basic implementation, calls just need to be updated to the new names exposed in the A2A SDK. If multiple versions of the spec are to be supported though, this may be more complex.
Additional Context
N/A
- 主要语言
- Java
- 星标
- 1.7k
- 派生
- 433
- 平均合并
- 3 天 13 小时
- 30 天内合并 PR
- 42
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
google/adk-java 的其他 Issue
-
GeminiUtil placeholder user turn ("Continue output. DO NOT look at this line ...") is flagged by prompt injection filters可能已有人在做 @hemasekhar-p 于 3 天前认领。 未关闭needs review
难度 2/5 1-3 小时 新手友好度 76/100
google/adk-java#1628 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
[spring-ai] ToolConverter silently drops enum and items from tool parameter schemas可能已有人在做 @hirematha 于 6 天前认领。 未关闭needs review
难度 2/5 1-3 小时 新手友好度 76/100
google/adk-java#1609 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
[spring-ai] Streaming responses ending with CJK punctuation (。！？) are misclassified as partial and never persisted to the session可能已有人在做 @hirematha 于 6 天前认领。 未关闭needs review
难度 2/5 1-3 小时 新手友好度 84/100
google/adk-java#1608 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
FirestoreSessionService compares event timestamps as text, reordering or skipping same-second events未关闭
难度 3/5 1-2 天 新手友好度 50/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
-
难度 2/5 1-3 小时 新手友好度 64/100
utopia-rise/godot-jvm#1004 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
spring-projects/spring-grpc#442 ·
-
Expose numberOfPermits in RateLimiterEvent.toString() and the ratelimiterevents actuator DTO可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
resilience4j/resilience4j#2547 ·
维护者通常 9 天内回复
-
Clock.MakeDate continues execution and returns a rolled-over instant after dispatching error on invalid date可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 1/5 1 小时以内 新手友好度 82/100
mit-cml/appinventor-sources#4155 ·
维护者通常 1 天内回复