The version 3.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 rocksdb.
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.
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 3.0.0 of rocksdb was just published.
rocksdb
The version 3.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 rocksdb.
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.
Commits
The new version differs by 20 commits.
90a6bf1
3.0.0
d20e1e0
prepare changelog for 3.0.0 (#57)
b02753f
rewrite changelog into new format (#56)
438d446
tweak readme + add standard badge
986f931
Merge pull request #55 from Level/fix-nan-deprecation-warnings
a5624bb
specify resource names for all workers
dc6861a
LD_RUN_CALLBACK macro uses Nan::AsyncResource + remove LD_RETURN_CALLBACK_OR_ERROR macro :fire:
2fd1257
use Nan::AsyncResource::runInAsyncScope instead of Nan::MakeCallback
240c7a3
pass in Nan::AsyncWorker::async_resource to Nan::Callback::Call()
77c48cf
standard
55ad4af
chore: remove typings (#54)
ae543be
add default export (#48)
2c02c51
remove node 4 :fire:
d7459ca
node-uuid deprecated -> use uuid
198f137
bump nan :arrow_up:
There are 20 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: