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 minibase-tests is breaking the build 🚨 #7

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.1.1 of minibase-tests just got published.

Branch Build failing 🚨
Dependency minibase-tests
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 minibase-tests 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 passed [Details](https://travis-ci.org/node-minibase/minibase/builds/176596366) - ✅ **coverage/coveralls** First build on greenkeeper/minibase-tests-1.1.1 at 100.0% [Details](https://coveralls.io/builds/8867297) - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/tunnckoCore/minibase/build/1.0.18)
Commits

The new version differs by 6 commits .

  • 366f086 chore(release): 1.1.1
  • f2faf60 fix(appveyor): allow failures
  • 518051e chore(appveyor): activate appveyor
  • 16bc4f4 docs(layout): update verb readme layout
  • 7dbe7ae docs(api): update api docs
  • 6291e8f fix(tests): fix and remove tests for "use" event

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: