Skip to content

Commit

Permalink
chore: release 2.1.2 (#312)
Browse files Browse the repository at this point in the history
  • Loading branch information
release-please[bot] authored Dec 2, 2020
1 parent 4c2a20b commit 5cdecc0
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-scheduler/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/scheduler?activeTab=versions

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


### Bug Fixes

* **browser:** check for fetch on window ([#313](https://www.github.com/googleapis/nodejs-scheduler/issues/313)) ([5a7840a](https://www.github.com/googleapis/nodejs-scheduler/commit/5a7840acbe5cbd96be701c8d06a3ec350bf45cc1))
* do not modify options object, use defaultScopes ([#305](https://www.github.com/googleapis/nodejs-scheduler/issues/305)) ([7f8b30c](https://www.github.com/googleapis/nodejs-scheduler/commit/7f8b30c165d3de8beebb0e6704535b4eed7d817d))

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


Expand Down
2 changes: 1 addition & 1 deletion packages/google-cloud-scheduler/package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "@google-cloud/scheduler",
"description": "Cloud Scheduler 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-scheduler/samples/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
"test": "mocha --timeout 10000 --exit"
},
"dependencies": {
"@google-cloud/scheduler": "^2.1.1",
"@google-cloud/scheduler": "^2.1.2",
"body-parser": "^1.18.3",
"express": "^4.16.4"
},
Expand Down

0 comments on commit 5cdecc0

Please sign in to comment.