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

## The dependency [open](https://github.com/sindresorhus/open) was updated from `7.0.1` to `7.0.2`.

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

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

open 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

---

Release Notes for v7.0.2

• Fix Docker in WSL2 for real (#168) 2c1647d

v7.0.1...v7.0.2

Commits

The new version differs by 2 commits.

• d8bf43e 7.0.2


• 2c1647d Fix Docker in WSL2 for real (#168)

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 failing Windows builds for Node.js 8.x and 12.x, then compare the dependency update from open 7.0.1 to 7.0.2 and inspect the linked failing branch. Done means the Windows build passes without breaking the successful macOS and Ubuntu builds.

Written by the indexing model from the issue text.