standard@8.6.0 breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

standard just published its new version 8.6.0.

State	Failing tests 🚨
Dependency	standard
New version	8.6.0
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 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 65 commits .

• 3f88a12 8.6.0
• b771408 changelog
• 4c82bc8 Remove standard-format references
• 938dcc3 standard-engine@5.2
• 21f0ca4 cross-spawn@5
• 451da5f eslint-plugin-react@6.7
• f27f1df eslint-plugin-promise@3.4
• e542e03 eslint@3.10
• 66f1ead Merge pull request #684 from capaj/patch-2
• a0280a9 added vscode-standardjs-snippets
• 1623ef3 authors
• 62d7bf4 8.5.0
• a9b6d58 changelog 8.5.0
• d9c6e2a eslint-config-standard@6.2.1
• e0e197d eslint-plugin-promise@3.3

There are 65 commits in total. 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 100.0% when pulling b2f942b on greenkeeper-standard-8.6.0 into 2de6d26 on master.