Skip to content

chore(spec): Update default protocol version to 0.3.0#366

Merged
holtskinner merged 1 commit intomainfrom
auto-update-a2a-types-6a152a83ada222c0ca88e38ca95fc0c2b746c802
Jul 30, 2025
Merged

chore(spec): Update default protocol version to 0.3.0#366
holtskinner merged 1 commit intomainfrom
auto-update-a2a-types-6a152a83ada222c0ca88e38ca95fc0c2b746c802

Conversation

@a2a-bot
Copy link
Copy Markdown
Collaborator

@a2a-bot a2a-bot commented Jul 30, 2025

Release-As: 0.3.0

Protocol Update: a2aproject/A2A@6a152a8

@a2a-bot a2a-bot requested a review from a team as a code owner July 30, 2025 14:58
Copy link
Copy Markdown
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 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.6 to 0.3.0, indicating a significant update to the API specification.
  • Granular Skill Security: Individual AgentSkill definitions can now specify their own security requirements, providing more granular control over access to specific agent capabilities.
  • New Security Scheme: A new MutualTlsSecurityScheme has been added, expanding the range of supported authentication methods to include mutual TLS.
  • OAuth2 Metadata Support: The OAuth2SecurityScheme now supports an oauth2_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

  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
Copy Markdown
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 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.

@holtskinner holtskinner changed the title Update to specification from 6a152a83ada222c0ca88e38ca95fc0c2b746c802 chore: Update default protocol version to 0.3.0 Jul 30, 2025
@holtskinner holtskinner changed the title chore: Update default protocol version to 0.3.0 chore(spec): Update default protocol version to 0.3.0 Jul 30, 2025
@holtskinner holtskinner force-pushed the auto-update-a2a-types-6a152a83ada222c0ca88e38ca95fc0c2b746c802 branch from 0a5af63 to 8e32574 Compare July 30, 2025 15:07
@holtskinner holtskinner enabled auto-merge (squash) July 30, 2025 15:08
@holtskinner holtskinner merged commit 49e686b into main Jul 30, 2025
8 checks passed
@holtskinner holtskinner deleted the auto-update-a2a-types-6a152a83ada222c0ca88e38ca95fc0c2b746c802 branch July 30, 2025 15:08
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