Closed greenkeeper[bot] closed 6 years ago
Merging #131 into master will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #131 +/- ##
=======================================
Coverage 85.98% 85.98%
=======================================
Files 54 54
Lines 1320 1320
=======================================
Hits 1135 1135
Misses 185 185
Update to this version instead 🚀
<a name"2.10.1">
The new version differs by 11 commits.
5838ce0
chore(deps): update dependency eslint-plugin-standard to v2.3.1 (#492)
0dd9183
chore(deps): update dependency node-uuid to v1.4.8 (#494)
1df0d8a
chore(deps): update dependency nodemon to v1.17.5 (#495)
ff1268d
chore(deps): update dependency mocha to v3.5.3 (#493)
c3b920b
chore(deps): update dependency eslint-plugin-promise to v3.7.0 (#490)
94b29de
chore(deps): update dependency eslint to v3.19.0 (#489)
d92b728
chore(deps): update dependency axios to v0.18.0 (#488)
f856f92
Docs: Updates Angular commit conventions link in Contributing.md (#472)
d10c94f
fix(cli): Respect git commit -a original behavior (#376) (#471)
5f8902e
fix(config): prioritized package.json last when looking for config files (#484)
4b8f29a
chore(deps): update babel6 monorepo (#487)
See the full diff
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](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: