This version is covered by your current version range and after updating it in your project the build went from success to failure.
As eslint-plugin-import 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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 105 commits .
f314e5ccleaned up build (fix #417) + made coverage work again (fix #403) trying to validate 1.10.3
2bb0163typo fix (in what is clearly untested code)
d3422aaMerge branch 'master' into release, bump to v1.10.3
ea84f34Merge pull request #419 from benmosher/issue-415-no-symbols
f9cf7a0removed es6-symbol completely, unneeded without for-of
35891cfTransformed all remaining occurences of for..of to forEach()
Hello lovely humans,
eslint-plugin-import just published its new version 1.10.3.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As eslint-plugin-import 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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 105 commits .
f314e5ccleaned up build (fix #417) + made coverage work again (fix #403) trying to validate 1.10.32bb0163typo fix (in what is clearly untested code)d3422aaMerge branch 'master' into release, bump to v1.10.3ea84f34Merge pull request #419 from benmosher/issue-415-no-symbolsf9cf7a0removedes6-symbolcompletely, unneeded without for-of35891cfTransformed all remaining occurences of for..of to forEach()dc3e852remove for-of syntax from rules/export5dd3d70changelog note for last commit4d17a93pin down es6-symbol63feebekeeping ESLint 2.x as a dev depenendency of 1.x (for 0.10 Travis builds)49b3531Merge branch 'release'21be81cchangelog note for the nightmare that is v1.10.11bb07bc1.10.2566c0a2Merge branch 'release'e8fde58Merge pull request #405 from benmosher/greenkeeper-eslint-3.0.0There are 105 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade