The version 6.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 typescript-eslint-parser.
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.
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 96.154% when pulling c47b5a58a12437391a560a671f55e44b87eaf7f3 on greenkeeper/typescript-eslint-parser-6.0.0 into 0783c22e5f8cb630eeb70075584f4ac0dd798e9a on master.
Version 6.0.0 of typescript-eslint-parser just got published.
The version 6.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 typescript-eslint-parser. 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
v6.0.0Commits
The new version differs by 11 commits.
9909aa1
6.0.0
2237dc9
Build: changelog update for 6.0.0
32c0cc8
Breaking: Explicitly handle TSEnumDeclaration (fixes #345) (#364)
5f741a9
Fix: Allow other orderings of implements/extends clauses (fixes #361) (#363)
f5bd145
Chore: Breakout and label TS-specific AST comparison tests (#360)
f6e56b3
Chore: Build out AST comparison tests and categorize issues (#358)
ab4e05e
Breaking: Only add .implements/.accessibility/.decorators if truthy (#354)
275897b
Fix: Location data for methods and constructors (#357)
5fce5e7
Fix: Exp. operator assignment is AssignmentExpression (fixes #355) (#356)
67971de
Fix: Include newlines at the end of source in AST (fixes #352) (#353)
8406209
Fix: Remove start and end values from JSX tokens (fixes #341) (#351)
See the full diff
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: