Update dependency @google-cloud/vision to v0.23.0 #894
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.12.0->0.23.00.16.0->0.23.0Release Notes
googleapis/nodejs-vision
v0.23.0Compare Source
New Features
Dependencies
Documentation
Internal / Testing Changes
v0.22.1Compare Source
Bug fixes
Documentation
Internal / Testing Changes
v0.22.0Compare Source
New Features
Object Localization is available on v1 of this library:
Dependencies
Internal / Testing Changes
v0.21.0Compare Source
Implementation Changes
🚨 BREAKING CHANGE
In this version we dropped support for NodeJS 4.x and 9.x. Your code might break if you're using this library on non LTS versions.
New Features
This release brings in v1p3beta1 of the Cloud Vision API, which includes the following new features:
Object localization
Product search
gen: v1p3beta1 of Cloud Vision API NodeJS Client Library (#124)
feat: implement manual methods for objectLocalization and productSearch on v1p3beta1 (#128)
Dependencies
Documentation
Internal / Testing Changes
v0.20.0Compare Source
Changes
v0.19.0Compare Source
Features
This is a minor release that updates
v1p2beta1code and adds a new sample of scanning the PDF file. The default endpoint is stillv1, and there are no incompatible changes.v0.18.0Compare Source
Features
This release contains GAPIC update to
v1p2beta1endpoint that contains just a proto change and no changes to the generated code. The added message typemessage AnnotateFileResponsewill be used in samples later. There are no incompatible changes, existing code (usingv1,v1p1beta1, orv1p2beta1endpoints) will work as earlier.v1endpoint is still used by default.v0.17.0Compare Source
Fixes
Updated dependencies, including google-gax, to fix streaming behavior. (googleapis/gax-nodejs#197)
v0.16.0Compare Source
Features
This release enables the new endpoint
v1p2beta1that you can work with using the following code:The default endpoint
v1has not changed so no existing code is affected by this change.v0.15.2Compare Source
Fixes
This patch release updates some dependencies to fix the security issues introduced by
log-driverpackage. No other changes since the previous release.v0.15.1Compare Source
Fixes
v0.15.0Compare Source
Features
In this release, still beta, we have added some small compatible improvements to the
v1API and refreshed auto generated code. This version will likely be released to general availability after some time.v0.14.0Compare Source
This should be considered a subsequent and hopefully final release candidate. It has no breaking changes; we just simply want to give the API introduced in 0.13.0 slightly more bake time before declaring GA.
Features
Beta Endpoint
This release adds the
v1p1beta1endpoint. This is a new backend endpoint which adds features which the backend API considers to be in public beta. These features are being prepared for general release and should be mostly stable; however, changes may occur if necessary.By default, this client library will use the
v1(general availability) endpoint, rather than silently opt you into using beta features. If you wish to usev1p1beta1, you can opt into it explicitly when requiring the library:The
v1p1beta1endpoint is a superset ofv1; it also contains allv1features. The goal is that you can change nothing but yourrequirestatement, and when these features go GA, you only have to remove the version designation.v0.13.0Compare Source
This is the (hopefully) final release candidate before declaring a stable release.
Request Format
We learned from a few mistakes we made in the previous release, and have updated the API to be simpler and more consistent. We now require the entire
AnnotateImageRequestto be sent toannotateImage, rather than just theimagecomponent. This allows for cases where you need to specify something else (e.g.imageContext) without having to fall back on the batch method.To make up for this, we also reinstated the ability to send a simple string or buffer in lieu of the entire request in the single-feature methods (#5), which should make this a net reduction of code.
Simple Cases
Here is a migration guide for simple cases:
Before
After
Complex Cases
In complex cases (for example, where you needed another key in the request), you will need to send the entire request object, except for the parts that get added in by the method (e.g. the
featureskey).Carrying forward the previous example:
Before
After
Refer to the nodejs-vision API reference documentation for details.
Features
Runnable samples
There are now runnable samples in the
samples/directory. These samples demonstrate the use of this API and offer an additional resource for getting started. These also power the readme, and are automatically tested to ensure that they are up-to-date and correct.Implementation Details
googleapis/nodejs-visionrepository.Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "
rebase!".🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot. View repository job log here.