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-plugin-node.
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-plugin-node just published its new version 2.0.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-plugin-node. 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
Breaking Changes:
eslint-plugin-node
dropped supports of ESLint 1. Now it requires ESLint>=2.0.0
.Notes:
eslint-plugin-node
has the plan to drop supports of ESLint 2 and Node.js 0.10/0.12. It will come at the end of 2016.The new version differs by 35 commits (ahead by 35, behind by 2).
9efa7f3
2.0.0
37e53ba
Fix: stop using ESLint under Node 0.x in Travis CI
fd9369b
Docs: add notes of requirements.
9fabf76
Breaking: drop supports for ESLint v1
0351193
Chore: upgdate my eslint config.
a7f3846
1.5.2
fc86406
Fix: invalid peerDependencies for ESLint 3.0.0
413c23d
1.5.1
ebe2151
Upgrade: minimatch 3.0.2
42fd1c8
1.5.0
c29759d
Docs: update README.md
155e3ce
Fix: Tweaks recommended config.
22e972d
New: add
plugin:node/recommended
config (#39)4499881
Docs: add semantic versioning policy (fixes #41)
4d9d009
Fix:
no-unsupported-features
had a false negative (fixes #40)There are 35 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade