search

Kronos-Integration / kronos-step-archive-arangodb

Stores blob data into the aragodb
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

An in-range update of mocha is breaking the build 🚨 #129

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 3.5.3 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.5.2
Type devDependency

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

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/Kronos-Integration/kronos-step-archive-arangodb/2192ff693d8c6db97afa4169599e0fe107023aca/dependencies/npm?status=passing) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/Kronos-Integration/kronos-step-archive-arangodb/2192ff693d8c6db97afa4169599e0fe107023aca/files?status=passing) - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Kronos-Integration/kronos-step-archive-arangodb/builds/274442010?utm_source=github_status&utm_medium=notification)
Release Notes v3.5.3

3.5.3 / 2017-09-11

🐛 Fixes

  • #3003: Fix invalid entities in xUnit reporter first appearing in v3.5.1 (@jkrems)
Commits

The new version differs by 3 commits.

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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