The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint-plugin-eslint-comments.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv2.0.0
Breaking changes
0cd25a3 and 54d5fa0 dropped the support of eslint@<4.7.0. ESLint changed the behavior about directive comments without backward compatibility in eslint/eslint#9216. And the rules of plugins cannot know the version of ESLint which is running the rule. They are recommending plugin developers to drop support for old ESLint if you want to know the version of ESLint. Eslint-plugin-eslint-comments v2.0.0 handles directive comments of eslint@>=4.7.0.
New features
400cea8 added new eslint-comments/no-aggregating-enable rule. The rule about new behavior of eslint@>=4.7.0. This rule reports eslint-enable directive comments if it affects multiple eslint-disable directive comments. That is confusable behavior that does not exist before eslint@4.7.0.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 2.0.0 of eslint-plugin-eslint-comments was just published.
The version 2.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint-plugin-eslint-comments.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0Breaking changes
eslint@<4.7.0
. ESLint changed the behavior about directive comments without backward compatibility in eslint/eslint#9216. And the rules of plugins cannot know the version of ESLint which is running the rule. They are recommending plugin developers to drop support for old ESLint if you want to know the version of ESLint.Eslint-plugin-eslint-comments
v2.0.0 handles directive comments ofeslint@>=4.7.0
.New features
eslint@>=4.7.0
. This rule reportseslint-enable
directive comments if it affects multipleeslint-disable
directive comments. That is confusable behavior that does not exist beforeeslint@4.7.0
.Commits
The new version differs by 9 commits.
82f315d
2.0.0
63b612c
Docs: fix wrong links
98bfc40
Docs: update README.md
3d451c3
New:
eslint-comments/recommended
preset5be249c
New:
no-restricted-disable
rule400cea8
New:
no-aggregating-enable
rule54d5fa0
Breaking: change behavior for
eslint@>=4.7
28327dc
Chore: upgrade devDependencies
0cd25a3
Breaking: drop support
eslint@<4.7
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: