An in-range update of pretty-quick is breaking the build 🚨

[greenkeeper]

The devDependency pretty-quick was updated from 2.0.0 to 2.0.1.

🚨 View failing branch.

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

pretty-quick is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ Test on node 12.x and macOS-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 12.x and windows-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 12.x and ubuntu-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 10.x and macOS-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 10.x and windows-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 10.x and ubuntu-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 8.12.x and macOS-latest: There are 2 failures, 0 warnings, and 0 notices.
• ❌ Test on node 8.12.x and windows-latest: There are 1 failures, 0 warnings, and 0 notices.
• ❌ Test on node 8.12.x and ubuntu-latest: There are 2 failures, 0 warnings, and 0 notices.

---

Release Notes for v2.0.1

2.0.1 (2019-11-05)

Bug Fixes

• handling of submodules and .git path (#90) (#92) (3370668)

Commits

The new version differs by 8 commits.

• 3370668 fix: handling of submodules and .git path (#90) (#92)
• 6862b20 chore: update package.json (#89)
• 02438dc chore: use shared prettier config (#88)
• a8dfa9e chore(deps): bump hoek from 4.2.0 to 4.2.1 (#86)
• 4e80800 chore(deps): bump extend from 3.0.1 to 3.0.2 (#80)
• 65dfdde docs: make license live forever (#87)
• be91e96 chore(deps): bump nwmatcher from 1.4.3 to 1.4.4 (#78)
• 0e4bc04 chore(deps): bump sshpk from 1.13.1 to 1.16.1 (#81)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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

[agilgur5]

This was probably failing due to the intermittent persistent CI errors that #504 fixed.