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

[greenkeeper]

The devDependency husky was updated from 1.2.0 to 1.2.1.

🚨 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 failed (Details).

---

Commits

The new version differs by 7 commits.

• 73c0ad7 1.2.1
• cb5fd3b Update CHANGELOG.md
• c0e5f5e Update package-lock.json
• aabd390 Fix whitespace in project folder name issue (#423)
• d43f813 Update README.md
• f0fcc21 Update README.md
• 4897994 npm upgrade

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 1.2.0 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 1.2.1 to 1.3.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

• c13003e 1.3.0
• 439c271 Update CHANGELOG.md
• d90e2d5 Update CHANGELOG.md
• 2b5ac5f Enable stdin if terminal (#415)

See the full diff