🚨 [security] Update husky 4.3.0 → 4.3.8 (patch)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ husky (4.3.0 → 4.3.8) · Repo · Changelog

Release Notes

4.3.8

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

4.3.7

• Fix: upgrade find-versions to 4.0.0 #837

4.3.6

• Fix prepare-commit-msg on windows #737

4.3.4

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

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

Commits

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

• 4.3.8
• fix 'toString' error and improve messages
• Update LICENSE (#736)
• 4.3.7
• update pkg-dir dependency and some devDependencies
• Upgrade find-versions to 4.0.0 (#837)
• 4.3.6
• fix prepare-commit-msg on windows (#737)
• Update README.md
• add prepare-commit-msg test
• 4.3.5
• rollback do not exit with 1 if install fails
• Update README.md
• 4.3.4
• update error message
• 4.3.3
• ignore tsconfig.tsbuildinfo
• 4.3.2
• provide workaround for npm7
• 4.3.1
• exit with 1 if husky fails to install/uninstall
• update gitignore
• Update README.md
• Changed create-react-app repo url (#759)
• Update README.md
• Update node.js.yml
• Update node.js.yml
• Update node.js.yml
• Create node.js.yml
• Update README.md

↗️ find-versions (indirect, 3.2.0 → 4.0.0) · Repo

Release Notes

4.0.0

Breaking

• Require Node.js 10 fb1da23
• Some patterns are no longer detected because of semver-regex limitations, which can and should be fixed:

  find-versions/test.js

  Line 16 in ceb9950

      <tbody>
  

  // TODO: Disabled because of https://github.com/Improve the regex, require Node.js 8 sindresorhus/semver-regex#15#issuecomment-751278009

v3.2.0...v4.0.0

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

Commits

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

• 4.0.0
• Require Node.js 10

↗️ semver-regex (indirect, 2.0.0 → 3.1.4) · Repo

Security Advisories 🚨

🚨 Regular expression denial of service in semver-regex

An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the semver-regex npm package, when an attacker is able to supply arbitrary input to the test() method

🚨 semver-regex Regular Expression Denial of Service (ReDOS)

npm semver-regex is vulnerable to Inefficient Regular Expression Complexity

Release Notes

3.1.4

• Backport of ReDoS fix 7712ba5

3.1.2

• Fix regex catastrophic backtracking 6baf2cc
  Working around this meant accepting some obscure false-positives. I don't think it will affect any real code, but it's good to be aware of. See the disabled tests in the commit.

v3.1.1...v3.1.2

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

Commits

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

• 3.1.4
• Fix ReDoS vulnerability backport
• Fix ReDoS vulnerability backport
• 3.1.2
• Move to GitHub Actions
• Fix regex catastrophic backtracking
• Meta tweaks
• 3.1.1
• Allow 0 as numeric identifier (#19)
• Create funding.yml
• 3.1.0
• Add TypeScript definition (#16)
• 3.0.0
• Meta tweaks
• Improve the regex, require Node.js 8 (#15)

↗️ which-pm-runs (indirect, 1.0.0 → 1.1.0)

Sorry, we couldn't find anything useful about this release.

🆕 yocto-queue (added, 0.1.0)

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

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 cancel merge

Cancels automatic merging of this PR

@​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)