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

Version 7.1.1 of babel-loader just got published.

Branch	Build failing 🚨
Dependency	babel-loader
Current Version	7.1.0
Type	devDependency

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

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

- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/GrimoireGL/GrimoireJS/935?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

Release Notes

7.1.1

🐛 Bug Fix

Do not read .babelrc for cache identifier when babelrc=false (#483) (Russ Tyndall)

📝 Documentation

Update README.md for webpack 3.x (#476) (Pierre Neter)

🏠 Internal

Update eslint to the latest version 🚀 (#482) (greenkeeper[bot])
chore(package): update husky to version 0.14.0 (#475) (greenkeeper[bot])

Commits

The new version differs by 6 commits.

5953fcf 7.1.1
f3cacd9 Update yarn.lock
0815f48 Update eslint to the latest version 🚀 (#482)
aefe583 Do not read .babelrc for cache identifier when babelrc=false (#483)
c8924f3 chore(package): update husky to version 0.14.0 (#475)
6063373 Update README.md for webpack 3.x (#476)

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:

GrimoireGL / GrimoireJS