search

Kronos-Integration / kronos-step-aggregate

step to aggregate requests from several endpoints
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

An in-range update of c8 is breaking the build 🚨 #651

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency c8 was updated from 5.0.2 to 5.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

c8 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 failed ([Details](https://travis-ci.org/Kronos-Integration/kronos-step-aggregate/builds/581807966?utm_source=github_status&utm_medium=notification)).
Release Notes for c8 v5.0.3

Bug Fixes

  • deps: update dependency rimraf to v3 (#132) (7601748)
  • deps: update dependency yargs to v14 (#134) (e49737f)
  • deps: update deps to address warning in cross-spawn (#141) (4b66221)
Commits

The new version differs by 8 commits.

  • 36ee27e chore: release 5.0.3 (#142)
  • 4b66221 fix(deps): update deps to address warning in cross-spawn (#141)
  • 2289302 chore(deps): update dependency mocha to v6.2.0 (#129)
  • af054df chore(deps): update dependency coveralls to v3.0.6 (#131)
  • 3fef41e chore(deps): update dependency standard-version to v7 (#130)
  • 7601748 fix(deps): update dependency rimraf to v3 (#132)
  • e49737f fix(deps): update dependency yargs to v14 (#134)
  • 82030ea chore(deps): update dependency coveralls to v3.0.5 (#128)

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:

greenkeeper[bot] commented 5 years ago

After pinning to 5.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 5 years ago

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 6 commits.

  • a107093 chore(release): 5.0.4
  • 1ebcaf9 fix(deps): merging failed when the same script occurred multiple times in the same report (#147)
  • 94ae71c chore: stop pinning deps
  • a6481f1 fix: don't load JSON that does not look like coverage (#146)
  • 9b3d089 fix(deps): update dependency yargs-parser to v14 (#144)
  • c05ec2e chore: update package-lock.json

See the full diff