chore(dependencies): update dependency husky to v7

[renovate]

This PR contains the following updates:

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

---

Release Notes

typicode/husky

v7.0.4

Compare Source

No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

v7.0.3

Compare Source

v7.0.2

Compare Source

Fix pre-commit hook in WebStorm (#​1023)

v7.0.1

Compare Source

• Fix gracefully fail if Git command is not found #​1003 (same as in v6)

v7.0.0

Compare Source

• Improve .husky/ directory structure. .husky/.gitignore is now unnecessary and can be removed.
• Improve error output (shorter)
• Update husky-init CLI
• Update husky-4-to-7 CLI
• Drop Node 10 support

Please help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!

v6.0.0

Compare Source

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

Compare Source

• 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

Compare Source

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

v5.1.2

Compare Source

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

v5.1.1

Compare Source

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

v5.1.0

Compare Source

• Add husky init

v5.0.9

Compare Source

• 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

Compare Source

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

v5.0.7

Compare Source

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

v5.0.6

Compare Source

• Remove unused files

v5.0.5

Compare Source

• Fix custom directory support #​827

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

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

---

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 is behind base branch, 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, click this checkbox.

---

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.