greenkeeper[bot]
commented
6 years ago Version 4.15.0 just got published.
Update to this version instead 🚀
Release Notes
v4.15.0- 6ab04b5 New: Add context.report({ messageId }) (fixes #6740) (#9165) (Jed Fox)
- fc7f404 Docs: add url to each of the rules (refs #6582) (#9788) (Patrick McElhaney)
- fc44da9 Docs: fix sort-imports rule block language (#9805) (ferhat elmas)
- 65f0176 New: CLIEngine#getRules() (refs #6582) (#9782) (Patrick McElhaney)
- c64195f Update: More detailed assert message for rule-tester (#9769) (Weijia Wang)
- 9fcfabf Fix: no-extra-parens false positive (fixes: #9755) (#9795) (Erin)
- 61e5fa0 Docs: Add table of contents to Node.js API docs (#9785) (Patrick McElhaney)
- 4c87f42 Fix: incorrect error messages of no-unused-vars (fixes #9774) (#9791) (akouryy)
- bbabf34 Update: add
ignoreCommentsoption toindentrule (fixes #9018) (#9752) (Kevin Partington) - db431cb Docs: HTTP -> HTTPS (fixes #9768) (#9768) (Ronald Eddy Jr)
- cbf0fb9 Docs: describe how to feature-detect scopeManager/visitorKeys support (#9764) (Teddy Katz)
- f7dcb70 Docs: Add note about "patch release pending" label to maintainer guide (#9763) (Teddy Katz)
Commits
The new version differs by 14 commits.
e14ceb04.15.02dfc3bdBuild: changelog update for 4.15.06ab04b5New: Add context.report({ messageId }) (fixes #6740) (#9165)fc7f404Docs: add url to each of the rules (refs #6582) (#9788)fc44da9Docs: fix sort-imports rule block language (#9805)65f0176New: CLIEngine#getRules() (refs #6582) (#9782)c64195fUpdate: More detailed assert message for rule-tester (#9769)9fcfabfFix: no-extra-parens false positive (fixes: #9755) (#9795)61e5fa0Docs: Add table of contents to Node.js API docs (#9785)4c87f42Fix: incorrect error messages of no-unused-vars (fixes #9774) (#9791)bbabf34Update: addignoreCommentsoption toindentrule (fixes #9018) (#9752)db431cbDocs: HTTP -> HTTPS (fixes #9768) (#9768)cbf0fb9Docs: describe how to feature-detect scopeManager/visitorKeys support (#9764)f7dcb70Docs: Add note about "patch release pending" label to maintainer guide (#9763)
See the full diff
Version 4.14.0 of eslint was just published.
The version 4.14.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.
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
v4.14.0complexityrule (fixes #8535) (#9754) (Kevin Partington)valid-typeofexample (#9753) (Teddy Katz)sourceproperty a little more subtle (#9735) (Jed Fox)lines-between-class-members(fixes #9665) (#9680) (sakabar)Commits
The new version differs by 19 commits.
8d166b44.14.05a29612Build: changelog update for 4.14.0be2f57eUpdate: support separate requires in one-var. (fixes #6175) (#9441)370d614Docs: Fix typos (#9751)8196c45Chore: Reorganize CLI options and associated docs (#9758)75c7419Update: Logical-and is counted incomplexityrule (fixes #8535) (#9754)eb4b1e0Docs: reintroduce misspelling invalid-typeofexample (#9753)ae51eb2New: Add allowImplicit option to array-callback-return (fixes #8539) (#9344)e9d5dfdDocs: improve no-extra-parens formatting (#9747)37d066cChore: Add unit tests for overrides glob matching. (#9744)805a94eChore: Fix typo in CLIEngine test name (#9741)1c2aafdUpdate: Improve parser integrations (fixes #8392) (#8755)4ddc131Upgrade: debug@^3.1.0 (#9731)f252c19Docs: Make the lint messagesourceproperty a little more subtle (#9735)5a5c23cDocs: fix the link to contributing page (#9727)There are 19 commits in total.
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: