Open greenkeeper[bot] opened 5 years ago
After pinning to 7.0.11 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
devDependency
@semantic-release/git was updated from 7.0.13
to 7.0.14
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@semantic-release/git was updated from 7.0.14
to 7.0.15
.Your tests are passing again with this update. Explicitly upgrade to this version π
devDependency
@semantic-release/git was updated from 7.0.15
to 7.0.16
.Your tests are passing again with this update. Explicitly upgrade to this version π
The new version differs by 5 commits.
a93b846
fix(package): update globby to version 10.0.0
2819d3b
fix(package): update dir-glob to version 3.0.0
184f7b3
fix: revert to execa ^1.0.0
39c4fd5
fix(package): update execa to version 2.0.0
3394211
chore(package): update ava to version 2.0.0
See the full diff
devDependency
@semantic-release/git was updated from 7.0.16
to 7.0.17
.Your tests are passing again with this update. Explicitly upgrade to this version π
The new version differs by 12 commits.
5132713
fix(package): update execa to version 3.2.0
7c9eb9a
fix: require Node.js >=8.16
4b73226
chore(package): update xo to version 0.25.2
a317bae
ci(node): set node 8 to node 8.3 and add node 12
4cb24c8
chore(package): update clear-module to version 4.0.0
9043edc
chore: remove commitizen from our dependencies
55c6df7
chore(package): update commitizen to version 4.0.0
a93b846
fix(package): update globby to version 10.0.0
2819d3b
fix(package): update dir-glob to version 3.0.0
184f7b3
fix: revert to execa ^1.0.0
39c4fd5
fix(package): update execa to version 2.0.0
3394211
chore(package): update ava to version 2.0.0
See the full diff
The devDependency @semantic-release/git was updated from
7.0.11
to7.0.12
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@semantic-release/git 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
- β **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/kevinmerckx/ng-playground/builds/544927421?utm_source=github_status&utm_medium=notification)).Release Notes for v7.0.12
7.0.12 (2019-05-14)
Bug Fixes
Commits
The new version differs by 4 commits.
712d684
fix(package): update fs-extra to version 8.0.0
185f94e
chore(package): update tempy to version 0.3.0
7f516ac
chore(package): update nyc to version 14.0.0
a24f2db
chore(package): update file-url to version 3.0.0
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: