search

node-minibase / minibase

:rocket: Minimal framework for creating highly modular and composable Node.js applications powered by plugins
https://github.com/node-minibase
MIT License
9 stars 0 forks source link

An in-range update of isobject is breaking the build 🚨 #24

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 3.0.1 of isobject just got published.

Branch Build failing 🚨
Dependency isobject
Current Version 3.0.0
Type dependency

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

isobject is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/tunnckoCore/minibase/build/1.0.96) - ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/12209639) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/node-minibase/minibase/builds/248890869?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 7 commits.

  • 7ad1fc4 3.0.1
  • b6de34a run verb to generate readme
  • 97b0a9d run update
  • add71c5 Merge pull request #8 from onokumus/master
  • ed08aa7 add optional types field in package.json
  • 2a0a71e include typescript type definitions in package
  • e353aa5 add typescript declaration file

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