chore(deps): update dependency husky to v4.3.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
husky (source)	4.2.1 -> 4.3.8

---

Release Notes

typicode/husky

v4.3.8

Compare Source

• Fix Cannot read property 'toString' of null
• Improve error messages

v4.3.7

Compare Source

• Fix: upgrade find-versions to 4.0.0 https://github.com/typicode/husky/pull/837

v4.3.6

Compare Source

• Fix prepare-commit-msg on windows #​737

v4.3.5

Compare Source

• Rollback and do not throw error if husky install fails

v4.3.4

Compare Source

• Throw error if husky install fails
• Add workaround for npm 7 currently missing INIT_CWD environment variable

v4.3.3

Compare Source

v4.3.2

Compare Source

v4.3.1

Compare Source

v4.3.0

Compare Source

• Add .cjs config file support #​754

v4.2.5

Compare Source

• Fix wrong error message #​709
• Update dependencies #​710

v4.2.4

Compare Source

• When Node version is unsupported, log actual version in addition to the error message #​701
• Fix: support cnpm package manager #​687
• Fix: always use sh to run scripts and avoid inconsistencies #​707
• Fix: don't throw error if files are already removed during uninstall #​708

v4.2.3

Compare Source

• Fix: check for husky.config.js not .huskyrc.config.js #​669

v4.2.2

Compare Source

• Fix #​662 disable fast-skip heuristic for .husky.js and .husky.config.js
• Fix do not install update, pre/post-receive hooks

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.