An in-range update of travis-deploy-once is breaking the build 🚨

[greenkeeper]

The devDependency travis-deploy-once was updated from 5.0.7 to 5.0.8.

🚨 View failing branch.

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

travis-deploy-once 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

• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

---

Release Notes for v5.0.8

5.0.8 (2018-09-19)

Bug Fixes

• fix babel-register config when module is globally installed (4697ad5)

Commits

The new version differs by 3 commits.

• 4697ad5 fix: fix babel-register config when module is globally installed
• 8105e60 chore(package): update nock to version 10.0.0
• 43b48a3 chore(package): update xo to version 0.23.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 5.0.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.