search

logan-engineering / limited-10-builder

0 stars 0 forks source link

An in-range update of function-bind is breaking the build 🚨 #27

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.1.1 of function-bind just got published.

Branch Build failing 🚨
Dependency function-bind
Current Version 1.1.0
Type devDependency

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

As function-bind 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 - Code** 3 failing files. [Details](https://www.bithound.io/github/logan-engineering/limited-10-builder/3e9bf05ab5b9fc67e795d386a82f334bc55fe751/files#filter-failing-file) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/logan-engineering/limited-10-builder/3e9bf05ab5b9fc67e795d386a82f334bc55fe751/dependencies/npm?status=passing)
Commits

The new version differs by 6 commits.

  • 1213f80 v1.1.1
  • 817f7d2 [Tests] up to node v8; newer npm breaks on older node; fix scripts
  • 854288b [Dev Deps] update eslint, jscs, tape, @ljharb/eslint-config
  • 5ed97f5 Only apps should have lockfiles
  • 5feefea Use a SPDX-compliant “license” field.
  • 83e639f [Dev Deps] update tape, jscs, eslint, @ljharb/eslint-config

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