refactor(spec)!: Remove redundant `final` field from `TaskStatusUpdateEvent` by madankumarpichamuthu · Pull Request #1308 · a2aproject/A2A

madankumarpichamuthu · 2025-12-11T21:38:41Z

Terminal states (COMPLETED, FAILED, CANCELLED, REJECTED) already indicate task completion, making the final field redundant. This creates consistency across streaming, polling, and push notification communication patterns.

Changes:

Removed final field (field 4) from TaskStatusUpdateEvent in proto
Updated examples to remove final: true references
Clarified that streams close upon terminal states
Added migration guidance in Appendix A.2.2

Fixes #1232

Terminal states (COMPLETED, FAILED, CANCELLED, REJECTED) already indicate task completion, making the final field redundant. This creates consistency across streaming, polling, and push notification communication patterns. Changes: - Removed final field (field 4) from TaskStatusUpdateEvent in proto - Updated examples to remove final: true references - Clarified that streams close upon terminal states - Added migration guidance in Appendix A.2.2 Fixes a2aproject#1232 Author: Madan Kumar Pichamuthu

gemini-code-assist · 2025-12-11T21:39:00Z

Summary of Changes

Hello @madankumarpichamuthu, 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!

This pull request refactors the TaskStatusUpdateEvent by removing the redundant final field. This change simplifies the protocol by relying on terminal task states (COMPLETED, FAILED, CANCELLED, REJECTED) to signal completion and stream termination, ensuring consistency across various communication patterns. The update includes comprehensive documentation changes and migration guidance for affected clients and agents, addressing issue #1232.

Highlights

Removal of Redundant Field: The final boolean field has been removed from the TaskStatusUpdateEvent in the a2a.proto specification, as terminal states (COMPLETED, FAILED, CANCELLED, REJECTED) inherently indicate task completion.
Stream Termination Logic: Stream termination is now solely determined by a task reaching any terminal state, simplifying the protocol and removing the need for an explicit final flag.
Documentation and Examples Updated: All relevant documentation, including specification examples, streaming topics, and Python tutorials, have been updated to reflect this change and remove references to the final field.
Migration Guidance Provided: New documentation explicitly outlines migration steps for both agents and clients to adapt to the removal of the final field, ensuring a smooth transition.

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 effectively removes the redundant final field from TaskStatusUpdateEvent and updates the associated documentation and examples. The addition of a migration guide is particularly helpful for a breaking change like this. I have a few suggestions to enhance the changes. Firstly, in the protobuf definition, it's a good practice to reserve the field number of the removed field to prevent future compatibility issues. Secondly, I noticed an inconsistency in the documentation regarding when a stream closes. Some sections mention only terminal states, while others correctly include interrupted states like INPUT_REQUIRED. I've left comments to help align the documentation for consistency.

docs/specification.md

docs/topics/streaming-and-async.md

specification/grpc/a2a.proto

Fix MD032 markdown linting errors - lists must be surrounded by blank lines.

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

Prevent future reuse of field number 4 to maintain wire compatibility. Author: Madan Kumar Pichamuthu

docs/specification.md

@Tehsmash

Addresses review feedback from @Tehsmash and @darrelmiller to remove the breaking change note from the specification document. Breaking changes should be tracked in issues, git history, and release notes rather than in the spec itself. Changes: - Removed "Behavior Change" section from docs/specification.md (lines 3491-3493) - Maintains all other changes from PR a2aproject#1308 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>

@Tehsmash

Addresses review feedback from @Tehsmash and @darrelmiller to remove the breaking change note from the specification document. Breaking changes should be tracked in issues, git history, and release notes rather than in the spec itself. Changes: - Removed "Behavior Change" section from docs/specification.md (lines 3491-3493) - Maintains all other changes from PR a2aproject#1308

darrelmiller · 2026-01-14T13:19:31Z

/vote

git-vote · 2026-01-14T13:19:34Z

Vote created

@darrelmiller has called for a vote on fix(spec): refactor: Remove redundant final field from TaskStatusUpdateEvent (#1308).

The members of the following teams have binding votes:

Team
@a2aproject/a2a-tsc

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor	Against	Abstain
👍	👎	👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 11months 29days 3h 50m 24s. It will pass if at least 51% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.

git-vote · 2026-01-15T13:19:55Z

Vote status

So far 0.00% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
0	0	0	8

Binding votes (0)

User	Vote	Timestamp
@muscariello	Pending
@darrelmiller	Pending
@geneknit	Pending
@hughesthe1st	Pending
@ToddSegal	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending
@spetschulatSFDC	Pending

git-vote · 2026-01-16T13:40:38Z

Vote status

So far 12.50% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
1	0	0	7

Binding votes (1)

User	Vote	Timestamp
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@geneknit	Pending
@hughesthe1st	Pending
@ToddSegal	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2026-01-17T13:49:55Z

Vote status

So far 12.50% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
1	0	0	7

Binding votes (1)

User	Vote	Timestamp
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@geneknit	Pending
@hughesthe1st	Pending
@ToddSegal	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2026-01-18T14:10:38Z

Vote status

So far 12.50% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
1	0	0	7

Binding votes (1)

User	Vote	Timestamp
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@geneknit	Pending
@hughesthe1st	Pending
@ToddSegal	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2026-01-19T14:19:56Z

Vote status

So far 12.50% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
1	0	0	7

Binding votes (1)

User	Vote	Timestamp
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@geneknit	Pending
@hughesthe1st	Pending
@ToddSegal	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

As requested by maintainers, breaking changes should be documented in issues, git history, and release notes rather than in the specification itself. This removes the A.2.2 section about the final field removal.

git-vote · 2026-01-20T14:40:38Z

Vote status

So far 12.50% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
1	0	0	7

Binding votes (1)

User	Vote	Timestamp
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@geneknit	Pending
@hughesthe1st	Pending
@ToddSegal	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

Non-binding votes (1)

User	Vote	Timestamp
Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

docs/topics/streaming-and-async.md

git-vote · 2026-01-21T14:49:56Z

Vote status

So far 37.50% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
3	0	0	5

Binding votes (3)

User	Vote	Timestamp
ToddSegal	In favor	2026-01-20 17:12:22.0 +00:00:00
geneknit	In favor	2026-01-20 19:55:38.0 +00:00:00
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

Non-binding votes (1)

User	Vote	Timestamp
Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

git-vote · 2026-01-22T15:10:39Z

Vote status

So far 50.00% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
4	0	0	4

Binding votes (4)

User	Vote	Timestamp
ToddSegal	In favor	2026-01-20 17:12:22.0 +00:00:00
geneknit	In favor	2026-01-20 19:55:38.0 +00:00:00
muscariello	In favor	2026-01-22 10:45:47.0 +00:00:00
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@darrelmiller	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

Non-binding votes (1)

User	Vote	Timestamp
Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

git-vote · 2026-01-23T15:19:57Z

Vote status

So far 50.00% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
4	0	0	4

Binding votes (4)

User	Vote	Timestamp
ToddSegal	In favor	2026-01-20 17:12:22.0 +00:00:00
geneknit	In favor	2026-01-20 19:55:38.0 +00:00:00
muscariello	In favor	2026-01-22 10:45:47.0 +00:00:00
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@darrelmiller	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

Non-binding votes (1)

User	Vote	Timestamp
Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

git-vote · 2026-01-24T15:40:39Z

Vote status

So far 50.00% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
4	0	0	4

Binding votes (4)

User	Vote	Timestamp
ToddSegal	In favor	2026-01-20 17:12:22.0 +00:00:00
geneknit	In favor	2026-01-20 19:55:38.0 +00:00:00
muscariello	In favor	2026-01-22 10:45:47.0 +00:00:00
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@darrelmiller	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

Non-binding votes (1)

User	Vote	Timestamp
Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

git-vote · 2026-01-25T15:55:40Z

Vote status

So far 50.00% of the users with binding vote are in favor and 0.00% are against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
4	0	0	4

Binding votes (4)

User	Vote	Timestamp
ToddSegal	In favor	2026-01-20 17:12:22.0 +00:00:00
geneknit	In favor	2026-01-20 19:55:38.0 +00:00:00
muscariello	In favor	2026-01-22 10:45:47.0 +00:00:00
spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00
@darrelmiller	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

Non-binding votes (1)

User	Vote	Timestamp
Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

muscariello

LGTM

git-vote · 2026-01-26T09:25:53Z

Vote closed

The vote passed! 🎉

62.50% of the users with binding vote were in favor and 0.00% were against (passing threshold: 51%).

Summary

In favor	Against	Abstain	Not voted
5	0	0	3

Binding votes (5)

User	Vote	Timestamp
@ToddSegal	In favor	2026-01-20 17:12:22.0 +00:00:00
@darrelmiller	In favor	2026-01-26 3:20:43.0 +00:00:00
@geneknit	In favor	2026-01-20 19:55:38.0 +00:00:00
@muscariello	In favor	2026-01-22 10:45:47.0 +00:00:00
@spetschulatSFDC	In favor	2026-01-15 23:55:38.0 +00:00:00

Non-binding votes (1)

User	Vote	Timestamp
@Tehsmash	In favor	2026-01-20 9:37:52.0 +00:00:00

🤖 I have created a release *beep* *boop* --- ## [1.0.0](v0.3.0...v1.0.0) (2026-03-12) ### ⚠ BREAKING CHANGES * **spec:** Combine `TaskPushNotificationConfig` and `PushNotificationConfig` ([#1500](#1500)) * **spec:** remove duplicated ID from the create task push config request ([#1487](#1487)) * **spec:** pluralize configs in `ListTaskPushNotificationConfigs` ([#1486](#1486)) * **spec:** Add LF prefix to the package. ([#1474](#1474)) * **spec:** Switch to non-complex IDs in requests ([#1389](#1389)) * **spec:** Standardize spelling of "canceled" to use American Spelling throughout ([#1283](#1283)) * **spec:** Align enum format with ADR-001 ProtoJSON specification ([#1384](#1384)) * **spec:** Remove redundant `final` field from `TaskStatusUpdateEvent` ([#1308](#1308)) * **spec:** Move `extendedAgentCard` field to `AgentCapabilities` ([#1307](#1307)) * **spec:** Fixes for the last_updated_after field ([#1358](#1358)) * **spec:** modernize oauth 2.0 flows - remove implicit/password, add device code / pkce ([#1303](#1303)) * **spec:** Make "message" field name consistent between protocol bindings ([#1302](#1302)) * **spec:** Remove deprecated fields from a2a.proto for v1.0 release ([#1301](#1301)) * **spec:** Rename `supportsAuthenticatedExtendedCard` to `supportsExtendedAgentCard` ([#1222](#1222)) * **spec:** Remove v1s from a2a url http bindings * **spec:** Large refactor of specification to separate application protocol definition from mapping to transports ### Features * **spec:** Add `tasks/list` method with filtering and pagination to the specification ([0a9f629](0a9f629)) * **spec:** modernize oauth 2.0 flows - remove implicit/password, add device code / pkce ([#1303](#1303)) ([525ff38](525ff38)) * **spec:** Natively Support Multi-tenancy on gRPC through an additional scope field on the request. ([#1195](#1195)) ([cfbce32](cfbce32)), closes [#1148](#1148) * **spec:** Provide ability for SDKs to be backwards compatible. ([#1401](#1401)) ([227e249](227e249)) * **spec:** Remove v1s from a2a url http bindings ([1bd263f](1bd263f)) ### Bug Fixes * Add missing metadata field to Part message in gRPC specification ([#1019](#1019)) ([b3b266d](b3b266d)), closes [#1005](#1005) * Add name field to FilePart protobuf message ([#983](#983)) ([2b7cb6f](2b7cb6f)), closes [#984](#984) * Clarify blocking calls return on interrupted states ([#1403](#1403)) ([0655ff3](0655ff3)) * **doc:** Makes JSON-RPC SendMessage response clearer ([#1241](#1241)) ([5792804](5792804)) * **docs:** Clearer wording around context id. ([#1588](#1588)) ([dec790a](dec790a)) * **grpc:** Fix inconsistent property name between gRPC and JSON-RPC in Message object ([#1100](#1100)) ([2a1f819](2a1f819)) * **grpc:** missing field in gRPC spec - state_transition_history ([#1138](#1138)) ([a2de798](a2de798)), closes [#1139](#1139) * **grpc:** Update `CreateTaskPushNotificationConfig` endpoint to `/v1/{parent=tasks/*/pushNotificationConfigs}` ([#979](#979)) ([911f9b0](911f9b0)) * **proto:** Add icon_url to a2a.proto ([#986](#986)) ([17e7f62](17e7f62)) * **proto:** Adds metadata field to A2A DataPart proto ([#1004](#1004)) ([a8b45dc](a8b45dc)) * Remove unimplemented state_transition_history capability field ([#1396](#1396)) ([c768a44](c768a44)), closes [#1228](#1228) * Restore CreateTaskPushNotificationConfig method naming ([#1402](#1402)) ([d14f410](d14f410)) * Revert "chore(gRPC): Update a2a.proto to include metadata on GetTaskRequest" ([#1000](#1000)) ([e6b8c65](e6b8c65)) * Simplify Part message structure by flattening FilePart and DataPart ([#1411](#1411)) ([bfae8f7](bfae8f7)) * **spec:** Add LF prefix to the package. ([#1474](#1474)) ([a54e809](a54e809)) * **spec:** add metadata to `CancelTaskRequest` ([#1485](#1485)) ([c441b91](c441b91)), closes [#1484](#1484) * **spec:** Added clarification on timestamps in HTTP query params ([#1425](#1425)) ([6292104](6292104)) * **spec:** Added clarifying text around messages and artifacts ([#1424](#1424)) ([b03d141](b03d141)) * **spec:** Adjust field number for `ListTasksRequest.tenant` to prevent missing number ([#1470](#1470)) ([cd16c52](cd16c52)) * **spec:** Clarify contextId behavior when message is sent with taskId but without contextId ([#1309](#1309)) ([a336a5a](a336a5a)) * **spec:** Clarify versioning strategy and client responsibilities in protocol specification ([#1259](#1259)) ([a4afeea](a4afeea)) * **spec:** Fix/1251 clarify authentication scheme ([#1256](#1256)) ([3e6c7db](3e6c7db)) * **spec:** Fixes for the last_updated_after field ([#1358](#1358)) ([0e204bf](0e204bf)) * **spec:** Make "message" field name consistent between protocol bindings ([#1302](#1302)) ([1e5f462](1e5f462)), closes [#1230](#1230) * **spec:** make `history_length` optional ([#1071](#1071)) ([0572953](0572953)) * **spec:** pluralize configs in `ListTaskPushNotificationConfigs` ([#1486](#1486)) ([cf735cb](cf735cb)) * **spec:** Remove config from binding. ([#1587](#1587)) ([010b9cc](010b9cc)) * **spec:** Remove deprecated fields from a2a.proto for v1.0 release ([#1301](#1301)) ([60f83c3](60f83c3)), closes [#1227](#1227) * **spec:** remove duplicated ID from the create task push config request ([#1487](#1487)) ([393898d](393898d)) * **spec:** Remove metadata field from ListTasksRequest ([#1235](#1235)) ([b6ef9ee](b6ef9ee)) * **spec:** Remove reserved and fix tags ordering ([#1494](#1494)) ([1997c9d](1997c9d)) * **spec:** Rename `supportsAuthenticatedExtendedCard` to `supportsExtendedAgentCard` ([#1222](#1222)) ([c196824](c196824)), closes [#1215](#1215) * **spec:** Standardize spelling of "canceled" to use American Spelling throughout ([#1283](#1283)) ([4dd980f](4dd980f)) * **spec:** Suggest Unique Identifier fields to be UUID ([#966](#966)) ([00cf76e](00cf76e)) * **spec:** Switch to non-complex IDs in requests ([#1389](#1389)) ([2596c1c](2596c1c)), closes [#1390](#1390) * **spec:** Update security schemes example ([#1364](#1364)) ([f9a8f5b](f9a8f5b)) * Update the Java tutorials and descriptions ([#1181](#1181)) ([202aa06](202aa06)) ### Documentation * **spec:** Align enum format with ADR-001 ProtoJSON specification ([#1384](#1384)) ([810eaa1](810eaa1)), closes [#1344](#1344) ### Code Refactoring * **spec:** Combine `TaskPushNotificationConfig` and `PushNotificationConfig` ([#1500](#1500)) ([d1ed0da](d1ed0da)) * **spec:** Large refactor of specification to separate application protocol definition from mapping to transports ([b078419](b078419)) * **spec:** Move `extendedAgentCard` field to `AgentCapabilities` ([#1307](#1307)) ([40d6286](40d6286)) * **spec:** Remove redundant `final` field from `TaskStatusUpdateEvent` ([#1308](#1308)) ([5b101cc](5b101cc)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: Amye Scavarda Perrin <amye@amye.org> Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>

madankumarpichamuthu requested review from a team as code owners December 11, 2025 21:38

gemini-code-assist bot reviewed Dec 11, 2025

View reviewed changes

docs/specification.md Outdated Show resolved Hide resolved

docs/topics/streaming-and-async.md Outdated Show resolved Hide resolved

specification/grpc/a2a.proto Show resolved Hide resolved

madankumarpichamuthu and others added 4 commits December 11, 2025 13:42

docs: Add blank lines before lists in migration guide

3f3dc67

Fix MD032 markdown linting errors - lists must be surrounded by blank lines.

Update docs/specification.md

32e6716

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

Update docs/topics/streaming-and-async.md

09aa3fd

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

fix: Reserve field number 4 in TaskStatusUpdateEvent

2a56632

Prevent future reuse of field number 4 to maintain wire compatibility. Author: Madan Kumar Pichamuthu

madankumarpichamuthu mentioned this pull request Dec 12, 2025

[Question] Is 'final' property necessary given terminal states? Can TaskArtifactUpdateEvent come after terminal state? #1232

Closed

Tehsmash reviewed Dec 15, 2025

View reviewed changes

docs/specification.md Show resolved Hide resolved

madankumarpichamuthu and others added 2 commits January 6, 2026 21:56

Merge branch 'main' into fix/1232-remove-final-field

3507a63

Merge branch 'main' into fix/1232-remove-final-field

a824f0b

madankumarpichamuthu force-pushed the fix/1232-remove-final-field branch from e593650 to 08cad2f Compare January 13, 2026 17:08

Merge branch 'main' into fix/1232-remove-final-field

74225e6

git-vote bot added gitvote gitvote/open labels Jan 14, 2026

docs: Remove breaking change section from specification

4fc8206

As requested by maintainers, breaking changes should be documented in issues, git history, and release notes rather than in the specification itself. This removes the A.2.2 section about the final field removal.

Tehsmash approved these changes Jan 20, 2026

View reviewed changes

holtskinner changed the title ~~fix(spec): refactor: Remove redundant final field from TaskStatusUpdateEvent~~ fix(spec)!: refactor: Remove redundant final field from TaskStatusUpdateEvent Jan 20, 2026

holtskinner changed the title ~~fix(spec)!: refactor: Remove redundant final field from TaskStatusUpdateEvent~~ refactor(spec)!: Remove redundant final field from TaskStatusUpdateEvent Jan 20, 2026

holtskinner reviewed Jan 20, 2026

View reviewed changes

docs/topics/streaming-and-async.md Outdated Show resolved Hide resolved

Update docs/topics/streaming-and-async.md

3ef73f3

Tehsmash mentioned this pull request Jan 21, 2026

[Bug]: Handle blocking SendMessage calls needing user interactions #1264

Closed

1 task

muscariello added this to the 1.0 milestone Jan 22, 2026

muscariello added this to TSC Review Jan 22, 2026

github-project-automation bot moved this to Backlog in TSC Review Jan 22, 2026

muscariello moved this from Backlog to In progress in TSC Review Jan 22, 2026

Merge branch 'main' into fix/1232-remove-final-field

58fd4dd

muscariello removed this from the 1.0 milestone Jan 22, 2026

Merge branch 'main' into fix/1232-remove-final-field

72a66ca

Merge branch 'main' into fix/1232-remove-final-field

867fed4

darrelmiller approved these changes Jan 26, 2026

View reviewed changes

muscariello approved these changes Jan 26, 2026

View reviewed changes

muscariello linked an issue Jan 26, 2026 that may be closed by this pull request

[Bug]: Handle blocking SendMessage calls needing user interactions #1264

Closed

1 task

git-vote bot added gitvote/closed gitvote/passed and removed gitvote/open labels Jan 26, 2026

Merge branch 'main' into fix/1232-remove-final-field

a368352

amye merged commit 5b101cc into a2aproject:main Jan 27, 2026
7 checks passed

github-project-automation bot moved this from In progress to Done in TSC Review Jan 27, 2026

a2a-bot mentioned this pull request Jan 27, 2026

chore(main): release 1.0.0 #1221

Merged

ishymko mentioned this pull request Feb 9, 2026

refactor!: Update to Protocol v1.0.0-rc and fix all tests a2aproject/a2a-python#665

Merged

Conversation

madankumarpichamuthu commented Dec 11, 2025

Uh oh!

gemini-code-assist bot commented Dec 11, 2025

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!

darrelmiller commented Jan 14, 2026

Uh oh!

git-vote bot commented Jan 14, 2026

Vote created

How to vote

Uh oh!

git-vote bot commented Jan 15, 2026

Vote status

Summary

Binding votes (0)

Uh oh!

git-vote bot commented Jan 16, 2026

Vote status

Summary

Binding votes (1)

Uh oh!

git-vote bot commented Jan 17, 2026

Vote status

Summary

Binding votes (1)

Uh oh!

git-vote bot commented Jan 18, 2026

Vote status

Summary

Binding votes (1)

Uh oh!

git-vote bot commented Jan 19, 2026

Vote status

Summary

Binding votes (1)

Uh oh!

git-vote bot commented Jan 20, 2026

Vote status

Summary

Binding votes (1)

Non-binding votes (1)

Uh oh!

Uh oh!

git-vote bot commented Jan 21, 2026

Vote status

Summary

Binding votes (3)

Non-binding votes (1)

Uh oh!

git-vote bot commented Jan 22, 2026

Vote status

Summary

Binding votes (4)

Non-binding votes (1)

Uh oh!

git-vote bot commented Jan 23, 2026

Vote status

Summary

Binding votes (4)

Non-binding votes (1)

Uh oh!

git-vote bot commented Jan 24, 2026

Vote status

Summary

Binding votes (4)

Non-binding votes (1)

Uh oh!

git-vote bot commented Jan 25, 2026

Vote status