An in-range update of semantic-release is breaking the build 🚨

[greenkeeper[bot]]

The devDependency semantic-release was updated from 15.13.16 to 15.13.17.

🚨 View failing branch.

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

semantic-release 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 failed ([Details](https://travis-ci.org/Kronos-Integration/test-step/builds/550386223?utm_source=github_status&utm_medium=notification)).

---

Release Notes for v15.13.17

15.13.17 (2019-06-25)

Bug Fixes

• package: update execa to version 2.0.0 (52c48be)

Commits

The new version differs by 2 commits.

• 01a0b2d test: use regexp to check missing module message
• 52c48be fix(package): update execa to version 2.0.0

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 15.13.16 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 semantic-release was updated from 15.13.17 to 15.13.18.

Your tests are still failing with this version. Compare changes

Release Notes for v15.13.18

15.13.18 (2019-06-26)

Bug Fixes

• revert to execa ^1.0.0 (6b3adf6)

Commits

The new version differs by 2 commits.

• 6b3adf6 fix: revert to execa ^1.0.0
• 228fed7 docs: document that plugins config is an override (#1216)

See the full diff