Upgrade husky: 4.3.8 → 6.0.0 (major)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳ ️ husky (4.3.8 → 6.0.0) · Repo · Changelog
Release Notes
6.0.0
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 init
has been moved to its own package (npx husky-init
)Added
- Programmatically use husky:
require('husky')
- TypeScript definitions
Migrating from husky 4
Husky 6 contains breaking changes. If you're coming from v4,
npm install husky@6
won'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
prepare
script instead (see usage in docs).
5.2.0
- Add
set
command to replace hooks (husky set .husky/pre-commit cmd
)- Update
add
command to append command (husky add .husky/pre-commit cmd
)- Improve error messages
5.1.3
- docs: add specific Yarn v2 install/uninstall instructions
- cli:
husky init
will detect Yarn v2 and initialize accordingly
5.1.2
5.1.1
- style(shell): add trailing newlines (#870)
- fix(init): update package.json postinstall
5.1.0
- Add
husky init
5.0.9
- fix(install): do not fail if not inside a Git directory (closes #851)
See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase
.
All Depfu comment commands
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu recreate
- Recreates this PR, overwriting any edits that you've made to it
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)