Skip to content

chore(deps): update dependency husky to v4.3.8#1214

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/husky-4.x
Open

chore(deps): update dependency husky to v4.3.8#1214
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/husky-4.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Oct 18, 2023

This PR contains the following updates:

Package Change Age Confidence
husky 4.3.04.3.8 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

typicode/husky (husky)

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 #​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


Configuration

📅 Schedule: (UTC)

  • 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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Oct 18, 2023

⚠ 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 cli npm v10.2.0 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN cli npm v10.2.0 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular/core@2.4.10
npm ERR! Found: zone.js@0.10.3
npm ERR! node_modules/zone.js
npm ERR!   zone.js@"0.10.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer zone.js@"^0.7.2" from @angular/core@2.4.10
npm ERR! node_modules/@angular/core
npm ERR!   @angular/core@"2.4.10" from the root project
npm ERR!   peer @angular/core@"2.4.10" from @angular/common@2.4.10
npm ERR!   node_modules/@angular/common
npm ERR!     @angular/common@"2.4.10" from the root project
npm ERR!     5 more (@angular/forms, @angular/platform-browser, ...)
npm ERR!   8 more (@angular/compiler, @angular/compiler-cli, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: zone.js@0.7.8
npm ERR! node_modules/zone.js
npm ERR!   peer zone.js@"^0.7.2" from @angular/core@2.4.10
npm ERR!   node_modules/@angular/core
npm ERR!     @angular/core@"2.4.10" from the root project
npm ERR!     peer @angular/core@"2.4.10" from @angular/common@2.4.10
npm ERR!     node_modules/@angular/common
npm ERR!       @angular/common@"2.4.10" from the root project
npm ERR!       5 more (@angular/forms, @angular/platform-browser, ...)
npm ERR!     8 more (@angular/compiler, @angular/compiler-cli, ...)
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/124fb1/b2704f/cache/others/npm/_logs/2023-10-18T12_24_15_510Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/124fb1/b2704f/cache/others/npm/_logs/2023-10-18T12_24_15_510Z-debug-0.log

@renovate renovate Bot requested a review from koenmetsu as a code owner October 18, 2023 12:22
@renovate renovate Bot force-pushed the renovate/husky-4.x branch from 7577728 to 9b0e99c Compare October 18, 2023 12:24
@renovate renovate Bot force-pushed the renovate/husky-4.x branch from 9b0e99c to 77caa99 Compare April 4, 2025 03:47
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 4, 2025

⚠️ 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 cli npm v11.16.0 does not support Node.js v16.15.0. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm error (0 , U.tracingChannel) is not a function
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-29T07_27_45_512Z-debug-0.log

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 4, 2025

@renovate renovate Bot force-pushed the renovate/husky-4.x branch 2 times, most recently from ac986a4 to 6840055 Compare May 5, 2025 14:45
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 5, 2025

@renovate renovate Bot force-pushed the renovate/husky-4.x branch 2 times, most recently from 5683fd5 to e18ac16 Compare August 19, 2025 07:53
@renovate renovate Bot force-pushed the renovate/husky-4.x branch 2 times, most recently from a050ba3 to e3a85dc Compare January 6, 2026 10:13
@renovate renovate Bot force-pushed the renovate/husky-4.x branch 2 times, most recently from b1f5d3d to a0ef8fc Compare March 19, 2026 19:20
@renovate renovate Bot force-pushed the renovate/husky-4.x branch from a0ef8fc to 2a939c3 Compare April 24, 2026 08:43
@renovate renovate Bot force-pushed the renovate/husky-4.x branch 6 times, most recently from 5700918 to 1bd4fc5 Compare May 7, 2026 09:38
@renovate renovate Bot force-pushed the renovate/husky-4.x branch from 1bd4fc5 to 6caefd2 Compare May 7, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants