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 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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
eslint just published its new version 3.14.0.
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 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:
GitHub Release
no-var
does not fix if causes ReferenceError (fixes #7950) (#7953) (Toru Nagashima)prefer-promise-reject-errors
rule (fixes #7685) (#7689) (Teddy Katz)__proto__
(#7934) (Teddy Katz)The new version differs by 210 commits .
67ac93c
3.14.0
2cf5810
Build: package.json and changelog update for 3.14.0
506324a
Fix:
no-var
does not fix if causes ReferenceError (fixes #7950) (#7953)05e7432
New: no-chained-assignments rule (fixes #6424) (#7904)
243e47d
Update: Add fixer for no-else-return (fixes #7863) (#7864)
f091d95
New:
prefer-promise-reject-errors
rule (fixes #7685) (#7689)ca01e00
Fix: recognize all line terminators in func-call-spacing (fixes #7923) (#7924)
a664e8a
Update: add ignoreJSX option to no-extra-parens (Fixes #7444) (#7926)
8ac3518
Fix: no-useless-computed-key false positive with
__proto__
(#7934)c835e19
Docs: remove reference to deleted rule (#7942)
3c1e63b
Docs: Improve examples for no-case-declarations (fixes #6716) (#7920)
7e04b33
Fix: Ignore inline plugin rule config in autoconfig (fixes #7860) (#7919)
6448ba0
Fix: add parentheses in no-extra-boolean-cast autofixer (fixes #7912) (#7914)
b3f2094
Fix: brace-style crash with lone block statements (fixes #7908) (#7909)
5eb2e88
Docs: Correct typos in configuring.md (#7916)
There are 210 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.