This repository has been archived by the owner on Jan 23, 2022. It is now read-only.
chore(deps): update dependency husky to v6 - autoclosed #66
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
->6.0.0
Release Notes
typicode/husky
v6.0.0
Compare 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 init
has 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@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).v5.2.0
Compare Source
set
command to replace hooks (husky set .husky/pre-commit cmd
)add
command to append command (husky add .husky/pre-commit cmd
)v5.1.3
Compare Source
husky init
will detect Yarn v2 and initialize accordinglyv5.1.2
Compare Source
prepare
script instead ofpostinstall
(#890)husky init
useprepare
script (#890)v5.1.1
Compare Source
v5.1.0
Compare Source
husky init
v5.0.9
Compare Source
See https://github.com/typicode/husky/releases/tag/v5.0.0 for v5 release notes
v5.0.8
Compare Source
v5.0.7
Compare Source
v5.0.6
Compare Source
v5.0.5
Compare Source
v5.0.4
Compare Source
v5.0.3
Compare Source
v5.0.2
Compare Source
v5.0.1
Compare Source
v5.0.0
Compare 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.8
Compare Source
Cannot read property 'toString' of null
v4.3.7
Compare Source
v4.3.6
Compare Source
prepare-commit-msg
on windows #737v4.3.5
Compare Source
v4.3.4
Compare Source
INIT_CWD
environment variablev4.3.3
Compare Source
v4.3.2
Compare Source
v4.3.1
Compare Source
v4.3.0
Compare Source
.cjs
config file support #754v4.2.5
Compare Source
v4.2.4
Compare Source
cnpm
package manager #687sh
to run scripts and avoid inconsistencies #707v4.2.3
Compare Source
husky.config.js
not.huskyrc.config.js
#669v4.2.2
Compare Source
.husky.js
and.husky.config.js
update
,pre/post-receive
hooksv4.2.1
Compare Source
v4.2.0
Compare Source
<2.13.0
v4.1.0
Compare Source
v4.0.10
Compare Source
v4.0.9
Compare Source
v4.0.8
Compare Source
v4.0.7
Compare Source
winpty
(#634)v4.0.6
Compare Source
v4.0.5
Compare Source
v4.0.4
Compare Source
.eslintrc.js
(#627)v4.0.3
Compare Source
v4.0.2
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
Yarn v2
new Plug'n'Play feature (thanks to @arcanis)Cygwin
andCmdr
)dependencies
and simplify codeNode 10+
Thanks to all contributors and everyone who is supporting Husky on Open Collective, GitHub sponsors and Patreon!
v3.1.0
Compare Source
pre-merge-commit
hook (#605)v3.0.9
Compare Source
is-ci
withci-info
#579v3.0.8
Compare Source
GIT_DIR
environment variable when hooks are runv3.0.7
Compare Source
Debug: display husky version and created at
v3.0.6
Compare Source
Debug: improve messages
v3.0.5
Compare Source
Fix: prevent
postinstall
from failing on windows typicode/husky#573v3.0.4
Compare Source
Fix: skip install earlier when
HUSKY_SKIP_INSTALL=1
(typicode/husky#563)v3.0.3
Compare Source
Fix: prevent old hooks (husky
< 1.0
) to be run if new ones are defined (husky>= 1.0
) typicode/husky#556v3.0.2
Compare Source
v3.0.1
Compare Source
v3.0.0
Compare Source
>= 2.13.2
. If you're already using huskyv2
and don't use an old version of Git, you can safely upgrade.Configuration
📅 Schedule: 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 WhiteSource Renovate. View repository job log here.