fix(deps): update dependency husky to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
husky	^8.0.3 → ^9.0.0

---

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

What's Changed

• fix: add husky label to deprecated warning by @​smackfu in #​1538

New Contributors

• @​smackfu made their first contribution in #​1538

Full Changelog: typicode/husky@v9.1.6...v9.1.7

v9.1.6

Compare Source

What's Changed

• Fix issue where example pre-commit file is generated incorrectly by @​dexmlee in #​1519

New Contributors

• @​OlegKipchatov made their first contribution in #​1495
• @​Byron2016 made their first contribution in #​1499
• @​dexmlee made their first contribution in #​1519

Full Changelog: typicode/husky@v9.1.5...v9.1.6

v9.1.5

Compare Source

What's Changed

• fixes #​1494, support pre-merge-commit hook by @​RainMeoCat in #​1497

New Contributors

• @​RainMeoCat made their first contribution in #​1497

Full Changelog: typicode/husky@v9.1.4...v9.1.5

v9.1.4

Compare Source

• Improve deprecation notice

v9.1.3

Compare Source

• fix: better handle space in PATH

v9.1.2

Compare Source

Show a message instead of automatically removing deprecated code.

This only concerns projects that still have the following code in their hooks:

- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh"  # <- This is deprecated, remove it

### Rest of your hook code

Hooks with these lines will fail in v10.0.0

v9.1.1

Compare Source

Super saiyan god dog! It's over 9.0.0!

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

• #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" are deprecated. husky command will automatically remove them, no action required.
• If you're having code in ~/.huskyrc please move it to .config/husky/init.sh

Support for these will be removed in v10.

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 😉

v9.1.0

Compare Source

v9.0.11

Compare Source

• chore: update package-lock.json by @​btea in #​1383
• fix: export HUSKY=0 in init (fixes #​1393) by @​typicode in #​1395

v9.0.10

Compare Source

• fix: rename index.d.ts to index.d.mts by @​mrkjdy in #​1379

v9.0.9

Compare Source

• refactor: rename files by @​typicode in #​1378

v9.0.8

Compare Source

• docs: update index.md by @​khaledYS in #​1369
• Fix tab detection on install command by @​glensc in #​1376
• refactor: reduce file size by @​typicode in #​1377

v9.0.7

Compare Source

• fix: typo and source ~/.huskyrc correctly (compatibility with v8)
• docs: fix example by @​typicode in #​1363

v9.0.6

Compare Source

• docs: add favicon by @​rakleed in #​1354
• chore: apply editorconfig to code only by @​typicode in #​1355
• docs: update install script to mjs and fix CI checks by @​starnayuta in #​1357
• Fix unbound variable by @​typicode in #​1359

v9.0.5

Compare Source

• docs: update path to startup files by @​ManuelRauber in #​1350
• fix: init error by @​typicode in #​1353

v9.0.4

Compare Source

• fix: init create dir before by @​typicode in #​1348
• refactor: simplify by @​typicode in #​1349
• fix: init not working on pnpm #​1334 by @​rozbo in #​1347

v9.0.3

Compare Source

• docs: fix link by @​typicode in #​1340
• chore: fix links in issue template by @​julien-f in #​1341
• fix: add scripts field if not present by @​chalkygames123 in #​1338
• docs: changelog link by @​typicode in #​1343
• fix: insert final newline by @​chalkygames123 in #​1339
• fix: fix git hooks path on windows by @​rozbo in #​1346

v9.0.2

Compare Source

• fix: exit code by @​gergelypap in #​1336
• docs: typo by @​chalkygames123 in #​1337

v9.0.1

Compare Source

Kicking off the year with an exciting update!

Note: install using husky@latest to get the bug fixes that were released after.

Introducing husky init

v8

npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"

v9

Adding husky to a project is now easier than ever. It's just a single line that does the same as above. No need to read the docs to get started anymore.

npx husky init

Adding a New Hook

v8

npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows

v9

Adding a hook is as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command. For example, on Linux/macOS:

echo "npm test" > .husky/pre-commit

Further Size Reduction

v8 was already the most compact Git hooks manager at approximately 6kB.

v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

More to Come

Additional features are in the pipeline for v9. Stay tuned 🙌

Other Changes

• Enhanced security with CI and npm --provenance for safer publishing.
• Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
• Fixed permission issue for Windows-created hooks; they no longer need to be executable.
• Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
• Modified behavior when .git is missing; it now triggers a warning instead of failure.
• Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
• Updated the Husky API for module usage.
• Transitioned to ESM for module usage.
• Dropped support for Node 14 and 16.
• Revamped docs.

How to Migrate

v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

Here are the steps to migrate:

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test 

Note: sh will be used to run hooks, even if a shebang is set.

If you were using husky as a module:

- const husky = require('husky')
- // ...
+ import husky from 'husky'
+ console.log(husky())

---

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.

[sweep-nightly]

Apply Sweep Rules to your PR?

• Apply: All new business logic should have corresponding unit tests.
• Apply: Refactor large functions to be more modular.
• Apply: Add docstrings to all functions and file headers.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

📝 Walkthrough

Walkthrough

The change involves updating the version of the husky package in the package.json file from ^8.0.3 to ^9.0.0. This upgrade signifies a transition to a newer major version, which may introduce new features, improvements, or breaking changes. No other dependencies or configurations within the package.json file have been altered.

Changes

File	Change Summary
package.json	Updated husky version from ^8.0.3 to ^9.0.0

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Husky

    User->>Husky: Install husky@^9.0.0
    Husky-->>User: Installation complete

Loading

Poem

🐰 In the garden where I hop and play,
A new husky version brightens my day!
With features anew, oh what a delight,
I'll dance through the code, all day and night!
So let’s celebrate, with a joyful cheer,
For updates like this bring us all near! 🌼

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b5dbe3e and ac7bf79.

Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing (1)

• package.json (1 hunks)

Additional comments not posted (1)

package.json (1)

14-14: Approve the version update of husky.

The change from "husky": "^8.0.3" to "husky": "^9.0.0" in the dependencies section is correctly implemented. This update to a newer major version may introduce significant improvements and potentially some breaking changes.

Given the major version update and the deprecated features mentioned in the PR summary, it's crucial to verify the integration of the new husky version with the existing project configurations and workflows. Consider running tests and checking the project's hook scripts to ensure they align with the new husky version's requirements and functionalities.