chore(deps-dev): bump husky from 4.3.8 to 5.1.3

[dependabot]

Bumps husky from 4.3.8 to 5.1.3.

Release notes

Sourced from husky's releases.

v5.1.3

• docs: add specific Yarn v2 install/uninstall instructions
• cli: husky init will detect Yarn v2 and initialize accordingly

v5.1.2

• docs: recommend prepare script instead of postinstall (#890)
• cli: husky init use prepare script (#890)

v5.1.1

• style(shell): add trailing newlines (#870)
• fix(init): update package.json postinstall

v5.1.0

• Add husky init

v5.0.9

• fix(install): do not fail if not inside a Git directory (closes #851)

See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes

v5.0.8

• fix(install): better handle Git <2.9 (#846) closes #844

v5.0.7

• fix(shell): double quote params (#824)

v5.0.6

• Remove unused files

v5.0.5

• Fix custom directory support #827

v5.0.0

👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.

Note about the license

Husky 5 is released under The Parity Public License.

It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️

If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.

This is only for a limited time, husky will be MIT again later.

Migrating

Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.

The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using husky add.

... (truncated)

Commits

• 70e4ba9 5.1.3
• 1fc98e3 docs: add yarn v2 uninstall
• e831c97 docs: fix docs links
• 61e271b test: fix and refactor tests
• 4ff36dc docs: add yarn v2 install
• 77a7f03 test: fix yarn v1 test
• 4c52a12 fix(init): use postinstall for yarn v2
• 67f1c26 chore: update devDependencies
• 299bcf4 5.1.2
• 84be675 docs: prepare script instead of postinstall (#890)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually