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

[greenkeeper[bot]]

Version 6.4.1 of nano just got published.

Branch	Build failing 🚨
Dependency	nano
Current Version	6.4.0
Type	dependency

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

nano is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very 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/npms-io/npms-analyzer/builds/277689563?utm_source=github_status&utm_medium=notification)

---

Release Notes

6.4.1

Switch to cloudant-follow dependency.

Commits

The new version differs by 4 commits ahead by 4, behind by 1.

• 56a5470 6.4.1
• c0c4558 6.4.0 mismatch
• f503170 Merge pull request #51 from apache/feat/cloudant-follow
• 0de43ee feat: switch from follow to cloudant-follow, which is maintaned

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 6.4.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

Version 6.4.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 2 commits.

• c308792 6.4.2
• 2e4f1b7 Use cloudant-follow (#60)

See the full diff