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

[greenkeeper]

The devDependency husky was updated from 3.0.2 to 3.0.3.

🚨 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 v3.0.3

Fix: prevent old hooks (husky < 1.0) to be run if new ones are defined (husky >= 1.0 ) #556

Commits

The new version differs by 12 commits.

• d067ac4 3.0.3
• 6a2d457 fix runner should not run old hooks defined in pkg.scripts if another one is in the new config
• 12bdd4c update please-upgrade-node
• d4062da Update README.md
• 80cb0bc Update README.md
• 8fad473 Update README.md
• 895667c Update README.md
• b4013bc Update README.md
• 9b279f5 Update README.md
• 3c15e76 Update README.md
• e674bf3 Update README.md
• f89c8c3 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.2 your tests are passing again. Downgrade this dependency 📌.