The version 4.0.0 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 tslint.
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.
[enhancement] adjacent-overload-signatures now works with classes, source files, modules, and namespaces (#1707)
[enhancement] Users are notified if they are using an old TSLint version (#1696)
[bugfix] Lint .jsx files if jsRules are configured (#1714)
[bugfix] Command line glob patterns now handle single quotes (#1679)
Thanks to our contributors!
Andrii Dieiev
Andy
Chris Barr
Davie Schoots
Jordan Hawker
Josh Goldberg
Stepan Riha
Yuichi Nukiyama
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 85.273% when pulling ea143f323681351f3cc6a6bd0d4aa5ef011de0c8 on greenkeeper/tslint-4.0.0 into f8a0545ae61f9c0c69b6c129ccd731254b45221b on master.
Version 4.0.0 of tslint just got published.
The version 4.0.0 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 tslint. 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.
Release Notes
v4.0.0v4.0.0
Check out the blog post!
no-unreachable
rule; covered by compiler (#661)extends
array to make it more intuitive (#1503)completed-docs
rule added (#1644)ordered-imports
auto fixed (#1640)arrow-parens
auto fixed (#1731)indent
rule now ignores template strings (#1611)object-literal-key-quotes
adds the optionsconsistent
andconsistent-as-needed
(#1733)--fix
option added to automatically fix selected rules (#1697)adjacent-overload-signatures
now works with classes, source files, modules, and namespaces (#1707).jsx
files ifjsRules
are configured (#1714)Thanks to our contributors!
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: