-
Notifications
You must be signed in to change notification settings - Fork 46
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 - autoclosed #726
Closed
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #726 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 2 2
Lines 7 7
======================================
Misses 7 7 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
February 5, 2024 09:10
efe5193
to
ceb9103
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
5 times, most recently
from
February 19, 2024 09:47
beea5b9
to
00321e9
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
5 times, most recently
from
March 8, 2024 15:23
4b676af
to
7b46194
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
March 11, 2024 09:20
9eb9ebc
to
7664f05
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
March 25, 2024 00:05
1812901
to
f185487
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
April 1, 2024 07:05
ac881e6
to
4664202
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
April 8, 2024 11:34
97c1caf
to
e81b4f0
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
April 15, 2024 00:47
e81b4f0
to
d7b34c4
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
5 times, most recently
from
July 29, 2024 16:28
fe2033f
to
3f66ecc
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
August 12, 2024 07:36
3d73139
to
5457cec
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
August 26, 2024 07:18
cadabba
to
1d33bc7
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
September 2, 2024 08:25
1d33bc7
to
9352339
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
September 12, 2024 01:25
8cc75f9
to
43f5127
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
September 23, 2024 09:59
e56bc45
to
fa42958
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
October 7, 2024 06:21
89ba9b6
to
f0e2289
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
October 21, 2024 09:03
0a8d2fb
to
c00ff26
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
October 22, 2024 23:21
c00ff26
to
6be80de
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
November 18, 2024 09:54
0098481
to
f1a8388
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
November 25, 2024 10:05
6568a74
to
63742d7
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
December 2, 2024 06:51
63742d7
to
d2b968a
Compare
renovate
bot
changed the title
chore(deps): update dependency husky to v9
chore(deps): update dependency husky to v9 - autoclosed
Dec 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
7.0.4
->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
Configuration
📅 Schedule: Branch creation - "* 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.
This PR was generated by Mend Renovate. View the repository job log.