search

unional / demo-driven

Demo Driven Development
MIT License
1 stars 1 forks source link

An in-range update of aurelia-logging-color is breaking the build 🚨 #71

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 0.5.16 of aurelia-logging-color was just published.

Branch Build failing 🚨
Dependency aurelia-logging-color
Current Version 0.5.15
Type dependency

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

aurelia-logging-color 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 - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/unional/demo-driven/builds/410929128?utm_source=github_status&utm_medium=notification)).
Release Notes v0.5.16

0.5.16 (2018-08-01)

Bug Fixes

Commits

The new version differs by 12 commits.

  • a3df03b fix: environment detection (#40)
  • d86823c Update eslint to the latest version 🚀 (#39)
  • 0e4b101 fix: update to color-map@1.1 (#33)
  • 319993a fix: remove src from package.
  • f5afebc Update ava to the latest version 🚀 (#27)
  • 8fbea87 Greenkeeper/semantic release 12.2.4 (#26)
  • 9935534 Update dependency-check to the latest version 🚀 (#25)
  • f57bb2a Update eslint-config-unional to the latest version 🚀 (#23)
  • 739a286 Update tslint-config-unional to the latest version 🚀 (#21)
  • 1084c37 Update @types/node to the latest version 🚀 (#22)
  • 6fe9b6e Update color-map to the latest version 🚀 (#20)
  • 5bbb6c4 chore: fix lint issues

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 6 years ago

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