Closed greenkeeper[bot] closed 6 years ago
Update to this version instead 🚀
The new version differs by 6 commits.
29c3610
4.13.0
ac331bc
Build: changelog update for 4.13.0
256481b
Update: update handling of destructuring in camelcase (fixes #8511) (#9468)
d067ae1
Docs: Don’t use undocumented array-style configuration for max-len (#9690)
1ad3091
Chore: fix test-suite to work with node master (#9688)
cdb1488
Docs: Adds an example with try/catch. (#9672)
See the full diff
Update to this version instead 🚀
The new version differs by 6 commits.
234cd26
4.13.1
3b0833f
Build: changelog update for 4.13.1
b72dc83
Fix: eol-last allow empty-string to always pass (refs #9534) (#9696)
d80aa7c
Fix: camelcase destructure leading/trailing underscore (fixes #9700) (#9701)
d49d9d0
Docs: Add missing period to the README (#9702)
4564fe0
Chore: no-invalid-meta crash if no export assignment (refs #9534) (#9698)
See the full diff
Update to this version instead 🚀
complexity
rule (fixes #8535) (#9754) (Kevin Partington)valid-typeof
example (#9753) (Teddy Katz)source
property a little more subtle (#9735) (Jed Fox)lines-between-class-members
(fixes #9665) (#9680) (sakabar)The new version differs by 19 commits.
8d166b4
4.14.0
5a29612
Build: changelog update for 4.14.0
be2f57e
Update: support separate requires in one-var. (fixes #6175) (#9441)
370d614
Docs: Fix typos (#9751)
8196c45
Chore: Reorganize CLI options and associated docs (#9758)
75c7419
Update: Logical-and is counted in complexity
rule (fixes #8535) (#9754)
eb4b1e0
Docs: reintroduce misspelling in valid-typeof
example (#9753)
ae51eb2
New: Add allowImplicit option to array-callback-return (fixes #8539) (#9344)
e9d5dfd
Docs: improve no-extra-parens formatting (#9747)
37d066c
Chore: Add unit tests for overrides glob matching. (#9744)
805a94e
Chore: Fix typo in CLIEngine test name (#9741)
1c2aafd
Update: Improve parser integrations (fixes #8392) (#8755)
4ddc131
Upgrade: debug@^3.1.0 (#9731)
f252c19
Docs: Make the lint message source
property a little more subtle (#9735)
5a5c23c
Docs: fix the link to contributing page (#9727)
There are 19 commits in total.
See the full diff
Update to this version instead 🚀
ignoreComments
option to indent
rule (fixes #9018) (#9752) (Kevin Partington)The new version differs by 14 commits.
e14ceb0
4.15.0
2dfc3bd
Build: changelog update for 4.15.0
6ab04b5
New: Add context.report({ messageId }) (fixes #6740) (#9165)
fc7f404
Docs: add url to each of the rules (refs #6582) (#9788)
fc44da9
Docs: fix sort-imports rule block language (#9805)
65f0176
New: CLIEngine#getRules() (refs #6582) (#9782)
c64195f
Update: More detailed assert message for rule-tester (#9769)
9fcfabf
Fix: no-extra-parens false positive (fixes: #9755) (#9795)
61e5fa0
Docs: Add table of contents to Node.js API docs (#9785)
4c87f42
Fix: incorrect error messages of no-unused-vars (fixes #9774) (#9791)
bbabf34
Update: add ignoreComments
option to indent
rule (fixes #9018) (#9752)
db431cb
Docs: HTTP -> HTTPS (fixes #9768) (#9768)
cbf0fb9
Docs: describe how to feature-detect scopeManager/visitorKeys support (#9764)
f7dcb70
Docs: Add note about "patch release pending" label to maintainer guide (#9763)
See the full diff
Update to this version instead 🚀
.eslintrc.*
(fixes #9535) (#9847) (Kevin Partington)The new version differs by 22 commits.
33ca1ea
4.16.0
1a9ddee
Build: changelog update for 4.16.0
e26a25f
Update: allow continue instead of if wrap in guard-for-in (fixes #7567) (#9796)
af043eb
Update: Add NewExpression support to comma-style (#9591)
4f898c7
Build: Fix JSDoc syntax errors (#9813)
13bcf3c
Fix: Removing curly quotes in no-eq-null report message (#9852)
b96fb31
Docs: configuration hierarchy for CLIEngine options (fixes #9526) (#9855)
8ccbdda
Docs: Clarify that -c configs merge with .eslintrc.*
(fixes #9535) (#9847)
978574f
Docs: Fix examples for no-useless-escape (#9853)
cd5681d
Chore: Deactivate consistent-docs-url in internal rules folder (#9815)
2e87ddd
Docs: Sync messageId examples' style with other examples (#9816)
1d61930
Update: use doctrine range information in valid-jsdoc (#9831)
133336e
Update: fix indent behavior on template literal arguments (fixes #9061) (#9820)
ea1b15d
Fix: avoid crashing on malformed configuration comments (fixes #9373) (#9819)
add1e70
Update: fix indent bug on comments in ternary expressions (fixes #9729) (#9818)
There are 22 commits in total.
See the full diff
Update to this version instead 🚀
The new version differs by 11 commits.
2af9446
4.17.0
5ad3fb2
Build: changelog update for 4.17.0
1da1ada
Update: Add "multiline" type to padding-line-between-statements (#8668)
bb213dc
Chore: Use messageIds in some of the core rules (#9648)
1aa1970
Docs: remove outdated rule naming convention (#9925)
3afaff6
Docs: Add prefer-destructuring variable reassignment example (#9873)
d20f6b4
Fix: Typo in error message when running npm (#9866)
51ec6a7
Docs: Use GitHub Multiple PR/Issue templates (#9911)
dc80487
Update: space-unary-ops uses astUtils.canTokensBeAdjacent (fixes #9907) (#9906)
084351b
Docs: Fix the messageId example (fixes #9889) (#9892)
9cbb487
Docs: Mention the globals
key in the no-undef docs (#9867)
See the full diff
Version 4.12.1 of eslint was just published.
The version 4.12.1 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.12.1Commits
The new version differs by 3 commits.
58216b6
4.12.1
fc9d27b
Build: changelog update for 4.12.1
1e362a0
Revert "Fix: Use XML 1.1 on XML formatters (fixes #9607) (#9608)" (#9667)
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: