-
Notifications
You must be signed in to change notification settings - Fork 9
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 #37
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/husky-9.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
6 times, most recently
from
January 29, 2024 15:20
6a4c595
to
dea9c18
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
February 4, 2024 19:48
ac8cb03
to
84bdd10
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
February 18, 2024 19:23
53c10f0
to
2beb2f5
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
February 25, 2024 19:42
045545b
to
f97eb5b
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 4, 2024 13:10
7e25cc1
to
1b16789
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 10, 2024 21:05
830f609
to
c1d6619
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 24, 2024 18:18
33ae05b
to
12668a9
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 31, 2024 19:21
1677e4d
to
27c989b
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
April 14, 2024 18:07
d5f4aeb
to
40e67db
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
April 22, 2024 12:14
0a6fceb
to
b5d4df5
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
April 29, 2024 01:39
657f6f5
to
36f1199
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
October 20, 2024 18:25
d1250c2
to
094a997
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
November 3, 2024 18:51
a7c4df2
to
13518da
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
November 10, 2024 18:57
13518da
to
6817098
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
November 24, 2024 18:23
45bf61c
to
498ff07
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
5 times, most recently
from
December 2, 2024 12:56
a5bb60d
to
46224f1
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
December 15, 2024 18:14
5cc0db3
to
5e524d7
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
6 times, most recently
from
December 22, 2024 18:49
4d833ef
to
06ae871
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
December 30, 2024 03:31
dced7c7
to
a72fc9a
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
January 6, 2025 14:33
2799884
to
db8b852
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
January 13, 2025 15:48
db8b852
to
099aeea
Compare
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:
4.3.8
->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
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
v8.0.3
Compare Source
v8.0.2
Compare Source
v8.0.1
Compare Source
v8.0.0
Compare Source
What's Changed
Feats
husky -
prefix to logged global error messages by @joshbalfour in https://github.com/typicode/husky/pull/1092PATH
when command not found to improve debuggability$HUSKY=0
Fixes
/usr/bin/env sh
instead of direct path ofsh
by @skhaz in https://github.com/typicode/husky/pull/1051./husky.sh
by @hyperupcall in https://github.com/typicode/husky/pull/1104basename
/dirname
to treat$0
as an argument by @mataha in https://github.com/typicode/husky/pull/1132git.io
links by @renbaoshuo in https://github.com/typicode/husky/pull/1136Docs
npx --no-install
option withnpx --no
by @sibiraj-s in https://github.com/typicode/husky/pull/1070pnpm
installation by @MohamadKh75 in https://github.com/typicode/husky/pull/1139Chore
v7.0.4
Compare Source
No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.
v7.0.3
Compare Source
v7.0.2
Compare Source
Fix pre-commit hook in WebStorm (#1023)
v7.0.1
Compare Source
v7.0.0
Compare Source
.husky/
directory structure..husky/.gitignore
is now unnecessary and can be removed.husky-init
CLIhusky-4-to-7
CLIPlease help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!
v6.0.0
Compare Source
After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉
Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!
OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!
Breaking change
husky init
has been moved to its own package (npx husky-init
)Added
require('husky')
Migrating from husky 4
Husky 6 contains breaking changes. If you're coming from v4,
npm install husky@6
won't be enough.Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.
If you're curious why config has changed, you may be interested in reading:
https://blog.typicode.com/husky-git-hooks-javascript-config/
Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use
prepare
script instead (see usage in docs).v5.2.0
Compare Source
set
command to replace hooks (husky set .husky/pre-commit cmd
)add
command to append command (husky add .husky/pre-commit cmd
)v5.1.3
Compare Source
husky init
will detect Yarn v2 and initialize accordinglyv5.1.2
Compare Source
prepare
script instead ofpostinstall
(#890)husky init
useprepare
script (#890)v5.1.1
Compare Source
v5.1.0
Compare Source
husky init
v5.0.9
Compare Source
See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes
v5.0.8
Compare Source
v5.0.7
Compare Source
v5.0.6
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.3
Compare Source
v5.0.2
Compare Source
v5.0.1
Compare Source
v5.0.0
Compare Source
👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.
Note about the license
Husky 5 is released under The Parity Public License.
It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️
If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.
This is only for a limited time, husky will be MIT again later.
Migrating
Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.
The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using
husky add
.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.
This PR was generated by Mend Renovate. View the repository job log.