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

[greenkeeper]

The devDependency husky was updated from 3.0.9 to 3.1.0.

🚨 View failing branch.

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

husky 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 1 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 1 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 v3.1.0

• Add pre-merge-commit hook (#605)

Commits

The new version differs by 5 commits.

• 436ca18 3.1.0
• 795508d add funding field
• 2b601d2 Add pre-merge-commit (#605)
• 3a844a6 Update README.md
• abcb11a update ISSUE_TEMPLATE.md

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 3.0.9 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.