chore(spec): Update default protocol version to 0.3.0#366
Conversation
There was a problem hiding this comment.
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 specification to version 0.3.0, primarily focusing on enhancing security definitions and capabilities. Key changes include the introduction of skill-specific security requirements, support for mutual TLS authentication, and the ability to specify OAuth 2.0 metadata URLs. These updates improve the flexibility and robustness of how agents and their skills handle authentication and authorization.
Highlights
- Protocol Version Update: The A2A protocol version has been incremented from
0.2.6to0.3.0, indicating a significant update to the API specification. - Granular Skill Security: Individual
AgentSkilldefinitions can now specify their own security requirements, providing more granular control over access to specific agent capabilities. - New Security Scheme: A new
MutualTlsSecuritySchemehas been added, expanding the range of supported authentication methods to include mutual TLS. - OAuth2 Metadata Support: The
OAuth2SecuritySchemenow supports anoauth2_metadata_url, allowing for dynamic discovery of OAuth 2.0 authorization server metadata.
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 or fill out our survey to provide feedback.
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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request updates the generated Python code for protobuf messages and Pydantic types to align with a new version of the A2A specification. The changes introduce new security schemes like mTLS, add metadata URLs for OAuth2, and update the protocol version. The modifications across a2a_pb2.py, a2a_pb2.pyi, and a2a/types.py are consistent with each other and appear to be correctly generated. I have reviewed the changes and found no issues.
0a5af63 to
8e32574
Compare
Release-As: 0.3.0
Protocol Update: a2aproject/A2A@6a152a8