B-Stefan / CheckAuroa-Server

The server application for the check aurora service
2 stars 2 forks source link

An in-range update of node-cache is breaking the build 🚨 #63

Open greenkeeper[bot] opened 5 years ago

greenkeeper[bot] commented 5 years ago

The dependency node-cache was updated from 4.2.0 to 4.2.1.

🚨 View failing branch.

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

node-cache 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 is in progress ([Details](https://travis-ci.org/B-Stefan/CheckAuroa-Server/builds/563271209?utm_source=github_status&utm_medium=notification)). - ❌ **CheckAuroa-Server:** Build failed ([Details](https://g.codefresh.io/build/5d38c5a74ca9052e2e32ed44)).

Commits

The new version differs by 15 commits.

  • f0c55ff updated lodash to latest 4.17.15
  • f0a9e97 bump version 4.2.1
  • 13f1b0c update readme for v4.2.1
  • 0aae371 fix some typos - thx @daluf
  • b3fd6c4 fix tests with new mocha + coffee script dependencies
  • c72383d Merge pull request #128 from AndrewLane/patch-1
  • 3a19704 Typo fix
  • 8399b71 clean up dockertests, update package.json, update copyright
  • ff189d4 Merge branch 'update-dependencies'
  • 09682f1 warn about upcoming major release
  • b208726 update dependencies so npm audit will shut up; update nvmrc to 10.16
  • ca51a2e Merge branch 'master' of github.com:mpneuried/nodecache
  • 5edeb0d add .nvmrc
  • f30c814 Merge pull request #120 from IsuruNana/patch-1
  • c9c3f97 Fix typo (exmaple to example) in README.md

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 4.2.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.