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-config-standard 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.
Coverage remained the same at 100.0% when pulling cc0ac3008b0a189391d294d308ac6b73e7b016c8 on greenkeeper-eslint-config-standard-6.2.1 into 2de6d2649a4ba4e712193de8412fca43b94d309e on master.
Coverage remained the same at 100.0% when pulling cc0ac3008b0a189391d294d308ac6b73e7b016c8 on greenkeeper-eslint-config-standard-6.2.1 into 2de6d2649a4ba4e712193de8412fca43b94d309e on master.
Hello lovely humans,
eslint-config-standard just published its new version 6.2.1.
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-config-standard 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 16 commits .
c879dfb
6.2.1
7b7eeeb
update dep versions for new rule
b42b795
wrap-iife: [2, "any", { "functionPrototypeMethods": true }]
fdfedd5
Add --save-dev
5eed6cd
6.2.0
bca87dc
Merge pull request #50 from feross/ecmaversion-8
9f14f10
ecmaVersion 8
cefa263
Merge pull request #49 from danyshaanan/patch-1
dab099a
Replace t.ok with t.equal
9567c3a
6.1.0
706d8f1
ecmaVersion 7
dbd4ecb
6.0.1
40124b6
Merge pull request #48 from feross/eslint3
8d9bbe1
peer depend on eslint 3
e3f1cf6
Merge pull request #44 from robinpokorny/remove-unneeded-conf
There are 16 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade