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

[greenkeeper]

The devDependency travis-deploy-once was updated from 5.0.9 to 5.0.10.

🚨 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).

---

Release Notes for v5.0.10

5.0.10 (2018-12-12)

Bug Fixes

• package: update p-retry to version 3.0.0 (b360e09)

Commits

The new version differs by 3 commits.

• b360e09 fix(package): update p-retry to version 3.0.0
• fe68469 chore(package): update nyc and sinon
• 0f8d0d3 chore(package): update commitizen to version 3.0.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.9 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency travis-deploy-once was updated from 5.0.10 to 5.0.11.

Your tests are still failing with this version. Compare changes

Release Notes for v5.0.11

5.0.11 (2018-12-15)

Bug Fixes

• readme: add deprecation notice (70e9057)

Commits

The new version differs by 1 commits.

• 70e9057 fix(readme): add deprecation notice

See the full diff