Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: a2aproject/a2a-java
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.2.3.Beta1
Choose a base ref
...
head repository: a2aproject/a2a-java
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.2.5
Choose a head ref
  • 19 commits
  • 81 files changed
  • 6 contributors

Commits on Jul 8, 2025

  1. chore: Prepare 0.2.3.Beta1 release (#174) 

    # 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕
    @kabir
    kabir authored Jul 8, 2025
    Configuration menu
    Copy the full SHA
    abe92d8 View commit details
    Browse the repository at this point in the history

Commits on Jul 9, 2025

  1. fix: (run-tck): update TCK repository reference (#175) 

    The a2a-tck repository has been moved from maeste/a2a-tck to
a2aproject/a2a-tck.

This commit updates the checkout action in the run-tck.yml workflow to
point to the new repository location.

# 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕
    @maeste
    maeste authored Jul 9, 2025
    Configuration menu
    Copy the full SHA
    03ed17e View commit details
    Browse the repository at this point in the history

Commits on Jul 11, 2025

  1. feat: Externalise sdk-jakarta, add list of integrations and make Quar… 

    …kus reference implementation (#178)

# 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #176  🦕
    @kabir
    kabir authored Jul 11, 2025
    Configuration menu
    Copy the full SHA
    8d31ddf View commit details
    Browse the repository at this point in the history

  2. fix: Incorporate latest feedback from #138 (#182) 

    # Description

This PR incorporates the latest feedback from
#138.

- [x] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)
    @fjuma
    fjuma authored Jul 11, 2025
    Configuration menu
    Copy the full SHA
    d121d5c View commit details
    Browse the repository at this point in the history

Commits on Jul 14, 2025

  1. fix: client sse (#177) 

    fix client send stream message without set text/event-stream.

# 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](../CONTRIBUTING.md).
- [ ] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [ ] Ensure the tests pass
- [ ] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

---------

Co-authored-by: chenkangqiang <chenkangqiang@meituan.com>
    @ChenKangQiang
    ChenKangQiang and chenkangqiang authored Jul 14, 2025
    Configuration menu
    Copy the full SHA
    c3e7f9e View commit details
    Browse the repository at this point in the history

  2. feat: Rework tests so they don't rely on running in container (#185) 

    # Description

While running the tests in a container is possible in Quarkus, and in
WildFly (with Arquillian), this might not be possible for all Java
runtimes.

Hence, this PR changes the tests so the interactions with the TaskStore,
QueueManager, and being notified about the subscription to a streaming
request happening.


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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕
    @kabir
    kabir authored Jul 14, 2025
    Configuration menu
    Copy the full SHA
    f902f18 View commit details
    Browse the repository at this point in the history

Commits on Jul 17, 2025

  1. chore: Clean up AbstractA2AServerTest (#187) 

    # 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
    @kabir @gemini-code-assist
    kabir and gemini-code-assist[bot] authored Jul 17, 2025
    Configuration menu
    Copy the full SHA
    d726d0f View commit details
    Browse the repository at this point in the history

  2. feat: Implement the spec updates for v0.2.4 and v0.2.5 (#192) 

    # Description

This PR brings in the updates required to align with the A2A v0.2.4 and
v0.2.5 spec versions.

- [X] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [X] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [X] Ensure the tests pass
- [X] Appropriate READMEs were updated (if necessary)

Fixes #183  🦕
    @fjuma
    fjuma authored Jul 17, 2025
    Configuration menu
    Copy the full SHA
    93d6bae View commit details
    Browse the repository at this point in the history

Commits on Jul 18, 2025

  1. fix: Fix JSONRPCVoidResponseSerializer constructor (#193) 

    # Description

- [X] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [X] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [X] Ensure the tests pass
- [X] Appropriate READMEs were updated (if necessary)
    @fjuma
    fjuma authored Jul 18, 2025
    Configuration menu
    Copy the full SHA
    da6e49d View commit details
    Browse the repository at this point in the history

  2. fix: Remove unnecessary check in the tck AgentExecutor implementation (… 

    …#194)

# Description

**NOTE:** This will fail the TCK tests until
a2aproject/a2a-tck#34 is included in a tag
Depends on a2aproject/a2a-tck#34


- [X] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [X] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [X] Ensure the tests pass
- [X] Appropriate READMEs were updated (if necessary)
    @fjuma
    fjuma authored Jul 18, 2025
    Configuration menu
    Copy the full SHA
    b420b52 View commit details
    Browse the repository at this point in the history

Commits on Jul 21, 2025

  1. chore: Release 0.2.5.Beta1 and move to next snapshot (#196) 

    # 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕
    @kabir
    kabir authored Jul 21, 2025
    Configuration menu
    Copy the full SHA
    bc3c8cb View commit details
    Browse the repository at this point in the history

  2. chore: automate releasing to Maven central when a tag happens. (#197) 

    # 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕
    @kabir
    kabir authored Jul 21, 2025
    Configuration menu
    Copy the full SHA
    6f5c8be View commit details
    Browse the repository at this point in the history

  3. Prepare 0.2.5.Beta2 so we can check the release to maven job

    @kabir
    kabir committed Jul 21, 2025
    Configuration menu
    Copy the full SHA
    b5c08bd View commit details
    Browse the repository at this point in the history

  4. Bump to next SNAPSHOT

    @kabir
    kabir committed Jul 21, 2025
    Configuration menu
    Copy the full SHA
    b568d03 View commit details
    Browse the repository at this point in the history

  5. chore: make workflows manually runnable (#195) 

    # 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](../CONTRIBUTING.md).
- [x] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [x] Ensure the tests pass
- [x] Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕
    @kabir
    kabir authored Jul 21, 2025
    Configuration menu
    Copy the full SHA
    865ee63 View commit details
    Browse the repository at this point in the history

  6. chore: release 0.2.5 

    Release-As: 0.2.5
    @fjuma
    fjuma committed Jul 21, 2025
    Configuration menu
    Copy the full SHA
    483760f View commit details
    Browse the repository at this point in the history

  7. chore: Next is 0.2.5

    @fjuma
    fjuma committed Jul 21, 2025
    Configuration menu
    Copy the full SHA
    c6627e4 View commit details
    Browse the repository at this point in the history

  8. chore: release 0.2.5 

    Release-As: 0.2.5
    @fjuma
    fjuma committed Jul 21, 2025
    Configuration menu
    Copy the full SHA
    d34844d View commit details
    Browse the repository at this point in the history

  9. chore: Release 0.2.5

    @fjuma
    fjuma committed Jul 21, 2025
    Configuration menu
    Copy the full SHA
    f4ea4ba View commit details
    Browse the repository at this point in the history
Loading