chore(deps): husky #367
Open
chore(deps): husky #367
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
4 times, most recently
from
acf7cd2
to
75ed94e
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
2 times, most recently
from
7377cfb
to
40ba4e3
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
40ba4e3
to
2db2cbe
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
2db2cbe
to
c1dddad
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
c1dddad
to
e0336a1
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
e0336a1
to
6fd4c1c
Compare
renovate
bot
force-pushed
the
renovate/husky-9.x
branch
from
6fd4c1c
to
095d335
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:
2.7.0->9.1.7Release Notes
typicode/husky (husky)
v9.1.7Compare Source
v9.1.6Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
v9.1.3Compare Source
PATHv9.1.2Compare Source
v9.1.1Compare Source
v9.1.0Compare 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 shand. "$(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
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"from your hooks~/.huskyrcto.config/husky/init.shSupport 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=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.0.11Compare Source
v9.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
What's Changed
New Contributors
Full Changelog: typicode/husky@v9.0.1...v9.0.2
v9.0.1Compare 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 initAdding 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
echocommand.v8
v9
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.package.json{ "scripts": { - "prepare": "husky install" + "prepare": "husky" } }.husky/pre-commitv8.0.3Compare Source
v8.0.2Compare Source
v8.0.1Compare Source
v8.0.0Compare Source
What's Changed
Feats
husky -prefix to logged global error messages by @joshbalfour in https://github.com/typicode/husky/pull/1092PATHwhen command not found to improve debuggability$HUSKY=0Fixes
/usr/bin/env shinstead of direct path ofshby @skhaz in https://github.com/typicode/husky/pull/1051./husky.shby @hyperupcall in https://github.com/typicode/husky/pull/1104basename/dirnameto treat$0as an argument by @mataha in https://github.com/typicode/husky/pull/1132git.iolinks by @renbaoshuo in https://github.com/typicode/husky/pull/1136Docs
npx --no-installoption withnpx --noby @sibiraj-s in https://github.com/typicode/husky/pull/1070pnpminstallation by @MohamadKh75 in https://github.com/typicode/husky/pull/1139Chore
v7.0.4Compare Source
No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.
v7.0.3Compare Source
v7.0.2Compare Source
Fix pre-commit hook in WebStorm (#1023)
v7.0.1Compare Source
v7.0.0Compare Source
.husky/directory structure..husky/.gitignoreis now unnecessary and can be removed.husky-initCLIhusky-4-to-7CLIPlease help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!
v6.0.0Compare Source
After being in early access for Open Source projects and Sponsors for a limited time, I'm happy to announce that husky 6 is MIT again and can be freely used in commercial projects! 🎉
Many thanks to the Open Source projects and Companies which have switched to/sponsored the new husky during this period!
OSS is my full-time job, please consider sponsoring the development of husky on GitHub sponsors or Open Collective. Thank you!
Breaking change
husky inithas been moved to its own package (npx husky-init)Added
require('husky')Migrating from husky 4
Husky 6 contains breaking changes. If you're coming from v4,
npm install husky@6won't be enough.Recommended: see husky-4-to-6 CLI to automatically migrate your config. There's also a dedicated section in the docs.
If you're curious why config has changed, you may be interested in reading:
https://blog.typicode.com/husky-git-hooks-javascript-config/
Also Husky 6 follows official npm and Yarn best practices regarding autoinstall. It's recommended to use
preparescript instead (see usage in docs).v5.2.0Compare Source
setcommand to replace hooks (husky set .husky/pre-commit cmd)addcommand to append command (husky add .husky/pre-commit cmd)v5.1.3Compare Source
husky initwill detect Yarn v2 and initialize accordinglyv5.1.2Compare Source
preparescript instead ofpostinstall(#890)husky initusepreparescript (#890)v5.1.1Compare Source
v5.1.0Compare Source
husky initv5.0.9Compare Source
See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes
v5.0.8Compare Source
v5.0.7Compare Source
v5.0.6Compare Source
v5.0.5Compare Source
v5.0.4Compare Source
v5.0.3Compare Source
v5.0.2Compare Source
v5.0.1Compare Source
v5.0.0Compare Source
👉 See https://typicode.github.io/husky for breaking changes and new installation instructions.
Note about the license
Husky 5 is released under The Parity Public License.
It doesn't affect you if you're using husky in an Open Source project or if you're a sponsor. You're free to use it as usual and I hope you'll enjoy this new release ❤️
If you're using husky in a commercial project, you may want to consider becoming a sponsor to support the project. You can also try it for 30 days.
This is only for a limited time, husky will be MIT again later.
Migrating
Important Husky v5 brings a lot of improvements but is also very different from v4. Git hooks won't work if you only upgrade husky dependency, existing config needs to be migrated too.
The best way to switch to v5 is to follow the new installation instructions and migrate existing hooks command using
husky add.v4.3.8Compare Source
Cannot read property 'toString' of nullv4.3.7Compare Source
v4.3.6Compare Source
prepare-commit-msgon windows #737v4.3.5Compare Source
v4.3.4Compare Source
INIT_CWDenvironment variablev4.3.3Compare Source
v4.3.2Compare Source
v4.3.1Compare Source
v4.3.0Compare Source
.cjsconfig file support #754v4.2.5Compare Source
v4.2.4Compare Source
cnpmpackage manager #687shto run scripts and avoid inconsistencies #707v4.2.3Compare Source
husky.config.jsnot.huskyrc.config.js#669v4.2.2Compare Source
.husky.jsand.husky.config.jsupdate,pre/post-receivehooksv4.2.1Compare Source
v4.2.0Compare Source
<2.13.0v4.1.0Compare Source
v4.0.10Compare Source
v4.0.9Compare Source
v4.0.8Compare Source
v4.0.7Compare Source
winpty(#634)v4.0.6Compare Source
v4.0.5Compare Source
v4.0.4Compare Source
.eslintrc.js(#627)v4.0.3Compare Source
v4.0.2Compare Source
v4.0.1Compare Source
v4.0.0Compare Source
Yarn v2new Plug'n'Play feature (thanks to @arcanis)CygwinandCmdr)dependenciesand simplify codeNode 10+Thanks to all contributors and everyone who is supporting Husky on Open Collective, GitHub sponsors and Patreon!
v3.1.0Compare Source
pre-merge-commithook (#605)v3.0.9Compare Source
is-ciwithci-info#579v3.0.8Compare Source
GIT_DIRenvironment variable when hooks are runv3.0.7Compare Source
Debug: display husky version and created at
v3.0.6Compare Source
Debug: improve messages
v3.0.5Compare Source
Fix: prevent
postinstallfrom failing on windows https://github.com/typicode/husky/pull/573v3.0.4Compare Source
Fix: skip install earlier when
HUSKY_SKIP_INSTALL=1(https://github.com/typicode/husky/issues/563)v3.0.3Compare Source
Fix: prevent old hooks (husky
< 1.0) to be run if new ones are defined (husky>= 1.0) https://github.com/typicode/husky/issues/556v3.0.2Compare Source
v3.0.1Compare Source
v3.0.0Compare Source
>= 2.13.2. If you're already using huskyv2and don't use an old version of Git, you can safely upgrade.Configuration
📅 Schedule: Branch creation - "after 3am,before 9am" in timezone America/Los_Angeles, 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.