-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of husky is breaking the build 🚨 #44
Comments
After pinning to 1.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
The devDependency husky was updated from
1.1.1
to1.1.2
.🚨 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 9 commits.
05f57f2
1.1.2
bbacc43
Update CHANGELOG.md
89efe65
Check that HUSKY_DEBUG equals "true"
0177900
Update CHANGELOG.md
ab4a28e
Fix "[[: not found"
2c98004
Update package-lock.json
74149bc
Update debug message
528c52a
Add HUSKY_DEBUG=true to .travis.ym
39678b3
Print debug message at hook start (#377)
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: