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

[greenkeeper[bot]]

Version 10.0.3 of standard just got published.

Branch	Build failing 🚨
Dependency	standard
Current Version	10.0.2
Type	devDependency

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

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 :muscle:

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
• ✅ coverage/coveralls First build on greenkeeper/standard-10.0.3 at 93.162% Details

---

Release Notes

v10.0.3

• Internal changes (incremented dependency versions)

Commits

The new version differs by 99 commits.

• 91e80a1 10.0.3
• 82a0d5c changelog
• d22676e Merge pull request #963 from daper/patch-1
• cfb84fe Remove tilde to lock down eslint-config-standard-jsx version
• 4a6e0d0 Update dependecy of eslint-config-standard-jsx
• ac9e09e Merge pull request #961 from igorsantos07/patch-1
• 873bc9b Adding valid example for no-unsafe-negation
• f00b169 more feross/standard -> standard/standard
• 9770303 Merge pull request #954 from standard/security
• 8cc2285 Add a security policy
• 2fa8b0f change more feross/standard -> standard/standard
• e79a692 Merge branch 'devjin0617-translation-kr'
• 34490f7 Merge branch 'translation-kr' of https://github.com/devjin0617/standard into devjin0617-translation-kr
• 6d59566 Merge pull request #953 from standard/translations
• 3895bc6 move english readme/rules to docs/ folder

There are 99 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 10.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.