Skip to content

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

Merged
ishymko merged 2 commits into1.0-devfrom
release-please--branches--1.0-dev
Mar 17, 2026
Merged

chore(1.0-dev): release 1.0.0-alpha.0#828
ishymko merged 2 commits into1.0-devfrom
release-please--branches--1.0-dev

Conversation

@a2a-bot
Copy link
Collaborator

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

🤖 I have created a release beep boop

⚠ BREAKING CHANGES

  • spec: upgrade SDK to A2A 1.0 spec and use proto-based types (#572, #665, #804, #765)
  • client: introduce ServiceParameters for extensions and include it in ClientCallContext (#784)
  • client: rename "callback" -> "push_notification_config" (#749)
  • client: transport agnostic interceptors (#796) (a910cbc)
  • add protocol_version column to Task and PushNotificationConfig models and create a migration (#789) (2e2d431)
  • server: implement Resource Scoping for tasks and push notifications (#709) (f0d4669)

Features

  • add GetExtendedAgentCardRequest as input parameter to GetExtendedAgentCard method (#767) (13a092f)
  • add validation for the JSON-RPC version (#808) (6eb7e41)
  • 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)
  • compat: REST and JSONRPC servers compatible with 0.3 clients (#795) (9856054)
  • 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 missing push notifications related methods (#711) (041f0f5)
  • implement rich gRPC error details per A2A v1.0 spec (#790) (245eca3)
  • 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)
  • spec: add tasks/list method with filtering and pagination to the specification (#511) (d5818e5)
  • use StreamResponse as push notifications payload (#724) (a149a09)
  • rest: update REST error handling to use google.rpc.Status (#838) (ea7d3ad)

Bug Fixes

  • add history length and page size validations (#726) (e67934b)
  • allign error codes with the latest spec (#826) (709b1ff)
  • client: align send_message signature with BaseClient (#740) (57cb529)
  • get_agent_card trailing slash when agent_card_path="" (#799) (#800) (a55c97e)
  • handle parsing error in REST (#806) (bbd09f2)
  • Improve error handling for Timeout exceptions on REST and JSON-RPC clients (#690) (2acd838)
  • Improve streaming errors handling (#576) (7ea7475)
  • properly handle unset and zero history length (#717) (72a1007)
  • return entire history when history_length=0 (#537) (acdc0de)
  • return mandatory fields from list_tasks (#710) (6132053)
  • taskslist error on invalid page token and response serialization (#814) (a102d31)
  • use correct REST path for Get Extended Agent Card operation (#769) (ced3f99)
  • Use POST method for REST endpoint /tasks/{id}:subscribe (#843) (a0827d0)

This PR was generated with Release Please. See documentation.

@a2a-bot a2a-bot requested a review from a team as a code owner March 13, 2026 10:37
@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 represents the release of version 1.0.0-alpha.0, marking a significant milestone in aligning the project with the A2A 1.0 protocol specifications. It encompasses a broad range of changes, including critical breaking changes, numerous new features, and essential bug fixes. Key areas of focus include enhancing client-side extension capabilities, ensuring robust backward compatibility with previous protocol versions, and refining core functionalities such as task management, push notifications, and agent card handling.

Highlights

  • Protocol and SDK Upgrade: The SDK has been upgraded to align with A2A 1.0 specifications, including an update to Protocol v1.0.0-rc, which introduces several breaking changes and ensures future compatibility.
  • Client-side Extensions and Service Parameters: Introduced ServiceParameters for extensions within ClientCallContext and added general client-side extension support across REST, JSONRPC, and gRPC clients.
  • Push Notification Configuration Renaming: The 'callback' parameter has been renamed to 'push_notification_config' in client configurations, reflecting a clearer intent for push notification management.
  • Backward Compatibility Enhancements: Extensive compatibility features have been added for gRPC, REST, and JSONRPC clients and servers to ensure interoperability with v0.3 versions of the protocol, including legacy model support and unified URL prefixes.
  • Vertex-based Task Store Implementation: A new vertex-based task store has been implemented, improving the storage and management of tasks within the system.
  • Agent Card Signing and Verification: Implemented Agent Card Signing and Verification as per the A2A specification, enhancing security and integrity of agent cards.
  • Tenant Context Propagation: Tenant context propagation has been implemented for both gRPC and JSON-RPC requests on the server side, improving multi-tenancy support.
Changelog
  • .release-please-manifest.json
    • Updated the manifest to reflect the new release version 1.0.0-alpha.0.
Ignored Files
  • Ignored by pattern: CHANGELOG.md (1)
    • CHANGELOG.md
Activity
  • The pull request was automatically generated by the Release Please bot to create the 1.0.0-alpha.0 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.

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 1.0.0-alpha.0, generated by Release Please. The change updates the .release-please-manifest.json file to reflect the new version. This is a standard and correct modification for an automated release process. After reviewing the changes, I have found no issues or areas for improvement.

@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch from 381fb24 to 40c4f03 Compare March 13, 2026 10:44
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 4 times, most recently from 24db503 to d113e4a Compare March 16, 2026 20:58
@github-actions
Copy link

github-actions bot commented Mar 16, 2026

🧪 Code Coverage (vs 1.0-dev)

⬇️ Download Full Report

No coverage changes.

Generated by coverage-comment.yml

@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch 3 times, most recently from 5780385 to 00fdaa2 Compare March 17, 2026 13:13
@a2a-bot a2a-bot force-pushed the release-please--branches--1.0-dev branch from fbc577d to af16adf Compare March 17, 2026 13:57
@ishymko ishymko merged commit fce163c into 1.0-dev Mar 17, 2026
10 checks passed
@ishymko ishymko deleted the release-please--branches--1.0-dev branch March 17, 2026 14:06
@a2a-bot
Copy link
Collaborator Author

a2a-bot commented Mar 17, 2026

🤖 Created releases:

🌻

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