-
Notifications
You must be signed in to change notification settings - Fork 626
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): update dependency husky to v9 #844
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
February 1, 2024 23:39
599b7ce
to
77a7240
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
February 4, 2024 18:36
fb897f3
to
6c8ff79
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
February 17, 2024 00:45
6c8ff79
to
b30fd1c
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
July 21, 2024 13:21
9cee7f5
to
711fd86
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
August 1, 2024 15:30
6b27854
to
a075522
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
August 23, 2024 14:11
a075522
to
90961dc
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
September 14, 2024 22:32
90961dc
to
1460dbd
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
November 4, 2024 05:50
7e16bf0
to
86405cc
Compare
Edited/Blocked NotificationRenovate 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. |
intcreator
force-pushed
the
renovate/husky-9.x
branch
from
November 4, 2024 21:52
930f412
to
15273ba
Compare
intcreator
reviewed
Nov 4, 2024
intcreator
reviewed
Nov 4, 2024
intcreator
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
November 7, 2024 20:11
e484311
to
f136414
Compare
intcreator
force-pushed
the
renovate/husky-9.x
branch
from
November 12, 2024 00:58
f136414
to
40f8975
Compare
sheerlox
approved these changes
Nov 12, 2024
🎉 This PR is included in version 3.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
intcreator
pushed a commit
that referenced
this pull request
Nov 12, 2024
## [3.2.0](v3.1.9...v3.2.0) (2024-11-12) ### ✨ Features * add support for Node v22 ([#914](#914)) ([9147b20](9147b20)) ### ⚙️ Continuous Integrations * **action:** update actions/checkout action to v4.2.2 ([#880](#880)) ([293f54a](293f54a)) * **action:** update actions/checkout digest to 11bd719 ([#879](#879)) ([0287c69](0287c69)) * **action:** update actions/setup-node digest to 39370e3 ([#889](#889)) ([0f7a3aa](0f7a3aa)) * **action:** update actions/upload-artifact action to v4.4.3 ([#878](#878)) ([226ad5b](226ad5b)) * **action:** update step-security/harden-runner action to v2.10.1 ([#882](#882)) ([b09438e](b09438e)) ### ♻️ Chores * **deps:** lock file maintenance ([ad613cb](ad613cb)) * **deps:** update dependency [@fast-check](https://github.com/fast-check)/jest to v2.0.3 ([2d00739](2d00739)) * **deps:** update dependency [@semantic-release](https://github.com/semantic-release)/github to v11.0.1 ([a17bbdd](a17bbdd)) * **deps:** update dependency [@types](https://github.com/types)/node to v20.17.6 ([4509c4d](4509c4d)) * **deps:** update dependency husky to v9 ([#844](#844)) ([9ea2216](9ea2216))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.0.3
->9.1.6
Release Notes
typicode/husky (husky)
v9.1.6
Compare Source
v9.1.5
Compare Source
v9.1.4
Compare Source
v9.1.3
Compare Source
PATH
v9.1.2
Compare Source
v9.1.1
Compare Source
v9.1.0
Compare Source
Super saiyan
goddog! 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 🐺⚡️
A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.
For more advanced use cases, see lint-staged.
Fixes
bunx husky init
commandDeprecations
#!/usr/bin/env sh
and. "$(dirname -- "$0")/_/husky.sh"
from your hooks~/.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
~/.huskyrc
correctly (compatibility with v8)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
v9
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
v9
Further Size Reduction
v8
was already the most compact Git hooks manager at approximately6kB
.v9
takes this a step further, reducing the size to just3kB
, 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
--provenance
for safer publishing.$XDG_CONFIG_HOME
support. Move~/.huskyrc
to~/.config/husky/init.sh
for centralized configuration.husky install
. Usehusky
orhusky some/dir
for the same functionality (deprecation notice to be added)..git
is missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1
withHUSKY=2
for debugging.ESM
for module usage.How to Migrate
v9
is backward compatible withv8
, allowing you to freely upgrade and migrate your hooks later.package.json
.husky/pre-commit
Configuration
📅 Schedule: Branch creation - "before 5am every weekday,every weekend" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.