search

ForbesLindesay / base64-encode

Encode base-64 strings with JavaScript
MIT License
6 stars 4 forks source link

An in-range update of better-assert is breaking the build 🚨 #8

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 7 years ago

Version 1.0.2 of better-assert just got published.

Branch Build failing 🚨
Dependency better-assert
Current Version 1.0.1
Type devDependency

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

As better-assert 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/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/ForbesLindesay/base64-encode/builds/268305407?utm_source=github_status&utm_medium=notification)
Release Notes Release v1.0.2

fix bug in node v0.11.*

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