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

[greenkeeper]

The devDependency husky was updated from 4.2.1 to 4.2.2.

🚨 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v4.2.2

• Fix #662 disable fast-skip heuristic for .husky.js and .husky.config.js
• Fix do not install update, pre/post-receive hooks

Commits

The new version differs by 7 commits.

• c16aa78 4.2.2
• 9e65360 update snapshot
• 015f3aa fix husky.sh syntax error
• 7791433 Fix #662 disable fast-skip heuristic for .husky.js and .husky.config.js
• 7e79d16 Fix: do not install server hooks
• b05fe3b Added husky.config.js (#595)
• 2998c95 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 4.2.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency husky was updated from 4.2.2 to 4.2.3.

Your tests are still failing with this version. Compare changes

Release Notes for v4.2.3

• Fix: check for husky.config.js not .huskyrc.config.js #669

Commits

The new version differs by 2 commits.

• df75e8a 4.2.3
• d9d8de3 fix: husky.config.js not .huskyrc.config.js (#669)

See the full diff