Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): 🔨 Upgrade dependency husky to v9 #291

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
husky 8.0.3 -> 9.1.7 age adoption passing confidence

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 😉

v9.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

v9.0.6

Compare Source

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

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

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8
npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows
v9
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.

package.json

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

.husky/pre-commit

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

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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/husky-9.x branch 10 times, most recently from 65024b0 to 4616afc Compare February 1, 2024 06:34
@renovate renovate bot force-pushed the renovate/husky-9.x branch 7 times, most recently from 5d548a5 to 135dd7d Compare February 5, 2024 22:47
@renovate renovate bot force-pushed the renovate/husky-9.x branch 4 times, most recently from 2479338 to 8fba843 Compare February 19, 2024 09:36
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 5494028 to a90f381 Compare March 1, 2024 07:22
@renovate renovate bot force-pushed the renovate/husky-9.x branch 6 times, most recently from 3ff9003 to 2f9d0a5 Compare March 10, 2024 19:32
@renovate renovate bot force-pushed the renovate/husky-9.x branch 4 times, most recently from fd3d672 to b3b36d6 Compare September 12, 2024 01:47
@renovate renovate bot force-pushed the renovate/husky-9.x branch 3 times, most recently from dab1c0c to ce8da2a Compare September 22, 2024 06:47
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 33ea61d to 87e8abf Compare September 27, 2024 09:17
@renovate renovate bot force-pushed the renovate/husky-9.x branch 4 times, most recently from b06da8d to 00fcc04 Compare October 15, 2024 19:47
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from a94b6ae to d936773 Compare October 26, 2024 12:40
@renovate renovate bot force-pushed the renovate/husky-9.x branch 4 times, most recently from bf734c8 to 36f6694 Compare November 4, 2024 07:17
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 1bd5140 to 8e3290f Compare November 11, 2024 10:09
@renovate renovate bot force-pushed the renovate/husky-9.x branch 3 times, most recently from 807bdc2 to 21f1c92 Compare November 22, 2024 21:48
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 7644ea7 to bca330e Compare November 26, 2024 15:34
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 324e3a9 to 942591b Compare December 9, 2024 11:22
@renovate renovate bot force-pushed the renovate/husky-9.x branch from 942591b to 0b80841 Compare December 10, 2024 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants