docs(spec): What changed from v0.3.0 to v1.0 by darrelmiller · Pull Request #1436 · a2aproject/A2A

darrelmiller · 2026-01-30T15:40:53Z

No description provided.

…or A2A Protocol v1.0

gemini-code-assist · 2026-01-30T15:41:12Z

Summary of Changes

Hello @darrelmiller, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

The v1.0 release of the A2A Protocol marks a significant maturation, focusing on standardization, enhanced type safety, improved developer experience, and enterprise-ready features. It introduces formal adherence to industry specifications, refines core data models and operations, and clarifies behavioral semantics, necessitating updates for existing implementations while providing a more robust and consistent foundation for future development.

Highlights

Part Type Unification: The Part object has been completely redesigned, unifying TextPart, FilePart, and DataPart into a single structure and removing the kind discriminator in favor of member-based polymorphism.
Enum Value Standardization: All enum values (e.g., TaskStatus.state, Message.role) have been changed from PascalCase or lowercase to SCREAMING_SNAKE_CASE with type prefixes (e.g., "completed" to "TASK_STATE_COMPLETED").
Agent Card Restructuring: The AgentCard object has undergone significant changes, including the consolidation of interface details into supportedInterfaces[], the addition of agentId and signatures[] for verification, and the relocation of supportsAuthenticatedExtendedCard to capabilities.extendedAgentCard.
Stream Event Discrimination: Stream events (TaskStatusUpdateEvent, TaskArtifactUpdateEvent) no longer use a kind discriminator; instead, their type is determined by a wrapper-based JSON member name (e.g., taskStatusUpdate or taskArtifactUpdate).
Cursor-Based Pagination: The ListTasks operation now uses cursor-based pagination for improved scalability, replacing the previous page-number-based approach.
New Specifications Adoption: The protocol now formally depends on several industry standards, including RFC 9457 for error details, RFC 8785 for JSON Canonicalization, RFC 7515 for JWS (for Agent Card signatures), and ISO 8601 for timestamp formatting.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request introduces a comprehensive "What's New" document for the A2A Protocol v1.0, which is a great addition for developers migrating from v0.3.0. The document is well-structured and covers the major changes in detail. I've identified a few areas with inconsistencies or inaccuracies that could be improved for clarity. My review includes suggestions to correct a code example, remove a misleading section, and fix minor inconsistencies in terminology and descriptions. Overall, this is a valuable piece of documentation.

docs/whats-new-v1.md

…port and OAuth 2.0 updates

muscariello

LGTM

…rted)

docs/whats-new-v1.md

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>

darrelmiller · 2026-01-30T18:37:57Z

@holtskinner Thank you for the review and suggestions. I have applied your changes.

holtskinner · 2026-02-02T15:51:10Z

@gemini-code-assist review

gemini-code-assist

Code Review

This pull request introduces a comprehensive and well-structured document, docs/whats-new-v1.md, which details the changes from A2A Protocol v0.3.0 to v1.0. The document is thorough, covering major themes, breaking changes, and providing a migration guide for developers. The changes are clearly explained with helpful code examples. I've included a few minor suggestions to improve consistency and clarity in the document. Overall, this is an excellent addition to the project's documentation.

docs/whats-new-v1.md

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Changes below as they appear in the file. - `blocking` flag existed in 0.3: [source](https://a2a-protocol.org/v0.3.0/specification/#712-messagesendconfiguration-object) - `SendMessage`: remove "MAY return Message"/"MUST return Task" which are not in the spec, remove service parameters mention as they are covered above - streaming was specified for gRPC in proto definition as `returns (stream StreamResponse)` - `SubscribeToTask` is not a new operation - blocking has no effect for streaming operations: [source](https://a2a-protocol.org/latest/specification/#322-sendmessageconfiguration) - `TaskNotCancelableError` was mentioned in 0.3: [source](https://a2a-protocol.org/v0.3.0/specification/#82-a2a-specific-errors) - RFC 7515 was mentioned for Agent Card signatures in 0.3: [source](https://a2a-protocol.org/v0.3.0/specification/#556-agentcardsignature-object), kept only RFC 8785 for canonicalization which wasn't - `agentId` field does not exist and never did - extension declarations (AgentExtension object) did not change between [0.3](https://a2a-protocol.org/v0.3.0/specification/#5521-agentextension-object) and [1.0](https://a2a-protocol.org/latest/specification/#444-agentextension) - Mutual TLS existed in 0.3: [source](https://a2a-protocol.org/v0.3.0/specification/#553-securityscheme-object) - subscribing to tasks not originally created via streaming is not a behavior change and is not explicitly mentioned in 1.0 - `token` is not removed from `PushNotificationConfig`: [source](https://a2a-protocol.org/latest/specification/#431-pushnotificationconfig) - `configId` does not exist in `PushNotificationConfig` ([source](https://a2a-protocol.org/latest/specification/#431-pushnotificationconfig)) and `id` was there in 0.3 ([source](https://a2a-protocol.org/v0.3.0/specification/#68-pushnotificationconfig-object)) - `PushNotificationNotSupportedError` existed in 0.3: [source](https://a2a-protocol.org/v0.3.0/specification/#82-a2a-specific-errors) - `SendMessageRequest` example fixed to match the spec - `createdAt` and `lastModified` do not exist in `Task`: [source](https://a2a-protocol.org/latest/specification/#411-task) - changes to nested `Task` objects removed as they are covered in respective sections (`TaskStatus`, `Message`, `Artifact`) - `timestamp` was not added to `Message`: [source](https://a2a-protocol.org/latest/specification/#414-message) - there is no "stricter typing" for `metadata` - "retained" should not be in the changelog - `createdAt` was not added to `Artifact`: [source](https://a2a-protocol.org/latest/specification/#417-artifact) - `signatures` field was there in 0.3: [source](https://a2a-protocol.org/v0.3.0/specification/#55-agentcard-object-structure) Re #1436. Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com> Co-authored-by: Darrel <darrmi@microsoft.com>

darrelmiller added 2 commits January 30, 2026 10:10

feat(docs): Add comprehensive overview for A2A Protocol v1.0 release

3558330

fix(docs): Update breaking changes and specifications in what's new f…

d42bffa

…or A2A Protocol v1.0

darrelmiller requested a review from a team as a code owner January 30, 2026 15:40

gemini-code-assist bot reviewed Jan 30, 2026

View reviewed changes

docs/whats-new-v1.md Outdated Show resolved Hide resolved

docs/whats-new-v1.md Outdated Show resolved Hide resolved

docs/whats-new-v1.md Outdated Show resolved Hide resolved

docs/whats-new-v1.md Outdated Show resolved Hide resolved

holtskinner changed the title ~~What changed from v0.3.0 to v1.0~~ docs(spec): What changed from v0.3.0 to v1.0 Jan 30, 2026

darrelmiller and others added 2 commits January 30, 2026 11:11

feat(docs): Enhance 'What's New' documentation with multi-tenancy sup…

7f5eef2

…port and OAuth 2.0 updates

Merge branch 'main' into whats-new-v1

884f8a1

muscariello self-requested a review January 30, 2026 16:14

muscariello approved these changes Jan 30, 2026

View reviewed changes

darrelmiller added 2 commits January 30, 2026 11:15

fix(docs): Update wording for clarity in 'What's New' documentation

8c6455c

fix: Add keystores and RFCs to spelling allow list (case-sensitive so…

96bd3f0

…rted)

darrelmiller force-pushed the whats-new-v1 branch from a4ca8cd to 96bd3f0 Compare January 30, 2026 16:23

holtskinner reviewed Jan 30, 2026

View reviewed changes

darrelmiller and others added 4 commits January 30, 2026 13:33

Fixed gemini review comments

e89b10a

Update docs/whats-new-v1.md

7f0fd96

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>

Update docs/whats-new-v1.md

959dc08

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Apply suggestions from code review

640b240

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>

darrelmiller added the no-issue label Jan 30, 2026

Removed time esitmates from migration strategy

fc607e2

gemini-code-assist bot reviewed Feb 2, 2026

View reviewed changes

docs/whats-new-v1.md Outdated Show resolved Hide resolved

docs/whats-new-v1.md Outdated Show resolved Hide resolved

docs/whats-new-v1.md Outdated Show resolved Hide resolved

holtskinner approved these changes Feb 3, 2026

View reviewed changes

Update docs/whats-new-v1.md

0135ef4

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

amye mentioned this pull request Feb 4, 2026

RFC: Standardizing Agent Interoperability via VMP-1.0 (BotNode.io) #1450

Closed

holtskinner and others added 4 commits February 5, 2026 10:39

Update docs/whats-new-v1.md

d4760a0

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

Merge branch 'main' into whats-new-v1

47afae1

Update docs/whats-new-v1.md

dc44798

Merge branch 'main' into whats-new-v1

ff48209

darrelmiller merged commit ed97dea into main Feb 5, 2026
13 checks passed

darrelmiller deleted the whats-new-v1 branch February 5, 2026 17:23

ishymko mentioned this pull request Feb 9, 2026

docs(spec): Fix whats-new-v1.md #1460

Merged

Conversation

darrelmiller commented Jan 30, 2026

Uh oh!

gemini-code-assist bot commented Jan 30, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

muscariello left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

darrelmiller commented Jan 30, 2026

Uh oh!

holtskinner commented Feb 2, 2026

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants