-
Notifications
You must be signed in to change notification settings - Fork 0
chore(deps): update dependency husky to v9 #55
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
Open
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/husky-9.x
base: dev
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 hidden or 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
570ff11 to
4564007
Compare
e259a88 to
136711d
Compare
2392037 to
eb96af1
Compare
eb96af1 to
a3ac43f
Compare
0ca9904 to
ac04c43
Compare
ac04c43 to
57711e6
Compare
57711e6 to
d99187f
Compare
d99187f to
3119451
Compare
3119451 to
54f04cc
Compare
54f04cc to
e2f05f9
Compare
e2f05f9 to
cdae875
Compare
cdae875 to
d6e1dcc
Compare
d6e1dcc to
3a1a54a
Compare
3a1a54a to
30672a2
Compare
30672a2 to
9381d62
Compare
9381d62 to
0ae0b55
Compare
0ae0b55 to
f661b51
Compare
f661b51 to
62fe1f7
Compare
62fe1f7 to
6bf9766
Compare
7ff92f1 to
948a98b
Compare
1dba56f to
666e78a
Compare
666e78a to
6acc4a7
Compare
6acc4a7 to
eaa0dde
Compare
eaa0dde to
b9c5ba8
Compare
65999a1 to
f524dba
Compare
f524dba to
2176b35
Compare
2176b35 to
19bf6bb
Compare
19bf6bb to
fb15e54
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:
8.0.3->9.1.7Release Notes
typicode/husky (husky)
v9.1.7Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.6...v9.1.7
v9.1.6Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.5...v9.1.6
v9.1.5Compare Source
What's Changed
pre-merge-commithook by @RainMeoCat in #1497New Contributors
Full Changelog: typicode/husky@v9.1.4...v9.1.5
v9.1.4Compare Source
v9.1.3Compare Source
PATHv9.1.2Compare Source
Show a message instead of automatically removing deprecated code.
This only concerns projects that still have the following code in their hooks:
Hooks with these lines will fail in
v10.0.0v9.1.1Compare Source
Super saiyan
goddog! It's over 9.0.0!What's new
You can now run package commands directly, no need for
npxor 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 initcommandDeprecations
#!/usr/bin/env shand. "$(dirname -- "$0")/_/husky.sh"are deprecated.huskycommand will automatically remove them, no action required.~/.huskyrcplease move it to.config/husky/init.shSupport for these will be removed in v10.
Friendly reminder
If Git hooks don't fit your workflow, you can disable Husky globally. Just add
export HUSKY=0to.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.1.0Compare Source
v9.0.11Compare Source
package-lock.jsonby @btea in #1383export HUSKY=0in init (fixes #1393) by @typicode in #1395v9.0.10Compare Source
v9.0.9Compare Source
v9.0.8Compare Source
v9.0.7Compare Source
~/.huskyrccorrectly (compatibility with v8)v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
v9.0.2Compare Source
v9.0.1Compare Source
Kicking off the year with an exciting update!
Note: install using
husky@latestto get the bug fixes that were released after.Introducing
husky initv8
v9
Adding husky to a project is now easier than ever. It's just a single line that does the same as above. No need to read the docs to get started anymore.
Adding a New Hook
v8
v9
Adding a hook is as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic
echocommand. For example, on Linux/macOS:Further Size Reduction
v8was already the most compact Git hooks manager at approximately6kB.v9takes 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
--provenancefor safer publishing.$XDG_CONFIG_HOMEsupport. Move~/.huskyrcto~/.config/husky/init.shfor centralized configuration.husky install. Usehuskyorhusky some/dirfor the same functionality (deprecation notice to be added)..gitis missing; it now triggers a warning instead of failure.HUSKY_DEBUG=1withHUSKY=2for debugging.ESMfor module usage.How to Migrate
v9is backward compatible withv8, allowing you to freely upgrade and migrate your hooks later.Here are the steps to migrate:
package.json{ "scripts": { - "prepare": "husky install" + "prepare": "husky" } }.husky/pre-commitNote:
shwill be used to run hooks, even if a shebang is set.If you were using
huskyas a module: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 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.