An in-range update of @makeomatic/deploy is breaking the build 🚨

Nobody has claimed this yet.

## Version **1.6.0** of [@makeomatic/deploy](https://github.com/makeomatic/deploy) just got published.

Branch


Build failing 🚨




Dependency


@makeomatic/deploy




Current Version


1.4.0




Type


devDependency

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

As @makeomatic/deploy is “only” a devDependency of this project it **might not break production or downstream projects**, but “only” your build or test tools – **preventing new deploys or publishes**.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details

- ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/makeomatic/ms-mailer/branches/greenkeeper-makeomatic-deploy-1-6-0/builds/1)

---

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start by opening the failed Semaphore build for the greenkeeper/@makeomatic/deploy-1.6.0 branch and identify the build step that fails. Then inspect the project's dependency configuration and the changes between @makeomatic/deploy 1.4.0 and 1.6.0. Done means the build passes with the supported dependency range and deploy or publish workflows are no longer blocked.

Written by the indexing model from the issue text.