The version 2.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 conventional-changelog-lint.
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).
Version 2.0.0 of conventional-changelog-lint just got published.
The version 2.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 conventional-changelog-lint. 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
v2.0.02.0.0 (2017-07-07)
Bug Fixes
Features
Commits
The new version differs by 10 commits.
c78cece
chore(release): v2.0.0
f0b83d8
feat: ignore fixup and squash commit (#17)
318a67f
refactor: move ignore wildcard matching to isIgnore method
702a2f7
fix: rebuff rules (#34)
1e69d54
docs: add recipe for linting of all commits in a PR (#36)
a0914d1
chore: tweaks to commit linting
ac820c8
chore: solidify lint-prcommits
627b3f3
chore: test commits in pr via Travis CI (#37)
05b4427
fix: prevent false positives for footer-leading-blank (#33)
8c354c5
fix: throw when detecting a shallow clone
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: