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

## The dependency [commander](https://github.com/tj/commander.js) was updated from `4.1.0` to `4.1.1`.

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

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

commander 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):** There are 1 failures, 0 warnings, and 0 notices.
- ✅ **build (windows-latest, 10.x):** null
- ❌ **build (windows-latest, 8.x):** There are 1 failures, 0 warnings, and 0 notices.
- ✅ **build (ubuntu-latest, 12.x):** null
- ✅ **build (ubuntu-latest, 10.x):** null
- ✅ **build (ubuntu-latest, 8.x):** null

---

Release Notes for v4.1.1

Fixed

• TypeScript definition for .action() should include Promise for async ([#1157])

Commits

The new version differs by 14 commits.

• d5186ba Bump version to 4.1.1


• 37e9428 Add 4.1.1 to CHANGELOG


• e5f316f Use npm ci with CI (#1164)


• cb54d5f fix(ts): action can be an async function (#1157)


• 6791884 Merge branch 'master' into develop


• f31d757 Add FUNDING file for enabling GitHub Sponsor on repo


• d9627f5 Merge pull request #1147 from shadowspawn/feature/changelog-lint


• 32c26df Use consistent list character in markdown


• 4092956 Merge branch 'master' into develop


• 82f5157 Fix diff order for 4.1 link


• 7a480a7 Add missing diff link for 4.1.0


• e45ae5a Merge pull request #1136 from shadowspawn/feature/update-examples


• d97aaaa Add missing diff link for 4.1.0


• 4922fb8 Update examples

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 checking the failing branch and reproducing the commander 4.1.1 update across the listed CI matrix, focusing on the Windows Node.js 8.x and 12.x failures. Compare the failing build output with the passing macOS and Ubuntu runs; done means the dependency update no longer breaks the Windows builds.

Written by the indexing model from the issue text.