search

cinecove / defunctr

Browser detection based on feature inspection
BSD 3-Clause "New" or "Revised" License
27 stars 2 forks source link

An in-range update of gulp-bump is breaking the build 🚨 #149

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.8.0 of gulp-bump just got published.

Branch Build failing 🚨
Dependency gulp-bump
Current Version 2.7.0
Type devDependency

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

As gulp-bump 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 is in progress [Details](https://travis-ci.org/cinecove/defunctr/builds/282294741?utm_source=github_status&utm_medium=notification) - ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/cinecove/defunctr/1ef04819c00154ea98415d05f44d2fc71b908dd0/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/cinecove/defunctr/1ef04819c00154ea98415d05f44d2fc71b908dd0/files?status=passing)
Release Notes gulp-bump@2.8.0
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 6 years ago

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