This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
chore(deps): update dependency husky to v8 #260
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}
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: package-lock.json |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
4.2.3->8.0.3Release Notes
typicode/husky (husky)
v8.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 #707Configuration
📅 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 has been generated by Mend Renovate. View repository job log here.