47 Commits

Author SHA1 Message Date
Luca Muscariello
b86d8bb2ed
docs: clean up documentation build chain and fix broken links (#1400)
- Move a2a.proto to specification/ root
- Update build scripts and macros to support new proto location
- Fix broken internal links and anchor references in specification.md
- Update .gitignore to properly exclude generated SDK docs
- Configure Sphinx to suppress external SDK warnings
- Fix MkDocs redirects and Python SDK toctree structure

---------

Signed-off-by: Luca Muscariello <muscariello@ieee.org>
2026-01-29 21:00:02 +01:00
Darrel
b078419954
docs(spec): Large refactor of specification to separate application protocol definition from mapping to transports. (#1160)
Related to #1151 

Fixes https://github.com/a2aproject/A2A/issues/998
Fixes https://github.com/a2aproject/A2A/issues/1091
Fixes https://github.com/a2aproject/A2A/issues/1072
Fixes https://github.com/a2aproject/A2A/issues/1058
Fixes https://github.com/a2aproject/A2A/issues/975
Fixes https://github.com/a2aproject/A2A/issues/1105
Fixes https://github.com/a2aproject/A2A/issues/989
Fixes https://github.com/a2aproject/A2A/issues/1189
Fixes https://github.com/a2aproject/A2A/issues/1187
Fixes https://github.com/a2aproject/A2A/issues/1177
Fixes https://github.com/a2aproject/A2A/issues/1180
Fixes https://github.com/a2aproject/A2A/issues/1172



In order to more effectively describe the A2A protocol in a consistent
way across different protocols, this PR refactors the specification to
describe the application protocol in a transport agnostic way, and then
have separate sections that describe how each of the transports map to
the abstract application protocol. To see a preview of what it looks
like you can go here
https://purple-moss-0838db51e.3.azurestaticapps.net/specification/

The goal of the TSC is to use the changes in this PR as the baseline for
a v1.0 Release Candidate. This will give SDK maintainers an stable
document to validate the changes in the specification through
implementations before v1.0 release.

There are many pending feature requests for the A2A specifications that
the TSC are supportive of. However, getting a stable, consistent,
unambiguous, multi-protocol specification is necessary before additional
features can be added safely.

## Document Restructuring 

- [A2A
Operations](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#3-a2a-protocol-operations)
are described independent of wire protocol
- [Protocol Data
Model](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#4-protocol-data-model)
is described using protobuf as source of truth. All other serializations
are derived from that.
- Protocol bindings (formerly described as transports) are now described
in their own sections
-
[JSON-RPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#9-json-rpc-protocol-binding)
-
[gRPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#10-grpc-protocol-binding)
-
[HTTP](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#11-httpjsonrest-protocol-binding)
- [Operation Parameters
](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#32-operation-parameter-objects)
describe structures reused across different operations
- [Operation
Semantics](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#33-operation-semantics)
describe common behavior patterns across operations

## New Sections

- [Requirements
Language](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#21-requirements-language)
- [Capability
Validation](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#334-capability-validation)
- [Abstract description of error
handling](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#332-error-handling)
- [Abstract description of
"headers"](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#325-headers)
-
[Extensions](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#46-extensions)
-
[Versioning](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#36-versioning)
- [Custom Binding
Guidelines](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#12-custom-binding-guidelines)
- [JSON Field Naming
Conventions](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#54-json-field-naming-convention)
- [Data Type
Conventions](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#55-data-type-conventions)
- [Security
Considerations](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#77-security-considerations)
- [Agent Card
Signing](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#84-agent-card-signing)
- [IANA
Considerations](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#13-iana-considerations)

## Protocol Clarifications

- Defining order for events returned from [Stream
Message](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#312-stream-message)
- [JSON
Examples](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#416-filepart)
provided for protobuf definitions of data model objects that previously
used discriminators
- Clarification of returned errors where multiple are applicable. e.g.
[Cancel
Task](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#315-cancel-task)
- Defined returned events and usage scenarios for
[Resubscribe](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#316-resubscribe-to-task)
- Defined protocol binding for errors using protocol native capabilities
for all bindings
-
[JSON-RPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#94-error-handling)
-
[gRPC](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#104-error-handling)
-
[HTTP](https://purple-moss-0838db51e.3.azurestaticapps.net/specification/#115-error-handling)
  
## Artifact Generation

The scripts have been changed to enable a2a.json to be generated from
the a2a.proto so that a2a.proto and specification.md are the only
normative source. Additional work is required to align the generated
a2a.json with the original one.

Release-As: 1.0

---------

Signed-off-by: Luca Muscariello <muscariello@ieee.org>
Signed-off-by: Luca Muscariello <lumuscar@cisco.com>
Co-authored-by: Luca Muscariello <muscariello@ieee.org>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Sam Betts <1769706+Tehsmash@users.noreply.github.com>
2025-11-20 14:52:09 -05:00
Eden Reich
0a9f629e80
feat(spec): Add tasks/list method with filtering and pagination to the specification (#831)
# Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:

- [x] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [x] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [x] Appropriate docs were updated (if necessary)
- [x] Fix existing linting errors (I guess they were already on the main
upstream)

Fixes #761  馃

---------

Signed-off-by: Eden Reich <eden.reich@gmail.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Darrel <darrmi@microsoft.com>
Co-authored-by: Amye Scavarda Perrin <amye@amye.org>
2025-10-16 12:47:20 -07:00
Holt Skinner
00cf76e7bb
fix(spec): Suggest Unique Identifier fields to be UUID (#966) 2025-08-13 20:56:28 +01:00
kthota-g
8d57eba286
docs: Address typos in docstrings and docs. Fixes #940 (#941)
Fixes #940  馃

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-07-31 15:59:53 +01:00
dmandar
6a152a83ad
chore: Update default protocol version to 0.3.0 (#932)
We can push this when we release 0.3.0

Release-As: 0.3.0

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-07-30 14:57:35 +00:00
Mike Smith
e162c0c6c4
feat!: Add mTLS to SecuritySchemes, add oauth2 metadata url field, allow Skills to specify Security (#901)
# Description

This PR makes changes to our security representations in AgentCards:

1. Adds a new MutualTLSSecurityScheme type for indicating mTLS
connection requirements. This matches the same field in the OpenAPI
specification v3.1. This type is pretty lacking: there is no way to
indicate any requirements on the certificate that is presented by the
client. I expect we'll want to extend this in the future (for example,
we may want to allow an agent to indicate that a SPIFFE certificate must
be presented). For now, users are advised to put requirements in the
description field.
2. Adds a field for specifying a URL for OAuth2 provider metadata. This
is planned for OpenAPI Specification v3.2, which has not yet been
released. This allows clients to fetch additional information about the
OAuth provider, such as to discover if they support Dynamic Client
Registration.
3. Allows AgentSkills to specify a `security` field. This allows agents
to indicate security requirements for leveraging a particular skill.

I also clarified the usage and expectations for the `security` field in
the base AgentCard.

This change is marked backwards incompatible due to the addition of the
MutualTLSSecurityScheme, which adds a new type to an exhaustive enum
(the security scheme `anyOf`).

Release-As: 0.3.0

---------

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
2025-07-29 13:39:27 -06:00
kthota-g
6fb2b771b0
ci: Trigger ci build for spec update (#936) 2025-07-29 19:50:41 +01:00
kthota-g
476863efa6
chore: Push to trigger spec update wf (#934)
# Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:

- [ ] Follow the [`CONTRIBUTING`
Guide](https://github.com/a2aproject/A2A/blob/main/CONTRIBUTING.md).
- [ ] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [ ] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 馃

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-07-29 11:16:51 -07:00
kthota-g
2cd7d98bc8
feat!: Add method for fetching extended card (#929)
# Description
This change adds support for a new JSON-RPC method
`agent/getAuthenticatedExtendedCard` for fetching authenticated extended
card.

This is only applicable if `AgentCard.supportsAuthenticatedExtendedCard`
bit is set to `true` that allows fetching authenticated context specific
agent card.

In the previous versions, the extended card was served via
`{AgentCard.url}/../agent/authenticatedExtendedCard` endpoint. This
endpoint is being removed in favor of the JSON-RPC method. This endpoint
will be deprecated in the SDKs and will be removed in a future release.

Release-As: 0.3.0

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-07-29 09:31:45 -07:00
Israel Ekpo
074a3dd06b
docs: Update Docs to Clarify that Task Id Must Be Generated By the A2A Server (#926)
Fixes #925  馃

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2025-07-28 17:03:25 +01:00
Mike Smith
ef4a305053
feat: Add signatures to the AgentCard (#917)
# Description

This introduces a `signatures` field on the AgentCard that contains JWS
formatted signatures. See issue #916 and discussion #199 for further
details, including how signatures are constructed and verified.

Fixes #916 馃
2025-07-25 18:12:25 +00:00
Holt Skinner
23d5c5967b chore: Update spec from #910 2025-07-24 20:20:43 +01:00
Holt Skinner
e834347c27
fix(spec): Add Transport enum to specification (#909)
Adds Enum of supported Transports to Specification, with extensibility
for proprietary protocols.
Adds URL formatting requirement for `AgentInterface.url` and
`AgentCard.url`

Co-authored-by: Stefano Maestri <stefano.maestri@javalinux.it>
2025-07-24 19:56:39 +01:00
Holt Skinner
0c95b1fa8a
docs(spec): Improve docstrings in the specification (#887)
Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-07-18 18:34:47 +01:00
kthota-g
6f1d17ba80
fix: Type fix and doc clarification (#877)
Release-As: 0.2.6

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
2025-07-17 17:10:05 +01:00
Holt Skinner
32f3f9eb2e Revert "feat(spec): Add AGENT_CARD_WELL_KNOWN_URI to spec (#824)"
This reverts commit 66da9d10ee87dc1f8baa20a21360bebbe7d4ff1b.
2025-07-02 13:09:37 -05:00
Holt Skinner
66da9d10ee
feat(spec): Add AGENT_CARD_WELL_KNOWN_URI to spec (#824)
Prevents usage of "Magic Strings" in SDKs, which supports better
adherence to the recommended path for Agent Cards.

NOTE: This path might also need to be changed based on feedback in
https://github.com/protocol-registries/well-known-uris/issues/66 so
having a global constant would make this adjustment easier.

Fixes #816 馃
2025-07-02 11:51:35 -05:00
Holt Skinner
7fd0dcc6e4
chore(spec): Add default value for AgentCard.protocolVersion (#812)
- Prevents a breaking change in the Python Library
2025-06-30 15:19:55 -05:00
dmandar
90fa642094
feat(spec)!: Add a required protocol version to the agent card. (#802)
Add a new protocol version field to the agent card.

Release-As: 0.2.5
2025-06-30 15:04:16 -05:00
Holt Skinner
3590012159
chore(spec): Add @TJS-examples to spec and add missing Union Types (#810)
- **Replaced `@example` with `@TJS-examples`**: All JSDoc `@example`
tags have been converted to `@TJS-examples`, used
by`typescript-json-schema` to generate example values.
- **Completed Union Types**: The `JSONRPCResponse` union type was
incomplete. Added the missing `ListTaskPushNotificationConfigResponse`
and `DeleteTaskPushNotificationConfigResponse` types to make it
consistent with the defined request types.
2025-06-30 19:52:04 +00:00
Holt Skinner
08132ac5c7
docs: Repo Link Updates (#780) 2025-06-23 21:34:48 +02:00
Matteo Murru
419a497f68
docs: Add @TJS-examples for AgentProvider and AgentExtension interfaces (#758)
Add missing `@TJS-examples` annotations to `AgentProvider` and
`AgentExtension` interfaces to improve TypeScript developer experience.

Examples use Google ecosystem references (ai.google.dev, OAuth 2.0) and
follow existing JSDoc patterns in the codebase.

First contribution to open source 鉂わ笍
2025-06-23 13:08:53 +00:00
Holt Skinner
4a5e970ec2
fix(spec): Make AgentCard.additionalInterfaces Optional for backwards compatibility (#760)
The Python SDK expects a value for `additionalInterfaces` if this is not
optional. New versions would be a breaking change.

Unit test output

```
ERROR tests/client/test_client.py - pydantic_core._pydantic_core.ValidationError: 1 validation error for AgentCard
additionalInterfaces
  Field required [type=missing, input_value={'name': 'Hello World Age... tags=['hello world'])]}, input_type=dict]
```

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-06-16 13:00:53 -05:00
Holt Skinner
14424a69d5
fix(spec): Fix casing of types.ts from #749 (#759)
Change from `snake_case` to `camelCase`
2025-06-16 12:46:59 -05:00
pstephengoogle
b35485e02e
feat: Add support for multiple transport announcement in AgentCard (#749)
This is designed to be backward compatible. Existing cards will work and
be correct with this update. New fields are added to the agent card and
default interpretation for these are provided to be backward compatible

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Co-authored-by: tomsun28 <tomsun28@outlook.com>
Co-authored-by: Mike Smith <mikeas@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: kthota-g <kcthota@google.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2025-06-16 11:13:44 -06:00
kthota-g
f355d3e922
feat: Support for multiple pushNotification config per task (#738)
- Support for list pushNotificationConfig for task
- Support for delete pushNotificationConfig
- Get pushNotificationConfig by id or by task
- update protos to use PushNotificationConfig

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-06-14 14:10:46 -07:00
Mike Smith
70f1e2b0c6
feat: Add protocol support for extensions (#716)
# Description

This updates the protocol to support Extensions. Extension profiles are
documents that describe modifications or additions to the core A2A
profile. AgentCards can declare supported extensions via
`capabilities.extensions`. This declaration can include additional
information via `capabilities.extensions.params`. Clients can use this
as a basis for extension negotiation: if a client supports an extension
that the server supports, the client can then follow the protocol
defined by the extension. This can include, but is not specifically
limited to:

1. Requiring specific structure of messages, such as following a
specific schema for a DataPart.
2. Providing additional information in request/response Message and
Artifact objects via their `metadata` field.
3. Exposing additional methods beyond the core A2A protocol methods.

Messages and Artifacts can now include an indication of which extensions
are present in their content. I do not yet know if extension indications
are necessary on other data structures (such as `MessageSendParams` or
`TaskStatus`). I'd say extension indications are not strictly necessary
at all: it's possible to infer that an extension was followed by
inspecting the message content itself (are the metadata fields you
expect present, does the DataPart follow the schema you expect, etc).
However, they are useful for validation and simplifying extension
implementation logic: "you said you followed this extension, so I'll
validate fields are present and then perform my processing".

Fixes #585

---------

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-06-04 10:17:37 -06:00
MUTHU K BOMMIAH
7ec8027b5f
docs: replace all references to 'MIME type' with 'Media Type' in code (#713) 2025-06-03 14:38:58 +00:00
Holt Skinner
e5754fe9a0
ci: Fix Dispatch A2A Update to only include first line (#707) 2025-06-02 13:40:01 -05:00
pstephengoogle
89bb5b8243
feat: Add gRPC and REST definitions to A2A protocol specifications (#695)
- Requires adding a new `PushNotificationConfig.id` field to support
multiple push notification callbacks per task

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
2025-06-02 12:11:28 -06:00
dmandar-google
9f3bb51257
feat(spec): Add an optional iconUrl field to the AgentCard (#687)
New addition to the agentcard: Optional iconUrl field that can point to
an image icon file for the agent.

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-05-29 21:56:55 -07:00
darkhaniop
628380e7e3
fix(spec): Spec inconsistencies and a minor bug (#322)
## Problem

In client-server messaging, the A2A protocol uses the [JSON-RPC
2.0](https://www.jsonrpc.org/specification) format, and the protocol
specification is written using the [JSON-Schema
specification](https://json-schema.org/). Fully complying with the
standards can help validate the payloads more accurately and help better
test different client and server implementations.

In addition to making the A2A spec more compliant with the mentioned
standards, changes in this PR are meant to fix a few minor bugs in the
A2A protocol spec (mismatches from what was implemented in the sample
A2A server and clients.

Addresses issue #353.

## Summary of changes
* Makes field "id" required on requests and responses. This field is
important because, according to the JSON RPC 2.0 spec, a message that
does not have an "id" is considered a notification, and the callee does
not have to send a response to such requests. Similarly, without the
"id" on the responses, the caller cannot correlate the responses to the
pending requests, meaning that fully JSON-RPC-compliant clients would
not be able to resolve such RPC calls.

---
*Edit: clearer wording + add issue references*

*Edit2: the scope of this PR has been reduced due to other updates
fixing parts of the spec, summary items were edited to reflect what has
already been addressed in other PRs.*

---

## (OLD) Summary of changes

* Add a missing definition for "TaskSendParams.acceptedOutputModes"
(described in #354). Fixed in #599.

* Remove "default" values for "const" fields. Compliance with JSON
schema, version `>=draft-6` and reduce ambiguity.
https://json-schema.org/understanding-json-schema/reference/const
Fixed in #599

* Make fields "jsonrpc" and "id" required on requests and responses.
Compliance with JSON-RPC 2.0.

* Make fields "error.code" and "error.message" required on errors. Fixed
in #599.

* In a few places, sort non-top-level dict keys to make them more
aligned with the pydantic JSON schema outputs. Since now, we are
discouraged from editing the spec manually, this item also drops out of
the scope of our concerns.

* The initial commit in this PR also included cleaning up several
unnecessary "null" types, which were addressed more thoroughly in #352.

## (OLD) Additional notes

While I sorted dictionaries within each model so that the keys of each
model would be in the same order as the pydantic-based scripts' exports,
at the same time, **I decided not to sort the top-level keys**
(`$defs/ModelKey`). Because doing so would make the diff ugly and harder
to read the applied changes. The top-level key sorting can be done
afterward.

---------

Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
Co-authored-by: kthota-g <kcthota@google.com>
2025-05-27 16:20:24 -07:00
Holt Skinner
729988a3f5
refactor: Remove Samples/Demo/test directories and change references to google/A2A (#668) 2025-05-27 16:31:32 -05:00
Shingo OKAWA
38c1fa5b23
chore: fix typo in types.ts doc comment (#626)
Signed-off-by: Shingo OKAWA <shingo.okawa.g.h.c@gmail.com>
2025-05-22 09:25:31 -07:00
Holt Skinner
d49241cbc9
ci: Add Auto-generation of a2a.json from types.ts (#620)
Use @a2a-bot to auto-generate `specification/json/a2a.json` whenever
`types/src/types.ts` is updated in a PR.

---------

Co-authored-by: a2a-bot <a2a-bot@google.com>
2025-05-21 12:26:05 -07:00
Holt Skinner
4d4f04f8a6
chore: Formatting for types.ts and a2a.json (#543) 2025-05-21 11:48:09 -07:00
dmandar-google
e0a3070fc2
feat: Add a new boolean for supporting authenticated extended cards (#618)
New boolean field `supportsAuthenticatedExtendedCard` that if true,
indicates an extended agent card is available at an authenticated
endpoint.
2025-05-21 10:35:55 -07:00
Holt Skinner
65d539db3e
docs: Update Information about spec generation (#610) 2025-05-20 14:35:29 -07:00
swapydapy
5368e7728c
feat: Add optional referenceTaskIds for task followups (#608)
### Problem
Clients need to follow up or refine previously created tasks by agents.

### Proposal
**New Task in same contextId (Preferred)**

Context can be thought of as a larger goal from a client perspective.
Clients can use the same contextId from the previous task and send a
message for refinement or followup. Agents should spawn up new tasks.
Tasks cannot restart processing from terminal states (Completed, Failed
and Cancelled).

### Proposed API Change

* Addition of optional `referenceTaskIds` field in the `Message` object.
* Optional addition of `referenceArtifactId` in `part` metadata of
`Message` object.
2025-05-20 12:51:13 -07:00
kthota-g
2d386d49e4
chore: update docstrings for types (#607)
# Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:

- [ ] Follow the [`CONTRIBUTING`
Guide](https://github.com/google/A2A/blob/main/CONTRIBUTING.md).
- [ ] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [ ] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 馃
2025-05-20 12:33:46 -07:00
kthota-g
50a6d6d916
chore: update main with changes from next (#599)
Changes from `next` to be merged into `main`
2025-05-20 00:41:29 -07:00
Andy Tien
8a44cfffd9
fix(spec): Optimize the camel case naming. (#534)
# Description

feat: Optimize the camel case naming.

- [x] Follow the [`CONTRIBUTING`
Guide](https://github.com/google/A2A/blob/main/CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- [x] Ensure the tests and linter pass (Run `nox -s format` from the
repository root to format)
- [x] Appropriate docs were updated (if necessary)

Co-authored-by: Andy Tian <tianxingzhivlog@gmail.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
2025-05-14 16:16:16 -06:00
Jeremy Whitlock
16d9fe158f
Remove 'null' support for JSON Schema types (#352)
This commit also makes running the A2A specification tests much simpler.

Fixes #264 馃
2025-04-30 20:24:57 -04:00
kthota-g
7fba74e52e
JSON schema fixes for #173 and #172 (#175) 2025-04-15 13:37:08 -07:00
James Heller
43fd3e3724
Add history array to Task schema definition (#167) 2025-04-15 10:26:12 -07:00
Rajesh Velicheti
47b436f3d4 Initial commit 2025-04-08 19:47:43 -07:00