chore(deps-dev): bump husky from 1.1.4 to 5.1.0

[dependabot-preview[bot]]

Bumps husky from 1.1.4 to 5.1.0.

Release notes

Sourced from husky's releases.

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.

v5.0.0-alpha.5

No release notes provided.

v4.3.8

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

v4.3.7

• Fix: upgrade find-versions to 4.0.0 typicode/husky#837

v4.3.6

• Fix prepare-commit-msg on windows #737

v4.3.5

... (truncated)

Commits

• 15a1a68 5.1.0
• c61ba5f feat(cli): add init
• 61977ad chore(test): use npm 7 --no option
• 52085ab chore: update package.json
• a8ac8c0 docs: npm requirement on Windows
• 7180418 docs: use --no instead of --no-install (deprecated) for npx 7
• c180976 chore: issue template
• 7bb2803 style: fix typo
• 4b880d0 docs: add badge link
• afef309 build(windows): fix prebuild script
• 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 will not automatically merge this PR because it includes an out-of-range update to a development dependency.

---

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 - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in the `.dependabot/config.yml` file in this repo: - Update frequency - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

[dependabot-preview[bot]]

Superseded by #357.