-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update commitizen to the latest version 🚀 #53
base: master
Are you sure you want to change the base?
Conversation
Version 2.10.1 just got published.Update to this version instead 🚀 Release Notesv2.10.1<a name"2.10.1"> 2.10.1 (2018-05-24)Bug FixesCommitsThe new version differs by 11 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v3.0.0<a name"3.0.0"> 3.0.0 (2018-10-01)Bug Fixes
Features
Breaking Changes
Includes most updates with the exception of semantic-release which breaks on windows. To be investigated in a later release. CommitsThe new version differs by 23 commits.
There are 23 commits in total. See the full diff |
Update to this version instead 🚀 Release Notes for v3.0.1<a name"3.0.1"> 3.0.1 (2018-10-01)Bug Fixes |
Update to this version instead 🚀 Release Notes for v3.0.2<a name"3.0.2"> 3.0.2 (2018-10-03)Bug Fixes |
Update to this version instead 🚀 Release Notes for v3.0.3<a name"3.0.3"> 3.0.3 (2018-10-19)Bug Fixes |
Update to this version instead 🚀 Release Notes for v3.0.4<a name"3.0.4"> 3.0.4 (2018-10-20)Bug Fixes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Version 2.10.0 of commitizen was just published.
commitizen
The version 2.10.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of commitizen.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v2.10.0<a name"2.10.0">
2.10.0 (2018-05-24)
Bug Fixes
Features
--allow-emtpy
flag (#477) (495437c1)Commits
The new version differs by 15 commits.
89300f5
Configure Renovate (#464)
0023958
fix: lodash Node Security warning (#482)
40d8dab
Activating Open Collective (#468)
495437c
feat(strategies): respect the
--allow-emtpy
flag (#477)07b92bc
docs: Fix Angular commit conventions link (#458)
53853fe
chore(Update cz-conventional-changelog to 2.0.0): (#439)
d74b920
chore: add a project .editorconfig (#456)
f359d65
docs(readme): change deprecated adapter (#457)
4b32235
docs(contributing): Indentation usage and link to angular convention (#455)
de2459f
Grammar and layout tweaks (#447)
f2f0453
docs($README): add related projects (#444)
53719a4
fix(cli): Don't print error stack trace if git-cz failed (#436) (#437)
2e283a3
docs($readme): add note about avoiding double calls to
precommit
(#433)d5e2424
fix(adapter): Don't print git root to stdout (#428)
bc39af3
docs(readme): Fix incorrect spelling of "changelog" (#427)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴