Skip to content

Commit

Permalink
chore: release 2.6.1 (#261)
Browse files Browse the repository at this point in the history
🤖 I have created a release \*beep\* \*boop\*
---
### [2.6.1](https://www.github.com/googleapis/python-vision/compare/v2.6.0...v2.6.1) (2021-10-26)


### Documentation

* update async_detect_document() sample ([#260](https://www.github.com/googleapis/python-vision/issues/260)) ([b044537](https://www.github.com/googleapis/python-vision/commit/b044537fb49794ba988ffd8324b50d5cdbac6678))
---


This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
  • Loading branch information
release-please[bot] authored Oct 26, 2021
1 parent 06958db commit 0880373
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 1 deletion.
7 changes: 7 additions & 0 deletions packages/google-cloud-vision/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,13 @@

[1]: https://pypi.org/project/google-cloud-vision/#history

### [2.6.1](https://www.github.com/googleapis/python-vision/compare/v2.6.0...v2.6.1) (2021-10-26)


### Documentation

* update async_detect_document() sample ([#260](https://www.github.com/googleapis/python-vision/issues/260)) ([b044537](https://www.github.com/googleapis/python-vision/commit/b044537fb49794ba988ffd8324b50d5cdbac6678))

## [2.6.0](https://www.github.com/googleapis/python-vision/compare/v2.5.0...v2.6.0) (2021-10-20)


Expand Down
2 changes: 1 addition & 1 deletion packages/google-cloud-vision/setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@

name = "google-cloud-vision"
description = "Cloud Vision API API client library"
version = "2.6.0"
version = "2.6.1"
release_status = "Development Status :: 5 - Production/Stable"
dependencies = [
# NOTE: Maintainers, please do not require google-api-core>=2.x.x
Expand Down

0 comments on commit 0880373

Please sign in to comment.