Skip to content

chore(1.0-dev): release 1.0.0-alpha.0#818

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.0#818
a2a-bot wants to merge 1 commit into1.0-devfrom
release-please--branches--1.0-dev

Conversation

@a2a-bot
Copy link
Collaborator

@a2a-bot a2a-bot commented Mar 12, 2026 •
edited
Loading

🤖 I have created a release beep boop

1.0.0-alpha.0 (2026-03-12)

⚠ BREAKING CHANGES

  • client: introduce ServiceParameters for extensions and include it in ClientCallContext (#784)
  • client: rename "callback" -> "push_notification_config" (#749)
  • Update to Protocol v1.0.0-rc and fix all tests (#665)
  • upgrade SDK to A2A 1.0 specs (#572)

Features

  • Add protocol_version column to Task and PushNotificationConfig models and create a migration (#789) (2e2d431)
  • add async context manager support to BaseClient (#688) (ae9dc88)
  • add async context manager support to ClientTransport (#682) (2e45c0d)
  • Add client-side extension support (#525) (9a92bd2)
  • Add custom ID generators to SimpleRequestContextBuilder (#594) (04bcafc)
  • add GetExtendedAgentCardRequest as input parameter to GetExtendedAgentCard method (#767) (13a092f)
  • Add validation for the JSON-RPC version (#808) (6eb7e41)
  • client: allow specifying history_length via call-site MessageSendConfiguration in BaseClient.send_message (53bbf7a)
  • client: expose close() and async context manager support on abstract Client (#719) (e25ba7b)
  • compat: AgentCard backward compatibility helpers and tests (#760) (81f3494)
  • compat: GRPC client compatible with 0.3 server (#779) (0ebca93)
  • compat: GRPC Server compatible with 0.3 client (#772) (80d827a)
  • compat: legacy v0.3 protocol models, conversion logic and utilities (#754) (26835ad)
  • compat: REST and JSONRPC clients compatible with 0.3 servers. (#798) (08794f7), closes #742
  • compat: REST and JSONRPC servers compatible with 0.3 clients. (#795) (9856054), closes #742
  • compat: set a2a-version header to 1.0.0 (#764) (4cb68aa)
  • compat: Unify v0.3 REST url prefix and expand cross-version tests (#820) (0925f0a)
  • Database forward compatibility: make owner field optional (#812) (cc29d1f)
  • handle tenant in Client (#758) (5b354e4)
  • Implement a vertex based task store (#752) (fa14dbf)
  • Implement a vertex based task store for the 1.0 branch (#791) (3b1eef7), closes #751
  • Implement Agent Card Signing and Verification per Spec (8a76730)
  • implement missing push notifications related methods (#711) (041f0f5)
  • implement rich gRPC error details per A2A v1.0 spec (#790) (245eca3)
  • jsonrpc: add option to disable oversized payload check in JSONRPC applications (ba142df)
  • rest, jsonrpc: Add client-side extension support (9a92bd2)
  • rest: add tenant support to rest (#773) (4771b5a)
  • send task as a first subscribe event (#716) (e71ac62)
  • server, grpc: Implement tenant context propagation for gRPC requests. (#781) (164f919)
  • server, json-rpc: Implement tenant context propagation for JSON-RPC requests. (#778) (72a330d)
  • server: add v0.3 legacy compatibility for database models (#783) (08c491e)
  • server: implement Resource Scoping for tasks and push notifications (#709) (f0d4669)
  • spec: Add tasks/list method with filtering and pagination to the specification (#511) (d5818e5)
  • support async card modifiers (#654) (a802500)
  • support disabling OTel instrumentation via env var (#611) (72216b9)
  • use StreamResponse as push notifications payload (#724) (a149a09)

Bug Fixes

  • add history length and page size validations (#726) (e67934b), closes #515
  • add metadata to send message request (12b4a1d)
  • client: align send_message signature with BaseClient (#740) (57cb529)
  • core: preserve legitimate falsy values in _clean_empty (#713) (7632f55)
  • deps: DeprecationWarning on HTTP_413_REQUEST_ENTITY_TOO_LARGE (#693) (9968f9c)
  • do not crash on SSE comment line (#636) (3dcb847)
  • Ensure metadata propagation for Task ToProto and FromProto conversion (#557) (fc31d03)
  • fix bad "list tasks" merge for JSON-RPC (#698) (0623015)
  • get_agent_card tailing slash when agent_card_path="" (#799) (#800) (a55c97e)
  • gRPC metadata header casing and invocation_metadata() call (#676) (390b763)
  • grpc: Add extensions to Artifact converters. (#523) (c03129b)
  • handle parsing error in REST (#806) (bbd09f2)
  • handle REST query params as per 1.0 spec (#804) (45b3059)
  • Improve error handling for Timeout exceptions on REST and JSON-RPC clients (#690) (2acd838)
  • Improve streaming errors handling (#576) (7ea7475)
  • incorporate latest 1.0 proto changes (#788) (47a5959), closes #559
  • jsonrpc, rest: extensions support in get_card methods in json-rpc and rest transports (#564) (847f18e)
  • map rejected task state in proto converters (#668) (957e92b), closes #625
  • properly handle unset and zero history length (#717) (72a1007)
  • remove v1 from HTTP+REST/JSON paths (#765) (627ae0b)
  • return background task from consume_and_break_on_interrupt to prevent GC (#775) (a236d4d)
  • return entire history when history_length=0 (#537) (acdc0de)
  • return mandatory fields from list_tasks (#710) (6132053), closes #515
  • return updated agent_card in JsonRpcTransport.get_card() (#552) (0ce239e)
  • server: fix deadlocks on agent execution failure in non-streaming (#614) (d3c973f)
  • taskslist error on invalid page token and response serialization (#814) (a102d31)
  • use correct REST path for Get Extended Agent Card operation (#769) (ced3f99), closes #559
  • use default_factory for mutable field defaults in ServerCallContext (#744) (22b25d6)

Documentation

  • explicitly mention supported spec version and transports in readme (#681) (c91d4fb), closes #677
  • Fixing typos (#586) (5fea21f)
  • Update README to include Code Wiki badge (2698cc0)

Miscellaneous Chores

Code Refactoring

  • client: introduce ServiceParameters for extensions and include it in ClientCallContext (#784) (942f4ae)
  • client: rename "callback" -> "push_notification_config" (#749) (7dec763)
  • Move agent card signature verification into A2ACardResolver (6fa6a6c)
  • Update to Protocol v1.0.0-rc and fix all tests (#665) (3358305)
  • upgrade SDK to A2A 1.0 specs (#572) (1cc993c)

This PR was generated with Release Please. See documentation.

@a2a-bot a2a-bot requested a review from a team as a code owner March 12, 2026 08:46
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Mar 12, 2026

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 marks the release of version 0.3.25, incorporating a substantial collection of updates, new functionalities, and critical bug fixes. The primary goal of this release is to advance the SDK towards A2A 1.0 specifications, enhance client and server capabilities, and improve overall stability and developer experience. It includes several breaking changes to align with the new protocol, alongside numerous features for extended functionality and a wide array of bug resolutions to address previous issues.

Highlights

  • Breaking Changes: Introduced ServiceParameters for extensions in ClientCallContext and renamed 'callback' to 'push_notification_config' in the client. The SDK has been upgraded to A2A 1.0 specifications, including an update to Protocol v1.0.0-rc, and opentelemetry is now an optional dependency. Custom __getattr__ and __setattr__ for camelCase fields in types.py have been removed, and the Agent Card Well-Known Path was updated to /.well-known/agent-card.json.
  • New Features: Added support for append and last_chunk to TaskUpdater.add_artifact, new helper methods get_artifact_text(), get_data_parts(), and get_file_parts(). metadata can now be passed to TaskUpdater.update_status() and RequestContext. A protocol_version column was added to Task and PushNotificationConfig models, along with a migration. Client-side extension support was introduced, and async context manager support was added to BaseClient and ClientTransport.
  • Bug Fixes: Resolved issues where consume_all didn't catch asyncio.TimeoutError in Python 3.10, and added __str__ and __repr__ methods to ServerError. Input validations were added for empty message content, task context IDs, and task IDs in TaskManager. Missing mime_type and name in proto conversion utils were addressed, and a fix was implemented for client hangs when implementing AgentExecutor.
  • Compatibility and Refactoring: Significant work was done on compatibility, including AgentCard backward compatibility helpers, and making gRPC, REST, and JSONRPC clients and servers compatible with 0.3 versions. The SDK was upgraded to A2A 1.0 specs, and the push_notifier interface was removed in favor of push_notification_config_store and push_notification_sender.
Changelog
Ignored Files
  • Ignored by pattern: CHANGELOG.md (1)
    • CHANGELOG.md
Activity
  • The pull request was automatically generated by a robot, a2a-bot, using Release Please.
  • The PR description indicates this is a release of version 0.3.25, with a detailed changelog of features, bug fixes, and breaking changes.
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[bot]
gemini-code-assist bot reviewed Mar 12, 2026
View reviewed changes
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 pull request is an automated release for version 0.3.25. While the change to .release-please-manifest.json is mechanically correct for the release process, there's a significant issue with the version number itself. The release contains numerous breaking changes, as detailed in the description, but is being versioned as a patch release. According to semantic versioning principles, this should be a minor version bump (e.g., to 0.4.0) for a pre-1.0.0 project. This incorrect versioning could cause significant problems for downstream consumers of this library.

@a2a-bot a2a-bot changed the title chore(1.0-dev): release 0.3.25 chore(1.0-dev): release 1.0.0-alpha.0 Mar 12, 2026
@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch 2 times, most recently from 6df5830 to bdda6ea Compare March 12, 2026 08:54
ishymko
ishymko requested changes Mar 12, 2026
View reviewed changes
Copy link
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.

Do not merge, release-please experimentation.

@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch 7 times, most recently from 4faa153 to e77bd74 Compare March 12, 2026 16:08
@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch from e77bd74 to e1dbc5e Compare March 12, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ishymko ishymko ishymko requested changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@a2a-bot @ishymko