standard-version@2.3.1 breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

standard-version just published its new version 2.3.1.

State	Failing tests 🚨
Dependency	standard-version
New version	2.3.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As standard-version 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 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

The new version differs by 4 commits .

• 8369375 chore(release): 2.3.1
• e160445 test: explicitly run cli with node to fix tests on windows (#53)
• f361c46 fix(commit): fix windows by separating add and commit exec (#55)
• 5e56185 test: fix async mock-git tests (#54)

See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}

[coveralls]

Coverage remained the same at 98.039% when pulling 2fc0013 on greenkeeper-standard-version-2.3.1 into 29319d8 on master.