search

nodecraft / spawnpoint

Agnostic JS framework that empowers devs to focus on quickly building apps, rather than application config, structure, health-checks, or architecture to build a 12 factor app in Docker.
MIT License
8 stars 5 forks source link

An in-range update of unexpected-eventemitter is breaking the build 🚨 #64

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency unexpected-eventemitter was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

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

unexpected-eventemitter is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ✅ **coverage/coveralls:** First build on greenkeeper/unexpected-eventemitter-2.2.0 at 91.746% ([Details](https://coveralls.io/builds/30876746)). - ❌ **Node 12 macOS-latest Test:** There are 2 failures, 0 warnings, and 0 notices. - ❌ **Node 10 macOS-latest Test:** There are 1 failures, 0 warnings, and 0 notices. - ❌ **Node 12 windows-latest Test:** There are 2 failures, 0 warnings, and 0 notices. - ❌ **Node 10 windows-latest Test:** There are 2 failures, 0 warnings, and 0 notices. - ✅ **Node 12 ubuntu-latest Test:** null - ✅ **Node 10 ubuntu-latest Test:** null
Commits

The new version differs by 2 commits.

  • 66a594b chore(release): 2.2.0
  • 2faaa59 feat: add "to emit with error" assertion

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

After pinning to 2.1.0 your tests are passing again. Downgrade this dependency 📌.