next-typescript-tailwind-mdx-starter icon indicating copy to clipboard operation
next-typescript-tailwind-mdx-starter copied to clipboard

Published 20 hours ago • verified publisher icon joelhooks

Upgrade husky: 5.2.0 → 7.0.4 (major)

Open depfu[bot] opened this issue 4 years ago • 1 comments

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 (5.2.0 → 7.0.4) · Repo · Changelog

Release Notes

7.0.4

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

7.0.2

Fix pre-commit hook in WebStorm (#1023)

7.0.1

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

7.0.0

  • 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!

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

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 74 commits:

Depfu Status

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)

depfu[bot] avatar Oct 22 '21 03:10 depfu[bot]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/joelhooks/next-typescript-tailwind-mdx-starter/6NUtcjuY1nxksUh9DqFdcXCYStqU
✅ Preview: https://next-typescript-tailwind-mdx-starter-git-depfu-464f6a-joelhooks.vercel.app

vercel[bot] avatar Oct 22 '21 03:10 vercel[bot]