Repository navigation
fix(a2a-agent-cards): use A2A 1.0 method names and card fields - #259
Merged
Merged
Conversation
A2A 1.0 renamed the JSON-RPC methods (message/send -> SendMessage, message/stream -> SendStreamingMessage) and moved protocolVersion from the top level of the agent card into each supportedInterfaces entry. The page still taught the 0.3 names and a top-level protocolVersion. The worked-example callout now says honestly that our own endpoint has not caught up yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
98ebda6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e4de7e3e.specification-website.pages.dev |
| Branch Preview URL: | https://fix-a2a-v1-method-names-2026.specification-website.pages.dev |
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
1 participant
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 A2A page described 0.3 method names while presenting the protocol as 1.0. It now uses
SendMessage,SendStreamingMessageandGetTask, places the protocol version on each supported interface, and distinguishes that value from the agent's own version.The migration guidance explains that aliases alone do not preserve compatibility: clients also need the correct message roles, part representation, request/response formats and discovery card. It links to the official migration guide and includes a
changedchangelog entry dated 15 October 2026; re-date that entry if the merge lands later.The worked-example callout identifies the existing endpoint's remaining differences from 1.0. This PR changes the guidance; a protocol implementation migration remains separate. Status stays
optional.A shared lockfile security refresh updates sharp, http-cache-semantics, smol-toml and source-map-js within the existing dependency requirements, including sharp in the MCP package, so the existing audit gates can pass.
Validation: production build and generated HTML/Markdown/llms-full/changelog RSS checked; lint, formatting, Agent Skill integrity, MCP protocol assertions and type-check pass. Both dependency audits report zero vulnerabilities. All fresh PR checks pass; the scheduled-only external-link check is skipped.