Update dependency husky to v9.1.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
husky	9.0.11 -> 9.1.7

---

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

• fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

• bunx husky init command
• Workaround for some hooks implementation on Windows 🤷

Deprecations

• Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
• Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

---

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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: superagent/yarn.lock

error SyntaxError: Invalid value type 2241:0 in /tmp/renovate/repos/github/dlminvestments/devops-insights-VM-1-Systems/superagent/yarn.lock
    at Parser.unexpected (/opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:64026:11)
    at Parser.parse (/opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:64154:16)
    at parse (/opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:64231:21)
    at module.exports.exports.default (/opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:63793:96)
    at Function.<anonymous> (/opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:3068:63)
    at Generator.next (<anonymous>)
    at step (/opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:310:30)
    at /opt/containerbase/tools/yarn-slim/1.22.22/22.11.0/node_modules/yarn/lib/cli.js:321:13