This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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 2.12.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
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
always
foreqeqeq
(refs #6144) (#6342) (alberto)max-lines
rule (fixes #6078) (#6321) (alberto)arrow-body-style
(fixes #5936) (#6216) (alberto)no-mixed-operators
rule (fixes #6023) (#6241) (Toru Nagashima)eslint:all
option (fixes #6240) (#6248) (Robert Fletcher)object-curly-newline
(fixes #6072) (#6223) (Toru Nagashima)no-useless-rename
false positive in babel-eslint (fixes #6266) (#6290) (alberto)--no-ignore
disables all forms of ignore (fixes #6260) (#6304) (alberto)The new version differs by 1424 commits .
d8d6d29
2.12.0
2813c7c
Build: package.json and changelog update for 2.12.0
54c30fb
Update: Add explicit default option
always
foreqeqeq
(refs #6144) (#6342)2d63370
Update: max-len will warn indented comment lines (fixes #6322) (#6324)
dcd4ad7
Docs: clarify usage of inline disable comments (fixes #6335) (#6347)
c03300b
Docs: Clarified how plugin rules look in plugin configs (fixes #6346) (#6351)
9c87709
Docs: Add semantic versioning policy (fixes #6244) (#6343)
5affab1
Docs: Describe values under Extending Configuration Files (refs #6240) (#6336)
2520f5a
New:
max-lines
rule (fixes #6078) (#6321)9bfbc64
Update: Option for object literals in
arrow-body-style
(fixes #5936) (#6216)977cdd5
Chore: remove unused method from FileFinder (fixes #6344) (#6345)
477fbc1
Docs: Add section about customizing RuleTester (fixes #6227) (#6331)
0e14016
New:
no-mixed-operators
rule (fixes #6023) (#6241)6e03c4b
Update: Add never option to arrow-body-style (fixes #6317) (#6318)
f804397
New: Add
eslint:all
option (fixes #6240) (#6248)There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade