Skip to content

Commit

Permalink
chore: release 2.1.2 (#232)
Browse files Browse the repository at this point in the history
  • Loading branch information
release-please[bot] authored Dec 2, 2020
1 parent 5e1a217 commit 787c0a7
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 2 deletions.
8 changes: 8 additions & 0 deletions packages/google-cloud-datalabeling/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,14 @@

[1]: https://www.npmjs.com/package/@google-cloud/datalabeling?activeTab=versions

### [2.1.2](https://www.github.com/googleapis/nodejs-datalabeling/compare/v2.1.1...v2.1.2) (2020-11-25)


### Bug Fixes

* **browser:** check for fetch on window ([#236](https://www.github.com/googleapis/nodejs-datalabeling/issues/236)) ([a861cd0](https://www.github.com/googleapis/nodejs-datalabeling/commit/a861cd0671cb04baf0f2b40f376fcb974e4c7159))
* do not modify options object, use defaultScopes ([#231](https://www.github.com/googleapis/nodejs-datalabeling/issues/231)) ([6bcb17b](https://www.github.com/googleapis/nodejs-datalabeling/commit/6bcb17b6cc40cbc2448e8722e8918324ae2261e4))

### [2.1.1](https://www.github.com/googleapis/nodejs-datalabeling/compare/v2.1.0...v2.1.1) (2020-07-10)


Expand Down
2 changes: 1 addition & 1 deletion packages/google-cloud-datalabeling/package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@google-cloud/datalabeling",
"description": "Data Labeling API client for Node.js",
"version": "2.1.1",
"version": "2.1.2",
"license": "Apache-2.0",
"author": "Google LLC",
"engines": {
Expand Down
2 changes: 1 addition & 1 deletion packages/google-cloud-datalabeling/samples/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
"test": "mocha --timeout 600000"
},
"dependencies": {
"@google-cloud/datalabeling": "^2.1.1"
"@google-cloud/datalabeling": "^2.1.2"
},
"devDependencies": {
"chai": "^4.2.0",
Expand Down

0 comments on commit 787c0a7

Please sign in to comment.