search

oneblink / aws-s3.js

our simplified wrapper for common AWS S3 operations
BSD 3-Clause "New" or "Revised" License
0 stars 1 forks source link

An in-range update of flow-bin is breaking the build 🚨 #51

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 0.54.1 of flow-bin just got published.

Branch Build failing 🚨
Dependency flow-bin
Current Version 0.54.0
Type devDependency

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

As flow-bin 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 - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/blinkmobile/aws-s3-js/build/1.0.130) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/blinkmobile/aws-s3.js/builds/272511299?utm_source=github_status&utm_medium=notification)
Commits

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