Bump husky from 3.0.5 to 6.0.0

[dependabot]

Bumps husky from 3.0.5 to 6.0.0.

Release notes

Sourced from husky's releases.

v6.0.0

After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉

Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!

OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!

Breaking change

• husky init has been moved to its own package (npx husky-init)

Added

• Programmatically use husky: require('husky')
• TypeScript definitions

Migrating from husky 4

Husky 6 contains breaking changes. If you're coming from v4, npm install husky@6 won't be enough.

Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.

If you're curious why config has changed, you may be interested in reading: https://blog.typicode.com/husky-git-hooks-javascript-config/

Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use prepare script instead (see usage in docs).

v5.2.0

• Add set command to replace hooks (husky set .husky/pre-commit cmd)
• Update add command to append command (husky add .husky/pre-commit cmd)
• Improve error messages

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)

... (truncated)

Commits

• cb4e3b9 v6.0.0
• db0a35c update
• 3bcbbd5 chore: update .gitignore
• 554ced9 v6.0.0
• ee1b299 update (#916)
• d022b2b style: formatting
• 57602ca docs: update how it works
• 6e19b1a style: img size
• 5a09e91 style: companies
• 5ee1f24 style: formatting
• 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

[gitpod-io]

[jywarren]

@dependabot rebase