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
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Download/redux-apis/builds/211707308)
Release Notesv6.4.1
🐛 Bug Fix
Fixed reset of BABEL_ENV when options.forceEnv is used (#420) @nikopavlica
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).
Version 6.4.1 of babel-loader just got published.
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
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Download/redux-apis/builds/211707308)Release Notes
v6.4.1Commits
The new version differs by 2 commits .
48325ea6.4.1f3241f8Fixed reset of BABEL_ENV when options.forceEnv is used (#420)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: