Closed greenkeeper[bot] closed 4 years ago
After pinning to 6.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
@semantic-release/commit-analyzer was updated from 6.3.0
to 6.3.1
.Your tests are still failing with this version. Compare changes
dependency
@semantic-release/commit-analyzer was updated from 6.3.1
to 6.3.2
.Your tests are still failing with this version. Compare changes
dependency
@semantic-release/commit-analyzer was updated from 6.3.2
to 6.3.3
.Your tests are still failing with this version. Compare changes
The dependency @semantic-release/commit-analyzer was updated from
6.2.0
to6.3.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@semantic-release/commit-analyzer is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ **Travis CI - Branch:**Release Notes for v6.3.0
6.3.0 (2019-08-09)
Features
Commits
The new version differs by 3 commits.
edad14c
feat: add support for conventionalcommits preset
247504d
chore(package): update commitizen to version 4.0.0
dbfb73a
ci(node): set node 8 to 8.3 and add node 12
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: