An in-range update of inquirer is breaking the build 🚨

## The dependency [inquirer](https://github.com/SBoudrias/Inquirer.js) was updated from `7.0.4` to `7.0.5`.

🚨 [View failing branch](https://github.com/cutenode/good-first-issue/compare/master...cutenode:greenkeeper%2Finquirer-7.0.5).

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

inquirer is a direct dependency of this project, and **it is very likely causing it to break**. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

- ❌ **build (macOS-latest, 12.x):** null
- ✅ **build (macOS-latest, 10.x):** null
- ✅ **build (macOS-latest, 8.x):** null
- ✅ **build (windows-latest, 12.x):** null
- ❌ **build (windows-latest, 10.x):** null
- ✅ **build (windows-latest, 8.x):** null
- ✅ **build (ubuntu-latest, 12.x):** null
- ✅ **build (ubuntu-latest, 10.x):** null
- ✅ **build (ubuntu-latest, 8.x):** null

---

Commits

The new version differs by 4 commits.

• 65a4d59 Publish


• e2099ed Update dependencies


• 8270551 Produce error on prompt in non-tty environment. (#891)


• 6a883e6 Update lint-staged to the latest version 🚀 (#886)

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](https://greenkeeper.io) Bot :palm_tree:

Start by reproducing the build with inquirer 7.0.5 and compare it with 7.0.4 across the failing macOS 12.x and Windows 10.x jobs. Trace the four upstream commits, then confirm that the affected build jobs pass without breaking the other listed Node.js versions and platforms.

Written by the indexing model from the issue text.