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 level-js.
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 level-js was just published.
[level-js](https://github.com/Level/level-js)
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 level-js.
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
v3.0.0Changed
location
andprefix
only (#116) (@ralphtheninja)util.inherits
withinherits
module (8db16c1
) (@ralphtheninja)7017edd
) (@ralphtheninja)package.json
description and keywords (#141) (@vweevers)Added
CHANGELOG.md
(#107, #115) (@ralphtheninja, @vweevers)UPGRADING.md
(#143) (@vweevers)CONTRIBUTORS.md
(replacesCOLLABORATORS.md
) (#141) (@vweevers)standard
(#112) (@ralphtheninja)remark
tooling (#141, #143, #147) (@vweevers)Buffer
,ArrayBuffer
andUint8Array
values withasBuffer
option (#146) (@vweevers)Fixed
level.js
in documentation to match npm namelevel-js
(#121) (@ralphtheninja)buffer@5
(#122) (@vweevers)NaN
) (#130) (@vweevers)ArrayBuffer
cursor key toBuffer
(#130) (@vweevers)setImmediate
with callback in_close()
(#111) (@ralphtheninja)instanceof Date
for cross-realm support (#129) (@vweevers)3.0.0-rc1
(43a702b
) (@ralphtheninja)Removed
test/levelup-test.js
(#134) (@ralphtheninja)levelup
from destroy tests (#136) (@ralphtheninja)Commits
The new version differs by 30 commits.
296cfe0
3.0.0
ef64509
Prepare 3.0.0 (#147)
97c464f
Add UPGRADING.md (#143)
9d93fda
Binary tests (#146)
9d5ec5c
Docs (#141)
7017edd
Tweak copyright years for less maintenance
43a702b
Fix wrong release date for 3.0.0-rc1
89c8034
Test illegal and stringified key types (#139)
8db16c1
Replace util.inherits with inherits module
9f0e2e5
Remove levelup from destroy tests (#136)
249f3e8
Remove test/levelup-test.js :fire: (#134)
2666a50
Merge pull request #130 from Level/key-types
4eaa630
test that iterator yields Buffer keys
b3a2240
test all valid key types
184ad0a
fix conversion of binary cursor key (which is an ArrayBuffer) to Buffer
There are 30 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: