Skip to content

Conversation

@coolbeevip
Copy link
Contributor

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.
  • Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
    • Important Prefixes for release-please:
      • fix: which represents bug fixes, and correlates to a SemVer 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 and linter pass (Run nox -s format from the repository root to format)
  • Appropriate docs were updated (if necessary)

Fixes #176 🦕

@coolbeevip coolbeevip requested a review from a team as a code owner June 12, 2025 08:47
@google-cla
Copy link

google-cla bot commented Jun 12, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@coolbeevip coolbeevip closed this Jun 12, 2025
@coolbeevip coolbeevip reopened this Jun 12, 2025
@holtskinner holtskinner changed the title feat: Add append and last_chunk to add_artifact method on TaskUpdater feat: Add append and last_chunk to add_artifact method on TaskUpdater Jun 17, 2025
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
@kthota-g kthota-g merged commit 8c6560f into a2aproject:main Jun 17, 2025
6 checks passed
@coolbeevip coolbeevip deleted the issue-176 branch June 18, 2025 00:40
holtskinner added a commit that referenced this pull request Jun 24, 2025
…Updater` (#186)

# 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/google-a2a/a2a-python/blob/main/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 and linter pass (Run `nox -s format` from the
repository root to format)
- [x] Appropriate docs were updated (if necessary)

Fixes #176  🦕

---------

Co-authored-by: kthota-g <kcthota@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
holtskinner added a commit that referenced this pull request Jun 30, 2025
…Updater` (#186)

# 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/google-a2a/a2a-python/blob/main/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 and linter pass (Run `nox -s format` from the
repository root to format)
- [x] Appropriate docs were updated (if necessary)

Fixes #176  🦕

---------

Co-authored-by: kthota-g <kcthota@google.com>
Co-authored-by: Holt Skinner <13262395+holtskinner@users.noreply.github.com>
holtskinner added a commit that referenced this pull request Jun 30, 2025
🤖 I have created a release *beep* *boop*
---


##
[0.2.10](v0.2.8...v0.2.10)
(2025-06-30)


### ⚠ BREAKING CHANGES

* Update to A2A Spec Version
[0.2.5](https://github.com/a2aproject/A2A/releases/tag/v0.2.5)
([#197](#197))

### Features

* Add `append` and `last_chunk` to `add_artifact` method on
`TaskUpdater`
([#186](#186))
([8c6560f](8c6560f))
* add a2a routes to existing app
([#188](#188))
([32fecc7](32fecc7))
* Add middleware to the client SDK
([#171](#171))
([efaabd3](efaabd3))
* Add more task state management methods to TaskUpdater
([#208](#208))
([2b3bf6d](2b3bf6d))
* raise error for tasks in terminal states
([#215](#215))
([a0bf13b](a0bf13b))

### Bug Fixes

* `consume_all` doesn't catch `asyncio.TimeoutError` in python 3.10
([#216](#216))
([39307f1](39307f1))
* Append metadata and context id when processing TaskStatusUpdateE…
([#238](#238))
([e106020](e106020))
* Fix reference to `grpc.aio.ServicerContext`
([#237](#237))
([0c1987b](0c1987b))
* Fixes Short Circuit clause for context ID
([#236](#236))
([a5509e6](a5509e6))
* Resolve `APIKeySecurityScheme` parsing failed
([#226](#226))
([aa63b98](aa63b98))
* send notifications on message not streaming
([#219](#219))
([91539d6](91539d6)),
closes [#218](#218)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Holt Skinner <holtskinner@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add_artifact argument (append)

3 participants