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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/tivac/mithril-codemods/builds/214631267)
Commits
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.13.3 of husky just got published.
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 :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/tivac/mithril-codemods/builds/214631267)Commits
The new version differs by 9 commits .
4b5011e0.13.36b92bb8Commentsc6f8bb10.13.3-0a2da709Prefer nvm over Node global install652c7f0Update README.mdd05a7b3Update README.md0bb5798Fix tests7af95d3update failure message (#107)be435caUpdate CHANGELOG.mdSee the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: