An in-range update of memdown is breaking the build 🚨

[greenkeeper[bot]]

Version 1.2.3 of memdown just got published.

Branch	Build failing 🚨
Dependency	memdown
Current Version	1.2.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

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 :muscle:

---

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/hoodiehq/hoodie-client-task/builds/177323760)

Commits

The new version differs by 3 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)

See the full diff.

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 1.2.2 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper[bot]]

Version 1.2.4 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits .

• 0454e57 1.2.4
• 371f3d2 fix missing npm files (#63)

See the full diff.

[inator]

@gr2m - can this be closed?

[gr2m]

yes.