This repository was archived by the owner on Oct 16, 2020. It is now read-only.
chore(deps): update dependency husky to v4 #659
Conversation
This file contains hidden or 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
Codecov Report
@@ Coverage Diff @@
## master #659 +/- ##
======================================
Coverage 82.4% 82.4%
======================================
Files 15 15
Lines 2126 2126
Branches 509 448 -61
======================================
Hits 1752 1752
Misses 364 364
Partials 10 10Continue to review full report at Codecov.
|
renovate
bot
force-pushed
the
renovate/husky-4.x
branch
9 times, most recently
from
905d0ed to
2fa1225
Compare
renovate
bot
force-pushed
the
renovate/husky-4.x
branch
3 times, most recently
from
7342b61 to
f246577
Compare
renovate
bot
force-pushed
the
renovate/husky-4.x
branch
from
f246577 to
33fb406
Compare
renovate
bot
force-pushed
the
renovate/husky-4.x
branch
2 times, most recently
from
5807f97 to
2ae04fa
Compare
renovate
bot
force-pushed
the
renovate/husky-4.x
branch
from
2ae04fa to
9a2679f
Compare
renovate
bot
force-pushed
the
renovate/husky-4.x
branch
from
9a2679f to
92669fe
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This PR contains the following updates:
Release Notes
typicode/husky
v4.2.5Compare Source
v4.2.4Compare Source
cnpmpackage manager #687shto run scripts and avoid inconsistencies #707v4.2.3Compare Source
husky.config.jsnot.huskyrc.config.js#669v4.2.2Compare Source
.husky.jsand.husky.config.jsupdate,pre/post-receivehooksv4.2.1Compare Source
v4.2.0Compare Source
<2.13.0v4.1.0Compare Source
v4.0.10Compare Source
v4.0.9Compare Source
v4.0.8Compare Source
v4.0.7Compare Source
winpty(#634)v4.0.6Compare Source
v4.0.5Compare Source
v4.0.4Compare Source
.eslintrc.js(#627)v4.0.3Compare Source
v4.0.2Compare Source
v4.0.1Compare Source
v4.0.0Compare Source
Yarn v2new Plug'n'Play feature (thanks to @arcanis)CygwinandCmdr)dependenciesand simplify codeNode 10+Thanks to all contributors and everyone who is supporting Husky on Open Collective, GitHub sponsors and Patreon!
v3.1.0Compare Source
pre-merge-commithook (#605)v3.0.9Compare Source
is-ciwithci-info#579v3.0.8Compare Source
GIT_DIRenvironment variable when hooks are runv3.0.7Compare Source
Debug: display husky version and created at
v3.0.6Compare Source
Debug: improve messages
v3.0.5Compare Source
Fix: prevent
postinstallfrom failing on windows #573v3.0.4Compare Source
Fix: skip install earlier when
HUSKY_SKIP_INSTALL=1(#563)v3.0.3Compare Source
Fix: prevent old hooks (husky
< 1.0) to be run if new ones are defined (husky>= 1.0) #556v3.0.2Compare Source
v3.0.1Compare Source
v3.0.0Compare Source
>= 2.13.2. If you're already using huskyv2and don't use an old version of Git, you can safely upgrade.v2.7.0Compare Source
Due to issues with Git
< 2.13.2, this version is a rollback and is the same as huskyv2.4.1. Changes introduced inv2.5.0andv2.6.0will be published inv3.0.0.v2.6.0Compare Source
HUSKY_USE_YARNsetting to use Yarn to run Husky<= 8.6.0Deprecated
v2.5.0Compare Source
CWDin debug messagesDeprecated
v2.4.1Compare Source
v2.4.0Compare Source
HUSKY_SKIP_HOOKSto skip all hooksv2.3.0Compare Source
HUSKY_DEBUG=1effective likeHUSKY_DEBUG=truerun-node/run-noderather than.bin/run-nodev2.2.0Compare Source
v2.1.0Compare Source
.rather thansourcev2.0.0Compare Source
Node 6supportv1.3.1Compare Source
is-ciand support more CIs1.3.0change related tostdindue to a bug on Windowsv1.3.0Compare Source
stdinif hook is running in a terminalv1.2.1Compare Source
v1.2.0Compare Source
v1.1.4Compare Source
execadependencyv1.1.3Compare Source
package.jsondoesn't existv1.1.2Compare Source
v1.1.1Compare Source
HUSKY_SKIP_INSTALLvalue first before checking if.gitexistsv1.1.0Compare Source
.git/hooksif it doesn't existv1.0.1Compare Source
husky-upgradechanges (#362, #360, #359)v1.0.0Compare Source
After a year of pre-releases and a complete rewrite, this marks the first stable release of husky 🐶🎉.
Notable changes
Below you'll find consolidated changes since
0.14.3. There's no change in code between1.0.0-rc.15and1.0.0.Hooks
sendemail-validatehookConfig
scriptsfield tohuskyfieldpre-commitrather thanprecommit).huskyrcconfigPackage managers
Environment variables
HUSKY_SKIP_INSTALLenvironment variable for skipping git hooks installationHUSKY_GIT_STDINenvironment variable forpre-push,pre-receive,post-receiveandpost-rewriteto access arguments passed by Git via stdinGIT_PARAMStoHUSKY_GIT_PARAMSMessages
--no-verifymessage more accurate and only show it for hooks that can be skippedUpgrade
husky-upgradecommand to automatically migrate hooks inpackage.jsonscriptsOther
Node 4supportnvmsupport (see Node version management in docs)Credits
Huge thanks to all the Contributors and Patreon Supporters! 🙏
v0.14.3Compare Source
PATH#150v0.14.2Compare Source
HOMEv0.14.1Compare Source
nvmwas installed with BrewRenovate configuration
📅 Schedule: "on the 1st through 7th day of the month" in timezone America/Los_Angeles.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.