Closed greenkeeper[bot] closed 7 years ago
Update to this version instead 🚀
Update to this version instead 🚀
Update to this version instead 🚀
Update to this version instead 🚀
The new version differs by 8 commits .
2915827
fix(package): "main" property within "package.json" (#409)
852d6f6
style: Add linting using eslint (#406)
6d282be
ci(appveyor): remove appveyor on finish script
f9a78e3
ci(appveyor): disable collection of artifacts
a655308
ci(tests): on windows run tests as node4/npm3
02021b9
ci(travis): update semantic-release to 6.3.5 and update travis config
9e88876
chore(package): update nyc to version 10.0.0 (#392)
ca32961
docs(install): Add documentation for installing and running locally (#300)
See the full diff.
Update to this version instead 🚀
The new version differs by 17 commits .
1d3139f
fix(commit): fix multiline commits with newlines
a97e3f8
ci(coverage): remove already tested branches not showing up in coverage
dd9298f
chore(package): update find-node-modules to version 1.0.4 (#384)
0ac499c
Merge branch 'master' of github.com:commitizen/cz-cli
e02c705
Allow using ES6 modules with default export (#328)
89b9a03
chore(package): update babel-core to version 6.18.2 (#379)
2eb14c2
ci(appveyor): retry failed npm installs
2a09176
ci(appveyor): bypass npm cache
afb47f7
chore(package): update inquirer to version 1.2.3 (#385)
3b9f0a6
Update shelljs to version 0.7.5 🚀 (#372)
7d7b2e3
chore(package): update lodash to version 4.17.2 (#389)
6deeb1d
chore(package): update ghooks to version 1.3.2 (#277)
c9d6c11
chore(package): update babel-preset-stage-2 to version 6.18.0 (#371)
0b9e519
chore(package): update babel-preset-es2015 to version 6.18.0 (#370)
3aae4f6
chore(package): update babel-cli to version 6.18.0 (#369)
There are 17 commits in total. See the full diff.
Update to this version instead 🚀
Version 2.8.7 of commitizen just got published.
The version 2.8.7 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.8.72.8.7 (2016-12-14)
Bug Fixes
Commits
The new version differs by 81 commits .
6fa09a2
fix(npmignore): ignore more unnecessary files (#393)
4586f15
docs: add vscode-commitizen to tools list (#397)
71731ca
Ci issues with commits (#402)
5f4ab63
chore(ci): add node versions and say git version in ci
fd51001
docs: replace sudo mention with link to how to fix EACCES error
45ff06f
chore(package): update axios to version 0.15.1 (#365)
e56d779
chore(package): update inquirer to version 1.2.2 (#364)
79ab068
chore(package): update mocha to version 3.1.2 (#363)
7ce4bb6
chore(package): update axios to version 0.15.0 (#362)
bd408d2
chore(package): update mocha to version 3.1.1 (#361)
ae6c612
chore(package): update glob to version 7.1.1 (#360)
a2a669e
chore(package): update nodemon to version 1.11.0 (#358)
0cae5b2
chore(package): update lodash to version 4.16.3 (#356)
dddbb65
chore(package): update babel-preset-stage-2 to version 6.17.0 (#355)
7f71340
chore(package): update babel-core to version 6.17.0 (#354)
There are 81 commits in total. 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: