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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/woshilapin/codingame-connector/builds/214366778)
Commits
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 7.2.1 of babel-eslint just got published.
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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/woshilapin/codingame-connector/builds/214366778)Commits
The new version differs by 6 commits .
3cda62e
7.2.1
5626de1
Remove left over eslint 2 estraverse code (#452)
b5fb53b
Fix type param and interface declaration scoping (#449)
f1cee0f
Remove lodash dependency (#450)
eb05812
Format non-regression errors for legibility (#451)
7972a05
Update README.md with codeFrame option (#448)
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: