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.
Hello lovely humans,
eslint just published its new version 3.1.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
fixable (fixes #6639) (#6644) (Toru Nagashima)no-unused-vars
false positive in loop (fixes #6646) (#6649) (Toru Nagashima)balanced
option tospaced-comment
(fixes #4133) (#6575) (Annie Zhang)endLine
andendColumn
of the lint result. (refs #3307) (#6640) (Toru Nagashima)padded-blocks
(fixes #6628) (#6643) (alberto)key-spacing
option (fixes #5613) (#5907) (Kyle Mendes)The new version differs by 43 commits .
67c3cc2
3.1.0
71f5a8a
Build: package.json and changelog update for 3.1.0
e8f8c6c
Fix: incorrect exitCode when eslint is called with --stdin (fixes #6677) (#6682)
38639bf
Update: make
no-var
fixable (fixes #6639) (#6644)dfc20e9
Fix:
no-unused-vars
false positive in loop (fixes #6646) (#6649)2ba75d5
Update: relax outerIIFEBody definition (fixes #6613) (#6653)
421e4bf
Chore: combine multiple RegEx replaces with one (fixes #6669) (#6661)
089ee2c
Docs: fix typos,wrong path,backticks (#6663)
ef827d2
Docs: Add another pre-commit hook to integrations (#6666)
a343b3c
Docs: Fix option typo in no-underscore-dangle (Fixes #6674) (#6675)
5985eb2
Chore: add internal rule that validates meta property (fixes #6383) (#6608)
4adb15f
Update: Add
balanced
option tospaced-comment
(fixes #4133) (#6575)1b13c25
Docs: fix incorrect example being mark as correct (#6660)
a8b4e40
Fix: Install required eslint plugin for "standard" guide (fixes #6656) (#6657)
720686b
New:
endLine
andendColumn
of the lint result. (refs #3307) (#6640)There are 43 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade