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.19.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
eslint.verify
should not mutate config argument (fixes #8329) (#8334) (alberto)The new version differs by 704 commits .
421aab4
3.19.0
26a4dd5
Build: changelog update for 3.19.0
e09132f
Fix: no-extra-parens false positive with exports and object literals (#8359)
91baed4
Update: allow custom messages in no-restricted-syntax (fixes #8298) (#8357)
35c93e6
Fix: prevent space-before-function-paren from checking type annotations (#8349)
3342e9f
Fix: don't modify operator precedence in operator-assignment autofixer (#8358)
f88375f
Docs: clarify that no-unsafe-negation is in eslint:recommended (#8371)
02f0d27
Docs: Add soda0289 to Development Team (#8367)
155424c
Fix: ignore empty path in patterns (fixes #8362) (#8364)
27616a8
Fix: prefer-const false positive with object spread (fixes #8187) (#8297)
8569a90
Docs: add note about git's linebreak handling to linebreak-style docs (#8361)
5878593
Chore: fix invalid syntax in no-param-reassign test (#8360)
1b1046b
Fix: don't classify plugins that throw errors as "missing" (fixes #6874) (#8323)
29f4ba5
Fix: no-useless-computed-key invalid autofix for getters and setters (#8335)
0541eaf
Fix: no-implicit-coercion invalid autofix with consecutive identifiers (#8340)
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.