-
Notifications
You must be signed in to change notification settings - Fork 1
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 #272
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/husky-9.x
base: main
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
added
dependencies
Pull requests that update a dependency file
MAJOR
labels
Jan 25, 2024
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
6 times, most recently
from
January 29, 2024 17:34
9f8ff5a
to
10065e2
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
February 1, 2024 19:12
58cf6c6
to
15f138a
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
February 14, 2024 00:43
15f138a
to
bf6240d
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
February 24, 2024 00:58
bf6240d
to
e9e7e5f
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
March 20, 2024 22:18
cd44502
to
462d096
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
April 29, 2024 21:22
ab10f76
to
e833737
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
May 24, 2024 18:33
e833737
to
a32138f
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
June 5, 2024 23:10
667f15d
to
36fe5b7
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
July 18, 2024 15:52
f98c1e2
to
3c506f7
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
July 25, 2024 15:35
f48ce63
to
644f114
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
July 29, 2024 15:19
0d9bc46
to
570bebd
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
August 20, 2024 20:02
ac64915
to
2c348eb
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
September 3, 2024 09:48
2c348eb
to
4428fab
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
September 16, 2024 19:34
578869f
to
7b3247d
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
3 times, most recently
from
October 3, 2024 16:59
4f48803
to
5f46f0c
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
October 10, 2024 17:12
5f46f0c
to
eb18ec3
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
October 22, 2024 19:15
eb18ec3
to
16b0a42
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
November 18, 2024 17:24
16b0a42
to
6e5351e
Compare
renovate
bot
changed the title
chore(deps): update dependency husky to v9
chore(deps): update dependency husky to v9 - autoclosed
Dec 8, 2024
renovate
bot
changed the title
chore(deps): update dependency husky to v9 - autoclosed
chore(deps): update dependency husky to v9
Dec 8, 2024
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.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
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.