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

[greenkeeper]

The devDependency husky was updated from 3.0.4 to 3.0.5.

🚨 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

• ❌ ci/circleci: build: Your tests failed on CircleCI (Details).

---

Release Notes for v3.0.5

Fix: prevent postinstall from failing on windows #573

Commits

The new version differs by 9 commits.

• 2dd9985 3.0.5
• e0b99e6 [Fix] Prevent postinstall from ever failing on windows (#573)
• 2f56681 add table of contents (#572)
• 03b0b2f Bump mixin-deep from 1.3.1 to 1.3.2 (#571)
• e15e09e Delete DOCS.md
• 75a38e1 Update README.md
• 96dd62c Bump eslint-utils from 1.3.1 to 1.4.2 (#569)
• d3e6a76 Next.js doesn't use husky now (#568)
• 179ffbe Update README.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.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.