Skip to content

docs: Blog post announcing V1.0#1621

Merged
spetschulatSFDC merged 6 commits intomainfrom
announcing-v1
Mar 12, 2026
Merged

docs: Blog post announcing V1.0#1621
spetschulatSFDC merged 6 commits intomainfrom
announcing-v1

Conversation

@darrelmiller
Copy link
Contributor

No description provided.

@darrelmiller darrelmiller requested a review from a team as a code owner March 12, 2026 16:50
@darrelmiller darrelmiller changed the title Blog post announcing V1.0 docs: Blog post announcing V1.0 Mar 12, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 adds a blog post announcing the release of A2A Protocol v1.0. The post highlights the key features and improvements in this release, emphasizing its production-readiness, enterprise support, and alignment with web architecture principles. It also clarifies the relationship between A2A and MCP and outlines the migration path for existing users.

Highlights

  • A2A Protocol v1.0 Release: The A2A Protocol community is announcing the release of v1.0, which is the first stable, production-ready version of the open standard for communication between AI agents.
  • Enterprise Requirements: The v1.0 release introduces capabilities aimed at production environments, including heterogeneous environment support, multi-tenancy support, signed Agent Cards, and improved security posture.
  • Web-Aligned Architecture: A2A v1.0 aligns with core architectural principles of the web, such as statelessness and standard protocol bindings, for better scalability.
  • Relationship with MCP: The release clarifies that A2A is complementary to the Model Context Protocol (MCP), not a replacement, with MCP focusing on tool and context integration at the agent level and A2A focusing on inter-agent communication.
  • Migration: AgentCard has evolved in a backward-compatible way and now allows agents to advertise support for both existing 0.3 protocol behavior and v1.0 simultaneously, enabling progressive migration.
Changelog
  • docs/announcing-1.0.md
    • Added a blog post announcing the release of A2A Protocol v1.0.
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
Copy link
Contributor

Warning

Gemini encountered an error creating the review. You can try again by commenting /gemini review.

Copy link
Member

@muscariello muscariello left a comment

Choose a reason for hiding this comment

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

LGTM

@spetschulatSFDC spetschulatSFDC enabled auto-merge (squash) March 12, 2026 17:01
@spetschulatSFDC spetschulatSFDC merged commit 4f77f1b into main Mar 12, 2026
12 of 13 checks passed
@spetschulatSFDC spetschulatSFDC deleted the announcing-v1 branch March 12, 2026 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants