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

[greenkeeper]

Version 0.13.3 of husky just got published.

Branch	Build failing 🚨
Dependency	husky
Current Version	0.13.2
Type	devDependency

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

As husky is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

---

Status Details

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

Commits

The new version differs by 9 commits .

• 4b5011e 0.13.3
• 6b92bb8 Comments
• c6f8bb1 0.13.3-0
• a2da709 Prefer nvm over Node global install
• 652c7f0 Update README.md
• d05a7b3 Update README.md
• 0bb5798 Fix tests
• 7af95d3 update failure message (#107)
• be435ca Update CHANGELOG.md

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

Version 0.13.4 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 9 commits.

• 5c6d1e6 0.13.4
• b330a22 Add .npmignore (#127)
• b500d3c Update README.md
• 2885443 index.js: minor reformat (#118)
• 0bd9db0 minor: update number of dependent projects (#122)
• 9d027eb Log Node version
• 803e841 Refactor
• df86893 Update CHANGELOG.md
• 41f40b1 Update README.md

See the full diff