chore(deps): update dependency husky to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
husky (source)	^7.0.0 -> 8.0.1

---

Release Notes

typicode/husky

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

Docs

• docs: fix uninstall via npm by @​pddpd in https://github.com/typicode/husky/pull/1033
• docs: add dog emoji as favicon by @​jamiehaywood in https://github.com/typicode/husky/pull/1095
• docs: replace deprecated npx --no-install option with npx --no by @​sibiraj-s in https://github.com/typicode/husky/pull/1070
• docs: add pnpm installation by @​MohamadKh75 in https://github.com/typicode/husky/pull/1139

Chore

• chore: update workflows by @​tiziodcaio in https://github.com/typicode/husky/pull/1125

---

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, click this checkbox.

---

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

[netlify]

✅ Deploy Preview for redwoodblog-dev ready!

Name	Link
🔨 Latest commit	c378c13
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodblog-dev/deploys/62acf0deaab441000829113b
😎 Deploy Preview	https://deploy-preview-23--redwoodblog-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.