The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @google-cloud/logging.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv2.0.0
This release is semver major release because it drops support for Node 4.x and 9.x. Apart from that there should be no other breaking changes.
Notable changes
Node.js 4.x and 9.x are no longer supported (#123)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.0.0 of @google-cloud/logging was just published.
The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of @google-cloud/logging.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0This release is semver major release because it drops support for Node 4.x and 9.x. Apart from that there should be no other breaking changes.
Notable changes
Commits
Commits
The new version differs by 36 commits.
7c0ccc2
chore(release): bump version to 2.0.0 (#149)
f7518e1
Re-generate library using /synth.py (#148)
dde2613
Re-generate library using /synth.py (#147)
ae3808c
fix(deps): update dependency yargs to v12 (#146)
268dab5
Re-generate library using /synth.py (#145)
bca99ad
chore(deps): update dependency uuid to v3.3.0 (#142)
19f0d4f
chore(deps): update dependency sinon to v6.0.1 (#141)
f2a5811
Configure Renovate (#129)
b60f986
Re-generate library using /synth.py (#140)
a80056a
refactor: drop repo-tool as an exec wrapper (#139)
faa3b6e
chore: update sample lockfiles (#138)
ea534d2
chore(package): update eslint to version 5.0.0 (#134)
b9e3de4
Re-generate library using /synth.py (#137)
4bd42b3
fix: update linking for samples (#136)
d135381
Re-generate library using /synth.py (#135)
There are 36 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: