Update husky to the latest version 🚀 #201
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
macklinu
force-pushed
the
greenkeeper/husky-0.13.3
branch
from
31a58cc to
2f78bc6
Compare
Generated by 🚫 dangerJS |
Codecov Report
@@ Coverage Diff @@
## master #201 +/- ##
=====================================
Coverage 0% 0%
=====================================
Files 4 4
Lines 104 104
Branches 16 16
=====================================
Misses 104 104Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 0.13.3 of husky just got published.
The version 0.13.3 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of husky.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 34 commits .
4b5011e0.13.36b92bb8Commentsc6f8bb10.13.3-0a2da709Prefer nvm over Node global install652c7f0Update README.mdd05a7b3Update README.md0bb5798Fix tests7af95d3update failure message (#107)be435caUpdate CHANGELOG.md0c3df4a0.13.283f9a21Update .travis.yml4b89c52Fix checking fornvm(#101)971ab6dAdd pkg-ok76adbe9Fix package entry point (#104)7e5875dUpdate README.mdThere are 34 commits in total. 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 🌴