Skip to content

chore(1.0-dev): release 1.0.0-alpha.1#861

Open
a2a-bot wants to merge 1 commit into1.0-devfrom
release-please--branches--1.0-dev
Open

chore(1.0-dev): release 1.0.0-alpha.1#861
a2a-bot wants to merge 1 commit into1.0-devfrom
release-please--branches--1.0-dev

Conversation

@a2a-bot
Copy link
Copy Markdown
Collaborator

@a2a-bot a2a-bot commented Mar 18, 2026

🤖 I have created a release beep boop

1.0.0-alpha.1 (2026-03-27)

⚠ BREAKING CHANGES

  • server: migrate from Application wrappers to Starlette route-based endpoints for rest (#892)
  • server: migrate from Application wrappers to Starlette route-based endpoints for jsonrpc (#873)

Features

  • A2A Version Header validation on server side. (#865) (b261ceb)
  • EventQueue - unify implementation between python versions (#877) (7437b88), closes #869
  • InMemoryTaskStore creates a copy of Task by default to make it consistent with database task stores (#887) (8c65e84), closes #869
  • server: add async context manager support to EventQueue (#743) (f68b22f)
  • server: validate presence according to google.api.field_behavior annotations (#870) (4586c3e)

Bug Fixes

  • #898. (6fa139e)
  • Add packaging to base dependencies (#897) (7a9aec7)
  • fix athrow() RuntimeError on streaming responses (#912) (ca7edc3)
  • fix docstrings related to CallContextBuilder args in constructors and make ServerCallContext mandatory in compat folder (#907) (9cade9b)
  • fix error handling for gRPC and SSE streaming (#879) (2b323d0)
  • fix REST error handling (#893) (405be3f)
  • Remove unconditional SQLAlchemy dependency from SDK core (#898) (ab762f0), closes #883
  • replace stale entry in a2a.types.all with actual import name (#902) (05cd5e9)

Documentation

  • add Database Migration Documentation (#864) (fd12dff)

Code Refactoring

  • server: migrate from Application wrappers to Starlette route-based endpoints for jsonrpc (#873) (734d062)
  • server: migrate from Application wrappers to Starlette route-based endpoints for rest (#892) (4be2064)

This PR was generated with Release Please. See documentation.

@a2a-bot a2a-bot requested a review from a team as a code owner March 18, 2026 10:03
@gemini-code-assist
Copy link
Copy Markdown
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 represents an automated release for version "1.1.0-alpha.0", generated by Release Please. It incorporates a new feature that introduces asynchronous context manager support for the EventQueue in the server, enhancing its capabilities.

Highlights

  • Version Update: The project's version has been incremented to "1.1.0-alpha.0" as part of this release.
  • New Feature: Asynchronous context manager support has been added to the EventQueue within the server component.
Ignored Files
  • Ignored by pattern: CHANGELOG.md (1)
    • CHANGELOG.md
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.

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 is an automated release for version 1.1.0-alpha.0, generated by release-please. The change updates the version in .release-please-manifest.json, which is consistent with the release process.

Copy link
Copy Markdown
Member

@ishymko ishymko left a comment

Choose a reason for hiding this comment

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

Safety net blocking comment.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 18, 2026

🧪 Code Coverage (vs 1.0-dev)

⬇️ Download Full Report

No coverage changes.

Generated by coverage-comment.yml

@a2a-bot a2a-bot changed the title chore(1.0-dev): release 1.1.0-alpha.0 chore(1.0-dev): release 1.0.0-alpha.1 Mar 18, 2026
@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch 11 times, most recently from bc3c87a to 2afa628 Compare March 24, 2026 16:11
@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch 6 times, most recently from 6f5a0b7 to 7a2da7d Compare March 27, 2026 09:28
@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch from 7a2da7d to dd7da8a Compare March 27, 2026 14:49
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