Skip to content

Conversation

a2a-bot
Copy link
Collaborator

@a2a-bot a2a-bot commented Aug 12, 2025

🤖 I have created a release beep boop

0.3.1 (2025-09-02)

Bug Fixes

  • Add missing metadata field to Part message in gRPC specification (#1019) (b3b266d), closes #1005
  • Add name field to FilePart protobuf message (#983) (2b7cb6f), closes #984
  • grpc: Update CreateTaskPushNotificationConfig endpoint to /v1/{parent=tasks/*/pushNotificationConfigs} (#979) (911f9b0)
  • proto: Add icon_url to a2a.proto (#986) (17e7f62)
  • proto: Adds metadata field to A2A DataPart proto (#1004) (a8b45dc)
  • Revert "chore(gRPC): Update a2a.proto to include metadata on GetTaskRequest" (#1000) (e6b8c65)
  • spec: Suggest Unique Identifier fields to be UUID (#966) (00cf76e)

This PR was generated with Release Please. See documentation.

@a2a-bot a2a-bot requested a review from a team as a code owner August 12, 2025 13:15
Copy link
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 represents an automated release for version 0.3.1, primarily focused on incorporating a minor bug fix. The changes include updating the changelog to document the new version and the specific typo correction.

Highlights

  • Release Automation: This PR is an automated release generated by Release Please for version 0.3.1.
  • Bug Fix: It includes a fix for a typo, changing "forseeable" to "foreseeable", as documented in issue #971.
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. 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.

Copy link
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 is an automated release pull request for version 0.3.1. The changes update the CHANGELOG.md to reflect the new release, including a bug fix. The formatting of the new entry is consistent with the rest of the file. The changes look correct.

@a2a-bot a2a-bot force-pushed the release-please--branches--main branch 2 times, most recently from 5086a4a to 4085019 Compare August 13, 2025 19:56
@a2a-bot a2a-bot force-pushed the release-please--branches--main branch 4 times, most recently from a790d51 to 0dbf75f Compare August 27, 2025 16:29
@a2a-bot a2a-bot force-pushed the release-please--branches--main branch 2 times, most recently from b023180 to dabcccc Compare September 2, 2025 16:54
@a2a-bot a2a-bot force-pushed the release-please--branches--main branch from dabcccc to 7253018 Compare September 2, 2025 16:56
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.

[Bug]: A2A DataPart proto missing metadata field [Bug]: FilePart.name field missing in gRPC spec
1 participant