Skip to content

chore(deps): update dependency husky to v9#204

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/husky-9.x
Open

chore(deps): update dependency husky to v9#204
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/husky-9.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 6, 2024

This PR contains the following updates:

Package Change Age Confidence
husky 7.0.49.1.7 age confidence

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

What's Changed

New Contributors

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

v9.1.6

Compare Source

What's Changed

New Contributors

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

v9.1.5

Compare Source

What's Changed

New Contributors

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

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

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

v9.0.5

Compare Source

v9.0.4

Compare Source

v9.0.3

Compare Source

v9.0.2

Compare Source

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())

v8.0.3

Compare Source

  • fix: add git not installed message #​1208

v8.0.2

Compare Source

  • docs: remove deprecated npm set-script

v8.0.1

Compare Source

  • fix: use POSIX equality operator

v8.0.0

Compare Source

What's Changed

Feats
  • feat: add husky - prefix to logged global error messages by @​joshbalfour in #​1092
  • feat: show PATH when command not found to improve debuggability
  • feat: drop Node 12 support
  • feat: skip install if $HUSKY=0
Fixes
Docs
Chore

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/New_York, 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 from fe4ea11 to c2dc98f Compare May 6, 2024 09:18
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 6, 2024

⚠ 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: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: frontend-app-ora@0.1.0
npm error Found: react@17.0.2
npm error node_modules/react
npm error   react@"^17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @testing-library/react@15.0.6
npm error node_modules/@testing-library/react
npm error   dev @testing-library/react@"15.0.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-06T09_18_01_427Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T09_18_01_427Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from ff84b9b to 91560ce Compare May 13, 2024 12:21
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 5677cd5 to 1ee48a6 Compare May 27, 2024 11:14
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 3 times, most recently from 25c41c2 to 344d080 Compare June 10, 2024 12:47
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 3 times, most recently from 4cdcff2 to 0a2c44e Compare June 17, 2024 12:02
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 3 times, most recently from 0a153a6 to 7a13d58 Compare July 1, 2024 07:30
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 5 times, most recently from a5d9127 to 09e13fa Compare July 22, 2024 08:57
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 5 times, most recently from c0ae4dc to ac53aa1 Compare July 29, 2024 16:11
@renovate renovate Bot force-pushed the renovate/husky-9.x branch from ac53aa1 to dad9586 Compare August 5, 2024 08:44
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 4c7fd03 to 8537115 Compare August 19, 2024 06:26
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 439262f to ea656a8 Compare August 20, 2024 12:51
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 5 times, most recently from 6e7edc1 to b3838c7 Compare November 7, 2024 16:23
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from d5165e4 to 1993539 Compare November 18, 2024 10:22
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from a052c5c to afcd6e9 Compare November 25, 2024 10:44
@renovate renovate Bot force-pushed the renovate/husky-9.x branch from afcd6e9 to 3b3aa25 Compare December 2, 2024 08:10
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 78d82a9 to 6c09a08 Compare December 16, 2024 09:47
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from d661e3a to f8858ba Compare December 23, 2024 10:21
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from f62b412 to 3cc3a30 Compare January 6, 2025 10:20
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from c1811f4 to b064d70 Compare January 20, 2025 08:41
@renovate renovate Bot force-pushed the renovate/husky-9.x branch from b064d70 to 31e1a3e Compare January 20, 2025 13:32
@renovate renovate Bot force-pushed the renovate/husky-9.x branch from 31e1a3e to 168971d Compare February 10, 2025 09:14
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from c6df5f1 to b1485a7 Compare February 24, 2025 11:10
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 4 times, most recently from 57824fe to d3d3a25 Compare March 3, 2025 15:24
@renovate renovate Bot force-pushed the renovate/husky-9.x branch 2 times, most recently from 988d275 to 1420690 Compare March 10, 2025 14:29
@renovate renovate Bot force-pushed the renovate/husky-9.x branch from 1420690 to 92cdfb9 Compare March 17, 2025 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants