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

[greenkeeper]

Version 7.2.3 of babel-eslint just got published.

Branch	Build failing 🚨
Dependency	babel-eslint
Current Version	7.2.2
Type	devDependency

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

As babel-eslint 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 💪

Status Details

- ✅ **Better Code Hub** ✅ Better Code Hub approves this code [Details](https://bettercodehub.com/results/storybooks/storybook/8f713dd5490d0fbb87cf885f3dd94b413c760b97),- ❌ **bitHound - Code** 310 failing files. [Details](https://www.bithound.io/github/storybooks/storybook/8f713dd5490d0fbb87cf885f3dd94b413c760b97/files#filter-failing-file),- ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/storybooks/storybook/8f713dd5490d0fbb87cf885f3dd94b413c760b97/dependencies/npm?status=passing),- ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/storybooks/storybook/builds/224520360)

---

Commits

The new version differs by 2 commits0.

• 94bb5a1 7.2.3
• dfaff04 Fix flow type spread handling (#465)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴