swellaby / slashhandler

Framework for building slack slashhandlers
MIT License
1 stars 0 forks source link

chore(deps): update dependency husky to v5 #130

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 3 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
husky ^4.3.5 -> ^5.0.0 age adoption passing confidence

Release Notes

typicode/husky ### [`v5.0.9`](https://togithub.com/typicode/husky/releases/v5.0.9) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.8...v5.0.9) - fix(install): do not fail if not inside a Git directory (closes [#​851](https://togithub.com/typicode/husky/issues/851)) See for v5 release notes ### [`v5.0.8`](https://togithub.com/typicode/husky/releases/v5.0.8) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.7...v5.0.8) - fix(install): better handle Git <2.9 ([#​846](https://togithub.com/typicode/husky/issues/846)) closes [#​844](https://togithub.com/typicode/husky/issues/844) ### [`v5.0.7`](https://togithub.com/typicode/husky/releases/v5.0.7) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.6...v5.0.7) - fix(shell): double quote params ([#​824](https://togithub.com/typicode/husky/issues/824)) ### [`v5.0.6`](https://togithub.com/typicode/husky/releases/v5.0.6) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.5...v5.0.6) - Remove unused files ### [`v5.0.5`](https://togithub.com/typicode/husky/releases/v5.0.5) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.4...v5.0.5) - Fix custom directory support [#​827](https://togithub.com/typicode/husky/issues/827) ### [`v5.0.4`](https://togithub.com/typicode/husky/compare/v5.0.3...v5.0.4) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.3...v5.0.4) ### [`v5.0.3`](https://togithub.com/typicode/husky/compare/v5.0.2...v5.0.3) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.2...v5.0.3) ### [`v5.0.2`](https://togithub.com/typicode/husky/compare/v5.0.1...v5.0.2) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.1...v5.0.2) ### [`v5.0.1`](https://togithub.com/typicode/husky/compare/v5.0.0...v5.0.1) [Compare Source](https://togithub.com/typicode/husky/compare/v5.0.0...v5.0.1) ### [`v5.0.0`](https://togithub.com/typicode/husky/releases/v5.0.0) [Compare Source](https://togithub.com/typicode/husky/compare/v4.3.8...v5.0.0) 👉 See 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`.

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: 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.

calebcartwright commented 3 years ago

Nope

renovate[bot] commented 3 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 5.x releases. However, if you upgrade to 5.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.