An in-range update of commitizen is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
The devDependency commitizen was updated from 3.1.1
to 3.1.2
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
commitizen is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Commits
The new version differs by 5 commits.
4417fcf
fix: release fixed sem-release (#648)
b3dd4c4
fix: update dependencies for security (#645)
1875a38
fix(deps): update dependency lodash to v4.17.14 [security] (#641)
372c75e
docs: highlight pre-requisties and bubble up related sections (#613)
b24eade
chore(security): fixed 5 vulnerabilities (#599)
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 π΄
After pinning to 3.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.