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 mukla is breaking the build 🚨 #16

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 0.4.9 of mukla just got published.

Branch Build failing 🚨
Dependency mukla
Current Version 0.4.8
Type devDependency

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

As mukla 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/211957647) - ✅ **coverage/coveralls** First build on greenkeeper/mukla-0.4.9 at 100.0% [Details](https://coveralls.io/builds/10636978) - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/tunnckoCore/minibase/build/1.0.71)
Commits

The new version differs by 6 commits .

  • a895cc4 chore(release): 0.4.9
  • b93c4d4 fix(readme): update readme template
  • d036e6f fix(ci): update CI and add appveyor
  • 4d00b3c fix(package): update deps and npm scripts
  • 3992991 fix(package): use stacktrace-metadata for better reporter
  • 4b7ad36 chore(package): remove lazy-cache

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: