An in-range update of babel-runtime is breaking the build 🚨

[greenkeeper[bot]]

Version 6.20.0 of babel-runtime just got published.

Branch	Build failing 🚨
Dependency	babel-runtime
Current Version	6.18.0
Type	dependency

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

As babel-runtime 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 is in progress [Details](https://travis-ci.org/declandewet/common-tags/builds/182442430) - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/declandewet/common-tags/build/247) - ❌ **bitHound - Dependencies** 11 failing dependencies. [Details](https://www.bithound.io/github/declandewet/common-tags/63026836212e4903b2ee9ff86e69377a7eafcf8f/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/declandewet/common-tags/63026836212e4903b2ee9ff86e69377a7eafcf8f/files?status=passing)

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.18.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.25.0 just got published.

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

[greenkeeper[bot]]

Version 6.26.0 just got published.

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