-
Notifications
You must be signed in to change notification settings - Fork 1
An in-range update of husky is breaking the build 🚨 #44
Comments
After pinning to 1.1.2 your tests are passing again. Downgrade this dependency 📌. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 22 commits.
There are 22 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 26 commits.
There are 26 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 32 commits.
There are 32 commits in total. See the full diff |
The devDependency husky was updated from
1.1.2
to1.1.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
Commits
The new version differs by 8 commits.
30619a3
1.1.3
96a73fc
Update dependencies
5c8d938
Don't fail if package.json doesn't exist
b94ac5c
Update README.md
f1a0457
Update README.md
4aa6487
Update README.md
6fd89e8
Update DOCS.md
4924a42
Update dependencies
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 🌴
The text was updated successfully, but these errors were encountered: