chore: update a2a.proto to v1.0.0 tag

[jmesnil]

The proto definitions did not change betwee the previous commit (601c408) and the v1.0.0 tag.

Update the tracking comment to reference the
official release tag.

[gemini-code-assist]

Summary of Changes

Hello, 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 updates a single comment within the a2a.proto file. The change ensures that the proto definitions are correctly attributed to the v1.0.0 release tag, providing better clarity and consistency for the source of these definitions.

Highlights

• Proto Definition Tracking: The tracking comment in a2a.proto was updated to reference the official v1.0.0 release tag instead of an older commit hash (601c408).

Changelog

• spec-grpc/src/main/proto/a2a.proto
  • Updated the tracking comment to reference the v1.0.0 tag.

Activity

• No specific activity (comments, reviews, or progress updates) has been recorded for this pull request yet.

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.

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

[gemini-code-assist]

Code Review

This pull request updates a comment in a2a.proto to reference the v1.0.0 tag instead of a commit hash. This is a good change for traceability. I have added one suggestion to further improve the comment by including the source repository, which will make it easier for future developers to find the origin of the file.