This repository was archived by the owner on Aug 22, 2025. It is now read-only.
leveldown@1.6.0 breaks build 🚨 - #30
Open
greenkeeperio-bot wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello lovely humans,
leveldown just published its new version 1.6.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As leveldown is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
GitHub Release
7c6209017b] - 📜 : adjust README to reflect prebuild changes (Lars-Magnus Skog)41c5dbe0d8] - ⬆️ : bump nan (Lars-Magnus Skog)4fba21f0ea] - ✨ 2016 -> 2017 (Lars-Magnus Skog)af08992825] - add compactRange doc link to index in README, improve test assertion in compactRange (Gordon Hall)19276edf82] - upgrade prebuild{,-{ci,install}} (Julian Gruber)460cea7136] - add to contribs + update readme (Gordon Hall)017bcae5e7] - add simple test to make sure that a range compaction does infact reduce the size of the database (Gordon Hall)14ba38b465] - get compactRange working (Gordon Hall)e31f433227] - start working on exposing compactRange from leveldb (Gordon Hall)The new version differs by 85 commits .
113e0ceBumped to 1.6.0f92a1bcMerge pull request #342 from ralphtheninja/master7c62090:scroll: adjust README to reflect prebuild changes41c5dbe:arrow_up: bump nan4fba21f:sparkles: 2016 -> 201763ca144Merge pull request #340 from bookchin/feature/compact-rangeaf08992add compactRange doc link to index in README, improve test assertion in compactRange76c0181Merge pull request #341 from Level/upgrade-prebuild19276edupgrade prebuild{,-{ci,install}}460cea7add to contribs + update readme017bcaeadd simple test to make sure that a range compaction does infact reduce the size of the database14ba38bget compactRange workinge31f433start working on exposing compactRange from leveldb710d190Bumped to 1.5.3539e43bMerge pull request #334 from Level/vweevers-patch-1There are 85 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.