This repository has been archived by the owner on Nov 8, 2019. It is now read-only.
Update cz-conventional-changelog to the latest version 馃殌 #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
2 similar comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 2.0.0 of cz-conventional-changelog 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 cz-conventional-changelog.
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-02-21)
Features
Breaking Changes
closes #17
(2d78e1d4)
Commits
The new version differs by 17 commits .
2d78e1dfeat(adapter): Split breaking changes into separate question (#44)042eadcMerge pull request #45 from commitizen/greenkeeper/commitizen-2.9.6cb65107chore(package): update commitizen to version 2.9.67025425Merge pull request #40 from commitizen/greenkeeper/commitizen-2.9.555c74f0chore(package): update commitizen to version 2.9.5dadb1a2Merge pull request #39 from commitizen/greenkeeper/commitizen-2.9.40d3aac1chore(package): update commitizen to version 2.9.4dcd7cccMerge pull request #38 from commitizen/greenkeeper/commitizen-2.9.3aae8ab7chore(package): update commitizen to version 2.9.30c55157Merge pull request #37 from commitizen/greenkeeper/commitizen-2.9.2d6315d5chore(package): update commitizen to version 2.9.23d654d8Merge pull request #35 from commitizen/greenkeeper/commitizen-2.9.05fb09cbchore(package): update commitizen to version 2.9.0ac1c81fMerge pull request #34 from commitizen/greenkeeper/commitizen-2.8.7a7ee137chore(package): update commitizen to version 2.8.7There are 17 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨