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 prettier-eslint-cli.
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 Notesv4.0.0
<a name"4.0.0">
4.0.0 (2017-05-21)
Bug Fixes
release: manually release a major version (d68ae4ff)
Breaking Changes
no more need for --prettier prefixing for Prettier's options
(d68ae4ff)
Commits
The new version differs by 2 commits.
d68ae4ffix(release): manually release a major version
9e11635Breaking Change: Be compatible with Prettier CLI (#59)
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 100.0% when pulling 4feabde1906be219a68d91ef23fdbc3b83fc2e67 on greenkeeper/prettier-eslint-cli-4.0.0 into e420c9f11778182208a5af1509877dcb434565be on master.
Coverage remained the same at 100.0% when pulling 4feabde1906be219a68d91ef23fdbc3b83fc2e67 on greenkeeper/prettier-eslint-cli-4.0.0 into e420c9f11778182208a5af1509877dcb434565be on master.
Version 4.0.0 of prettier-eslint-cli 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 prettier-eslint-cli. 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.0<a name"4.0.0">
4.0.0 (2017-05-21)
Bug Fixes
Breaking Changes
(d68ae4ff)
Commits
The new version differs by 2 commits.
d68ae4f
fix(release): manually release a major version
9e11635
Breaking Change: Be compatible with Prettier CLI (#59)
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: