An in-range update of husky is breaking the build 🚨
greenkeeper opened this issue · comments
The devDependency husky was updated from 2.5.0 to 2.6.0.
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
- ❌ Travis CI - Branch:
The build failed.
The buildCommits
The new version differs by 9 commits.
ae5700e2.6.0e85d280update CHANGELOG.md8d4f833Merge branch 'master' of https://github.com/typicode/husky449a615adds an optional settings to use Yarn to run Husky (#511)0f68515add more debug messages1255096Open Collective integrationf7029a1Update CHANGELOG.mdfa449edupdate engines node in package.json (#512)f276923Update CHANGELOG.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 🌴
After pinning to 2.5.0 your tests are passing again. Downgrade this dependency 📌.
- The
devDependencyhusky was updated from2.6.0to2.7.0.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
- The
devDependencyhusky was updated from2.7.0to3.0.0.
Your tests are passing again with this update. Explicitly upgrade to this version 🚀
Commits
The new version differs by 16 commits.
06893a03.0.08b5924fUpdate README.md4e044f6Correct typos (#522)0843abdUpdate README.mdb5793bfUpdate README.mdf3fed433.0.0-04d2bf26Update CHANGELOG.md1bb44dfUpdate CHANGELOG.md479e08aFix HUSKY_SKIP_INSTALL=1 not skipping install (#518)ca57293show error if --absolute-git-dir isn't supportedb60a1a9Update CHANGELOG.md8920e33Update README.mda90bdd3Update README.md4e8ebc2Update README.md086a5e0use absolute git dir (#516)
There are 16 commits in total.
See the full diff