-
Notifications
You must be signed in to change notification settings - Fork 5
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 #666
Open
descope
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
descope
bot
force-pushed
the
renovate/husky-9.x
branch
from
December 10, 2024 13:54
534fdfd
to
deccd65
Compare
Your Vercel team allenzhou is not permitted to deploy from this git repository. Contact an administrator to add github organization descope as a Protected Git Scope in allenzhou on Vercel. Once added, commit again to see your changes. Learn more: https://vercel.com/docs/security/protected-git-scopes |
descope
bot
force-pushed
the
renovate/husky-9.x
branch
from
December 12, 2024 11:40
deccd65
to
bc0919d
Compare
descope
bot
force-pushed
the
renovate/husky-9.x
branch
from
December 14, 2024 14:15
bc0919d
to
59e8f22
Compare
descope
bot
force-pushed
the
renovate/husky-9.x
branch
from
December 25, 2024 22:06
59e8f22
to
63062c6
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.7
Release Notes
typicode/husky (husky)
v9.1.7
Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.6...v9.1.7
v9.1.6
Compare Source
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.1.5...v9.1.6
v9.1.5
Compare Source
What's Changed
pre-merge-commit
hook by @RainMeoCat in https://github.com/typicode/husky/pull/1497New Contributors
Full Changelog: typicode/husky@v9.1.4...v9.1.5
v9.1.4
Compare Source
v9.1.3
Compare Source
PATH
v9.1.2
Compare 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.0
v9.1.1
Compare Source
Super saiyan
goddog! It's over 9.0.0!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"
are deprecated.husky
command will automatically remove them, no action required.~/.huskyrc
please move it to.config/husky/init.sh
Support 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=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.1.0
Compare Source
v9.0.11
Compare Source
package-lock.json
by @btea in https://github.com/typicode/husky/pull/1383export HUSKY=0
in init (fixes #1393) by @typicode in https://github.com/typicode/husky/pull/1395v9.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
v9.0.1
Compare Source
Kicking off the year with an exciting update!
Note: install using
husky@latest
to get the bug fixes that were released after.Introducing
husky init
v8
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
echo
command. For example, on Linux/macOS: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.Here are the steps to migrate:
package.json
.husky/pre-commit
Note:
sh
will be used to run hooks, even if a shebang is set.If you were using
husky
as a module:Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" in timezone Asia/Jerusalem, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled because a matching PR was automerged previously.
♻ 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 has been generated by Renovate Bot.