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/zaccolley/songkick.pink/builds/211701592)
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/zaccolley/songkick.pink/builds/211701592)Release Notes
v6.4.1Commits
The new version differs by 2 commits .
48325ea
6.4.1
f3241f8
Fixed 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: