Skip to content

fix: Add name field to FilePart protobuf message#403

Merged
holtskinner merged 1 commit intomainfrom
auto-update-a2a-types-2b7cb6f8408e6324c48fb82c71839c67a18f1fab
Aug 13, 2025
Merged

fix: Add name field to FilePart protobuf message#403
holtskinner merged 1 commit intomainfrom
auto-update-a2a-types-2b7cb6f8408e6324c48fb82c71839c67a18f1fab

Conversation

@a2a-bot
Copy link
Collaborator

@a2a-bot a2a-bot commented Aug 13, 2025

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @a2a-bot, I'm Gemini Code Assist1! 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 updates the A2A gRPC specification by incorporating a new name field into the FilePart message. This change reflects an evolution in the data structure for file-related parts within the A2A system, ensuring that generated code aligns with the latest protocol definition.

Highlights

  • New Field in FilePart Message: A new name field has been introduced to the FilePart message within the A2A gRPC specification.
  • Generated Protobuf Code Update: The generated Python protobuf file (src/a2a/grpc/a2a_pb2.py) has been updated to reflect the modified FilePart definition, including changes to its serialized descriptor.
  • Python Type Hint Synchronization: The Python type hint file (src/a2a/grpc/a2a_pb2.pyi) has been synchronized to include the new name attribute and its type in the FilePart class, ensuring type safety and clarity.
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.

Footnotes

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

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the generated Python code for the A2A gRPC service, reflecting a change in the protobuf specification. The primary modification is the addition of a name field to the FilePart message. The changes within src/a2a/grpc/a2a_pb2.py and its corresponding stub file src/a2a/grpc/a2a_pb2.pyi are consistent with this update and appear to be correctly generated. I have reviewed the code changes and found no issues.

@holtskinner holtskinner changed the title Update to specification from 2b7cb6f8408e6324c48fb82c71839c67a18f1fab fix: Add name field to FilePart protobuf message Aug 13, 2025
@holtskinner holtskinner merged commit 1dbe33d into main Aug 13, 2025
8 of 9 checks passed
@holtskinner holtskinner deleted the auto-update-a2a-types-2b7cb6f8408e6324c48fb82c71839c67a18f1fab branch August 13, 2025 15:55
holtskinner pushed a commit that referenced this pull request Aug 20, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.3.2](v0.3.1...v0.3.2)
(2025-08-20)


### Bug Fixes

* Add missing mime_type and name in proto conversion utils
([#408](#408))
([72b2ee7](72b2ee7))
* Add name field to FilePart protobuf message
([#403](#403))
([1dbe33d](1dbe33d))
* Client hangs when implementing `AgentExecutor` and `await`ing twice in
execute method
([#379](#379))
([c147a83](c147a83))
* **grpc:** Update `CreateTaskPushNotificationConfig` endpoint to
`/v1/{parent=tasks/*/pushNotificationConfigs}`
([#415](#415))
([73dddc3](73dddc3))
* make `event_consumer` tolerant to closed queues on py3.13
([#407](#407))
([a371461](a371461))
* non-blocking `send_message` server handler not invoke push
notification
([#394](#394))
([db82a65](db82a65))
* **proto:** Add `icon_url` to `a2a.proto`
([#416](#416))
([00703e3](00703e3))
* **spec:** Suggest Unique Identifier fields to be UUID
([#405](#405))
([da14cea](da14cea))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants