Update dependency husky to v8 #86

renovate · 2023-09-02T21:30:26Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
husky (source)	`4.2.3` -> `8.0.3`

Release Notes

typicode/husky (husky)

`v8.0.3`

Compare Source

fix: add git not installed message #1208

`v8.0.2`

Compare Source

docs: remove deprecated npm set-script

`v8.0.1`

Compare Source

fix: use POSIX equality operator

`v8.0.0`

Compare Source

What's Changed

Feats

feat: add husky - prefix to logged global error messages by @joshbalfour in https://github.com/typicode/husky/pull/1092
feat: show PATH when command not found to improve debuggability
feat: drop Node 12 support
feat: skip install if $HUSKY=0

Fixes

fix: hook script use /usr/bin/env sh instead of direct path of sh by @skhaz in https://github.com/typicode/husky/pull/1051
fix: actually set 'husky_skip_init' as readonly in ./husky.sh by @hyperupcall in https://github.com/typicode/husky/pull/1104
fix: force basename/dirname to treat $0 as an argument by @mataha in https://github.com/typicode/husky/pull/1132
fix: remove git.io links by @renbaoshuo in https://github.com/typicode/husky/pull/1136

No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

`v7.0.3`

Compare Source

`v7.0.2`

Compare Source

Fix pre-commit hook in WebStorm (#1023)

`v7.0.1`

Compare Source

Fix gracefully fail if Git command is not found #1003 (same as in v6)

`v7.0.0`

Compare Source

Improve .husky/ directory structure. .husky/.gitignore is now unnecessary and can be removed.
Improve error output (shorter)
Update husky-init CLI
Update husky-4-to-7 CLI
Drop Node 10 support

Please help me develop and release OSS projects ❤️ on GitHub Sponsors or Open Collective. Thank you for your support!

`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

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).

`v5.2.0`

Compare Source

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

`v5.1.3`

Compare Source

docs: add specific Yarn v2 install/uninstall instructions
cli: husky init will detect Yarn v2 and initialize accordingly

`v5.1.2`

Compare Source

docs: recommend prepare script instead of postinstall (#890)
cli: husky init use prepare script (#890)

`v5.1.1`

Compare Source

style(shell): add trailing newlines (#870)
fix(init): update package.json postinstall

`v5.1.0`

Compare Source

Add husky init

`v5.0.9`

Compare Source

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

`v5.0.8`

Compare Source

fix(install): better handle Git <2.9 (#846) closes #844

`v5.0.7`

Compare Source

fix(shell): double quote params (#824)

`v5.0.6`

Compare Source

Remove unused files

`v5.0.5`

Compare Source

Fix custom directory support #827

`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

Fix Cannot read property 'toString' of null
Improve error messages

`v4.3.7`

Compare Source

Fix: upgrade find-versions to 4.0.0 https://github.com/typicode/husky/pull/837

`v4.3.6`

Compare Source

Fix prepare-commit-msg on windows #737

`v4.3.5`

Compare Source

Rollback and do not throw error if husky install fails

`v4.3.4`

Compare Source

Throw error if husky install fails
Add workaround for npm 7 currently missing INIT_CWD environment variable

`v4.3.3`

Compare Source

`v4.3.2`

Compare Source

`v4.3.1`

Compare Source

`v4.3.0`

Compare Source

Add .cjs config file support #754

`v4.2.5`

Compare Source

Fix wrong error message #709
Update dependencies #710

`v4.2.4`

Compare Source

When Node version is unsupported, log actual version in addition to the error message #701
Fix: support cnpm package manager #687
Fix: always use sh to run scripts and avoid inconsistencies #707
Fix: don't throw error if files are already removed during uninstall #708

Configuration

📅 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.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate · 2023-09-02T21:30:27Z

⚠ Artifact update problem

Renovate 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:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @rollup/plugin-node-resolve@15.2.1
npm ERR! Found: rollup@2.1.0
npm ERR! node_modules/rollup
npm ERR!   dev rollup@"2.1.0" from the root project
npm ERR!   peerOptional rollup@"^1.20.0||^2.0.0||^3.0.0" from @rollup/plugin-json@6.0.0
npm ERR!   node_modules/@rollup/plugin-json
npm ERR!     dev @rollup/plugin-json@"6.0.0" from the root project
npm ERR!   3 more (@rollup/pluginutils, rollup-plugin-commonjs, rollup-plugin-terser)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional rollup@"^2.78.0||^3.0.0" from @rollup/plugin-node-resolve@15.2.1
npm ERR! node_modules/@rollup/plugin-node-resolve
npm ERR!   dev @rollup/plugin-node-resolve@"15.2.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: rollup@3.28.1
npm ERR! node_modules/rollup
npm ERR!   peerOptional rollup@"^2.78.0||^3.0.0" from @rollup/plugin-node-resolve@15.2.1
npm ERR!   node_modules/@rollup/plugin-node-resolve
npm ERR!     dev @rollup/plugin-node-resolve@"15.2.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/e9e88f/25f05b/cache/others/npm/_logs/2023-09-02T21_30_17_087Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/e9e88f/25f05b/cache/others/npm/_logs/2023-09-02T21_30_17_087Z-debug-0.log

Update dependency husky to v8

a8a19f6

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency husky to v8 #86

Update dependency husky to v8 #86

renovate bot commented Sep 2, 2023 •

edited

renovate bot commented Sep 2, 2023

Update dependency husky to v8 #86

Are you sure you want to change the base?

Update dependency husky to v8 #86

Conversation

renovate bot commented Sep 2, 2023 • edited

Release Notes

What's Changed

Feats

Fixes

Docs

Chore

Breaking change

Added

Migrating from husky 4

Note about the license

Migrating

Configuration

renovate bot commented Sep 2, 2023

⚠ Artifact update problem

File name: package-lock.json

renovate bot commented Sep 2, 2023 •

edited