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

[greenkeeper[bot]]

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

🚨 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/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/Dexus/pem/builds/434227150?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v5.0.9

5.0.9 (2018-09-27)

Bug Fixes

• use require.resolve to load babel preset (16292d3)

Commits

The new version differs by 2 commits.

• 16292d3 fix: use require.resolve to load babel preset
• 858d475 test: add babel-register.js to test coverage

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]]

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

[greenkeeper[bot]]

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

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

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