chore(main): release 1.0.1-alpha.2

[a2a-bot]

🤖 I have created a release beep boop

1.0.1-alpha.2 (2026-02-27)

Bug Fixes

• a2a part metadata handling (#249) (7bd24a2)

---

This PR was generated with Release Please. See documentation.

[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 automates the release of version 1.1.0-alpha for the a2a-go project. It incorporates a set of new features that enhance functionality and several bug fixes that improve stability and compliance, reflecting the latest developments in the codebase.

Highlights

• New Features Introduced: Several new features were added, including capability validation, compatibility header handling, emitting tasks as the first subscription event, improved gRPC error handling with errinfo, and tenant management in a2aclient and a2asrv.
• Critical Bug Fixes: Important bug fixes were implemented, addressing REST transport SSE keep-alives and panic handling, ensuring TCK compliance by yielding SubmittedTask as the first event, updating compatibility for older library versions, and correcting HistoryLength.
• Automated Release: This pull request represents the automated release of version 1.1.0-alpha, updating the project's version manifest and changelog.

Changelog

• .release-please-manifest.json
  • Updated the project's root version from 0.3.7 to 1.1.0-alpha.
• CHANGELOG.md
  • Added a new section for version 1.1.0-alpha, detailing new features and bug fixes.
  • Features include: capability validation, compat header handling, emitting task as first subscription event, gRPC error construction with errinfo, and tenant handling in a2aclient and a2asrv.
  • Bug fixes include: REST transport SSE keep-alives and panic handling, TCK compliance for SubmittedTask event, updating compat for old lib versions, and updating HistoryLength.

Activity

• The pull request was automatically generated by the 'Release Please' bot to create a new release.

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, generated by Release Please, prepares for the 1.1.0-alpha release. It updates the version in .release-please-manifest.json and adds the corresponding changelog entry to CHANGELOG.md. My review focuses on the formatting of the changelog, where I've identified some extra blank lines that could be removed for consistency and improved readability.

[gemini-code-assist]

The new changelog entry contains extra blank lines (e.g., at line 5 and line 14) which makes the formatting inconsistent with other entries in the file. Please remove these to improve readability.