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

[greenkeeper[bot]]

Version 6.25.0 of babel-core just got published.

Branch	Build failing 🚨
Dependency	babel-core
Current Version	6.24.1
Type	devDependency

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

As babel-core 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

- ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/phenomnomnominal/tractor-plugin-visual-regression/1392513556ab6a14774c00444b94495e6d56ba58/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/phenomnomnominal/tractor-plugin-visual-regression/1392513556ab6a14774c00444b94495e6d56ba58/files?status=passing) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/phenomnomnominal/tractor-plugin-visual-regression/builds/240999292?utm_source=github_status&utm_medium=notification) - ✅ **coverage/coveralls** First build on greenkeeper/babel-core-6.25.0 at 34.746% [Details](https://coveralls.io/builds/11895367)

---

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]]

Version 6.26.0 just got published.

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