Update commitizen to the latest version 馃殌 #39
Merged
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}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.9.4 of commitizen just got published.
The version 2.9.4 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 commitizen.
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.9.42.9.4 (2017-01-06)
Bug Fixes
Commits
The new version differs by 17 commits .
1d3139ffix(commit): fix multiline commits with newlinesa97e3f8ci(coverage): remove already tested branches not showing up in coveragedd9298fchore(package): update find-node-modules to version 1.0.4 (#384)0ac499cMerge branch 'master' of github.com:commitizen/cz-clie02c705Allow using ES6 modules with default export (#328)89b9a03chore(package): update babel-core to version 6.18.2 (#379)2eb14c2ci(appveyor): retry failed npm installs2a09176ci(appveyor): bypass npm cacheafb47f7chore(package): update inquirer to version 1.2.3 (#385)3b9f0a6Update shelljs to version 0.7.5 馃殌 (#372)7d7b2e3chore(package): update lodash to version 4.17.2 (#389)6deeb1dchore(package): update ghooks to version 1.3.2 (#277)c9d6c11chore(package): update babel-preset-stage-2 to version 6.18.0 (#371)0b9e519chore(package): update babel-preset-es2015 to version 6.18.0 (#370)3aae4f6chore(package): update babel-cli to version 6.18.0 (#369)There 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 馃尨