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.
Coverage remained the same at 100.0% when pulling e4f0189eb11b09da1be4546d3cc5692c210e0891 on greenkeeper-eslint-plugin-node-3.0.2 into c4e8cb1e2f3248a5bdd4def2639a2ab677cc1dc9 on master.
Hello lovely humans,
eslint-plugin-node just published its new version 3.0.2.
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
No change.
I had published 2.1.4 to the
latest
tag.This release recovers the releasing mistake.
The new version differs by 14 commits .
77d0c76
3.0.2
6bbee16
3.0.1
610b905
Fix:
no-deprecated-api
crash on undeclared assignment (fixes #55) (#56)382886e
Chore: upgrade eslint-config-mysticatea
34928aa
3.0.0
13c61b1
Breaking: update
plugin:node/recommended
95b8164
Fix: version number for tests.
8e0c033
Squashed commit of the following:
9aa7e8d
Breaking: add ES2016/2017 features to
no-unsupported-features
(fixes #46)a6f90e1
Chore: punycode → domain in tests
292e8f8
Fix: false positive of
no-unsupported-features
about code point escapes.9e77b54
Chore: upgrade eslint & eslint-config-mysticatea
ce465b8
Breaking: add new deprecated APIs to
no-deprecated-api
rule. (fixes #54)02a3ace
Chore: add Node 7 to .travis.yml
See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade