-
Notifications
You must be signed in to change notification settings - Fork 0
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 #86
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
from
February 3, 2024 15:47
a6f065e
to
f5585a9
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
February 17, 2024 18:10
f5585a9
to
e109b8e
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 2, 2024 16:32
37e0a71
to
34de039
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 23, 2024 12:14
1016eff
to
270c146
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
April 6, 2024 14:01
84c45b3
to
12e7d9c
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
April 13, 2024 16:50
12e7d9c
to
29f2f99
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
April 27, 2024 12:54
3fe1db4
to
077cfa9
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
May 4, 2024 15:20
077cfa9
to
3db6400
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
May 11, 2024 15:38
3db6400
to
a3a8ce2
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
June 8, 2024 15:02
5ac34b3
to
ae3150d
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
June 22, 2024 12:54
47c8150
to
4dcf8e5
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
July 13, 2024 15:08
40fb3fe
to
d083c6e
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
July 27, 2024 12:25
d083c6e
to
b4be671
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
August 10, 2024 15:07
6161a21
to
e24755b
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
August 17, 2024 15:34
8106d65
to
ce5ca17
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
August 24, 2024 15:30
ce5ca17
to
c2dd85e
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
September 7, 2024 16:59
1f6c139
to
e060b4c
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
September 14, 2024 14:01
b403438
to
1798102
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
September 28, 2024 15:35
9e68261
to
e3ec331
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
October 5, 2024 15:32
e3ec331
to
70172d5
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
October 26, 2024 15:53
70172d5
to
e8f9e7d
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
November 2, 2024 12:50
e8f9e7d
to
9d34b08
Compare
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:
^8.0.3
->^9.0.0
Release Notes
typicode/husky (husky)
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 - "after 8pm every weekend" in timezone Asia/Tokyo, 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.