memdown@1.2.3 breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

memdown just published its new version 1.2.3.

State	Failing tests 🚨
Dependency	memdown
New version	1.2.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As memdown 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!

🌴

---

The new version differs by 31 commits .

• 4f242a3 1.2.3
• 304a401 Use immediate in browsers, setImmediate in Node (#61)
• 0fb34b3 chore(package): update ltgt to version 2.1.3 (#60)
• ef16868 1.2.2
• 2f95432 Minor cleanup (#54)
• 8671844 1.2.1
• a794387 get code coverage up to 100% (#53)
• 8cf8870 update .zuul.yml browsers
• 9551393 pin abstract-leveldown to 2.4.1
• 261af87 use --no-coverage with zuul
• 68c1bf4 Merge pull request #49 from Level/tests-for-empty-batch-values
• 2b8dde6 add tests for empty batch values
• eb030ea 1.2.0
• e6a9821 Merge pull request #48 from Level/allow-empty-value-in-batch
• 565f125 allow empty value in batch

There are 31 commits in total. See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}

[JohannesBertens]

Yes, this breaks 'testrpc' for me!

[kumavis]

This was resolved in 1.2.4