fix(spec): make `history_length` optional by yarolegovich · Pull Request #1071 · a2aproject/A2A

yarolegovich · 2025-09-15T18:31:28Z

Description

Both fields are optional in types.ts and jsonrpc schema.
For both cases it might be useful to differentiate 0 and unset. For example:

A client calls GetTask and doesn't want History to be fetched / included in the response.
A client calls SendMessage and doesn't want history to be persisted at all.

The change is backward-compatible and makes it possible for a2a servers to provide consistent behavior regardless of the selected transport.

Fixes #1072

gemini-code-assist

Summary of Changes

Hello @yarolegovich, 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 enhances the flexibility of history management within the a2a system by making the history_length field optional in key gRPC message definitions: SendMessageConfiguration and GetTaskRequest. This update allows clients to precisely control whether history is fetched or persisted, differentiating between a zero value and an unset state. The change ensures consistency across various communication transports, including gRPC and JSON-RPC, and is fully backward-compatible.

Highlights

gRPC Field Optionality: The history_length field in both SendMessageConfiguration and GetTaskRequest gRPC messages has been updated from a required int32 to an optional int32. This allows for explicit differentiation between a zero value (e.g., unlimited history) and an unset value (e.g., no history desired).
Consistency Across Transports: This change aligns the gRPC specification with existing types.ts and JSON-RPC schemas, where history_length is already optional. This ensures a2a servers can provide consistent behavior regarding history handling, regardless of the communication transport used.
Backward Compatibility: The modification is backward-compatible, meaning existing clients will continue to function without issues, while new clients can leverage the enhanced control offered by the optional field.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 makes the history_length field optional in SendMessageConfiguration and GetTaskRequest to align with the JSON-RPC specification and provide more flexibility. The change is logical and well-justified. My review includes suggestions to improve the comments for these fields to clearly document the behavior when the field is unset, which is important for API consumers.

specification/grpc/a2a.proto

ToddSegal · 2025-11-10T21:41:55Z

cleanup for 1.0 needs this.

recommend we vote

/vote

git-vote · 2025-11-10T21:41:58Z

Vote created

@ToddSegal has called for a vote on fix(grpc): make history_length optional (#1071).

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 7days. 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 · 2025-11-11T21:54:21Z

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	2025-11-10 21:42:05.0 +00:00:00
darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00
@lerhaupt	Pending
@geneknit	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2025-11-12T21:54:31Z

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	2025-11-10 21:42:05.0 +00:00:00
darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00
@lerhaupt	Pending
@geneknit	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

# Description The specification states that a history length of 0 should return unlimited results (see [code](https://github.com/a2aproject/A2A/blob/202aa069e66f701bacf2156d42d8916fc96a5188/specification/grpc/a2a.proto#L128-L130)). However, this was recently changed to return 0 results. This fix restores the correct behavior. Please note that there is an outstanding proposal to change this behavior. See a2aproject/A2A#1071 for more details. Prerequisites: - [x] Follow the [`CONTRIBUTING` Guide](https://github.com/a2aproject/a2a-python/blob/main/CONTRIBUTING.md). - [x] Make your Pull Request title in the <https://www.conventionalcommits.org/> specification. - Important Prefixes for [release-please](https://github.com/googleapis/release-please): - `fix:` which represents bug fixes, and correlates to a [SemVer](https://semver.org/) patch. - `feat:` represents a new feature, and correlates to a SemVer minor. - `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking change (indicated by the `!`) and will result in a SemVer major. - [x] Ensure the tests and linter pass (Run `bash scripts/format.sh` from the repository root to format) - [x] Appropriate docs were updated (if necessary) Fixes #<issue_number_goes_here> 🦕

git-vote · 2025-11-13T22:24:22Z

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	2025-11-10 21:42:05.0 +00:00:00
darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00
@lerhaupt	Pending
@geneknit	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2025-11-14T22:40:46Z

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	2025-11-10 21:42:05.0 +00:00:00
darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00
@lerhaupt	Pending
@geneknit	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2025-11-15T22:54:22Z

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	2025-11-10 21:42:05.0 +00:00:00
darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00
@lerhaupt	Pending
@geneknit	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2025-11-16T23:10:46Z

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	2025-11-10 21:42:05.0 +00:00:00
darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00
@lerhaupt	Pending
@geneknit	Pending
@hughesthe1st	Pending
@000-000-000-000-000	Pending
@SivaNSAP	Pending

git-vote · 2025-11-17T21:42:04Z

Vote closed

The vote did not pass.

37.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
3	0	0	5

Binding votes (3)

User	Vote	Timestamp
@ToddSegal	In favor	2025-11-10 21:42:05.0 +00:00:00
@darrelmiller	In favor	2025-11-10 22:13:44.0 +00:00:00
@muscariello	In favor	2025-11-10 23:01:30.0 +00:00:00

git-vote · 2025-11-18T17:04:34Z

Vote created

@amye has called for a vote on fix(grpc): make history_length optional (#1071).

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 7days. 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 · 2025-11-19T17:10:47Z

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
000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@lerhaupt	Pending
@ToddSegal	Pending
@SivaNSAP	Pending

git-vote · 2025-11-20T17:24:23Z

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
000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@lerhaupt	Pending
@ToddSegal	Pending
@SivaNSAP	Pending

holtskinner · 2025-11-21T16:25:59Z

@yarolegovich Be sure to rebase to main after the recent refactoring

git-vote · 2025-11-21T17:40:47Z

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
000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
@muscariello	Pending
@darrelmiller	Pending
@lerhaupt	Pending
@ToddSegal	Pending
@SivaNSAP	Pending

amye · 2025-11-21T17:51:02Z

Ping for this particular comment: #1071 (comment)

@muscariello
@darrelmiller
@lerhaupt
@ToddSegal
@SivaNSAP

git-vote · 2025-11-22T17:54:24Z

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
000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
muscariello	In favor	2025-11-21 19:46:54.0 +00:00:00
@darrelmiller	Pending
@lerhaupt	Pending
@ToddSegal	Pending
@SivaNSAP	Pending

git-vote · 2025-11-23T18:10:47Z

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
000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
muscariello	In favor	2025-11-21 19:46:54.0 +00:00:00
@darrelmiller	Pending
@lerhaupt	Pending
@ToddSegal	Pending
@SivaNSAP	Pending

git-vote · 2025-11-24T18:24:24Z

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
000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
muscariello	In favor	2025-11-21 19:46:54.0 +00:00:00
@darrelmiller	Pending
@lerhaupt	Pending
@ToddSegal	Pending
@SivaNSAP	Pending

amye · 2025-11-24T18:39:25Z

Round 2,
Ping for this particular comment: #1071 (comment)

@muscariello
@darrelmiller
@lerhaupt
@ToddSegal
@SivaNSAP

git-vote · 2025-11-25T12:25:19Z

Vote closed

The vote passed! 🎉

87.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
7	0	0	1

Binding votes (7)

User	Vote	Timestamp
@000-000-000-000-000	In favor	2025-11-18 17:06:02.0 +00:00:00
@SivaNSAP	In favor	2025-11-25 6:12:49.0 +00:00:00
@ToddSegal	In favor	2025-11-24 20:13:27.0 +00:00:00
@darrelmiller	In favor	2025-11-24 19:00:25.0 +00:00:00
@geneknit	In favor	2025-11-18 17:06:51.0 +00:00:00
@hughesthe1st	In favor	2025-11-18 17:10:20.0 +00:00:00
@muscariello	In favor	2025-11-24 22:04:46.0 +00:00:00

…legovich/1071

holtskinner · 2025-12-10T16:19:00Z

@darrelmiller Can you check that this update still complies with your refactoring changes?

The actual change to the spec types (making history_length optional) is already done, now the key change is just the description for the field.

muscariello

LGTM

Tehsmash · 2026-01-21T16:28:03Z

This PR looks like its just a comment change now, @muscariello I check it against spec.md and the change is correct, I think we can merge, its passed it's vote etc.

🤖 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>

yarolegovich requested a review from a team as a code owner September 15, 2025 18:31

gemini-code-assist bot reviewed Sep 15, 2025

View reviewed changes

specification/grpc/a2a.proto Outdated Show resolved Hide resolved

specification/grpc/a2a.proto Outdated Show resolved Hide resolved

mikeas1 mentioned this pull request Sep 24, 2025

[Bug]: history length is not optional in .proto #1072

Closed

1 task

holtskinner added the TSC Review To be reviewed by the Technical Steering Committee label Sep 29, 2025

fjuma mentioned this pull request Oct 21, 2025

[fix(grpc)]: make history_length optional a2aproject/a2a-java#384

Closed

yarolegovich added 4 commits November 7, 2025 19:31

make history_length optional

6f88c5e

update and unify historyLength-related comments

c24e50e

spec fix

e3bf4ea

prettier

988f6d2

herczyn force-pushed the fix/required-history-length branch from c98d4dc to 988f6d2 Compare November 7, 2025 18:31

lkawka mentioned this pull request Nov 7, 2025

fix: return entire history when history_length=0 a2aproject/a2a-python#537

Merged

4 tasks

git-vote bot added gitvote gitvote/open labels Nov 10, 2025

darrelmiller approved these changes Nov 11, 2025

View reviewed changes

Merge branch 'main' into fix/required-history-length

f7ceca1

amye added this to TSC Review Nov 17, 2025

amye moved this to Backlog in TSC Review Nov 17, 2025

amye moved this from Backlog to In review in TSC Review Nov 17, 2025

git-vote bot removed the gitvote/open label Nov 17, 2025

git-vote bot added gitvote/open and removed gitvote/closed gitvote/failed labels Nov 18, 2025

git-vote bot added gitvote/closed gitvote/passed and removed gitvote/open labels Nov 25, 2025

amye moved this from In Voting to Done in TSC Review Nov 25, 2025

Merge branch 'main' of https://github.com/a2aproject/A2A into pr/yaro…

d1e81a9

…legovich/1071

holtskinner changed the title ~~fix(grpc): make history_length optional~~ fix(spec): make history_length optional Dec 10, 2025

Merge branch 'main' into fix/required-history-length

09addee

muscariello self-requested a review December 19, 2025 09:51

muscariello approved these changes Dec 19, 2025

View reviewed changes

Merge branch 'main' into fix/required-history-length

6c58b80

Merge branch 'main' into fix/required-history-length

d251bd9

muscariello merged commit 0572953 into a2aproject:main Jan 21, 2026
6 checks passed

a2a-bot mentioned this pull request Jan 21, 2026

chore(main): release 1.0.0 #1221

Merged

Conversation

yarolegovich commented Sep 15, 2025 • edited by holtskinner Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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!

ToddSegal commented Nov 10, 2025

Uh oh!

git-vote bot commented Nov 10, 2025

Vote created

How to vote

Uh oh!

git-vote bot commented Nov 11, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 12, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 13, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 14, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 15, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 16, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 17, 2025

Vote closed

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 18, 2025

Vote created

How to vote

Uh oh!

git-vote bot commented Nov 19, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

git-vote bot commented Nov 20, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

holtskinner commented Nov 21, 2025

Uh oh!

git-vote bot commented Nov 21, 2025

Vote status

Summary

Binding votes (3)

Uh oh!

amye commented Nov 21, 2025

yarolegovich commented Sep 15, 2025 •

edited by holtskinner

Loading