Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency husky to v9.1.7 #2520

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
husky 9.0.7 -> 9.1.7 age adoption passing confidence

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

  • fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

  • bunx husky init command
  • Workaround for some hooks implementation on Windows 🤷

Deprecations

  • Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
  • Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

v9.0.11

Compare Source

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

Copy link
Contributor Author

renovate bot commented Feb 7, 2024

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm ERR!     node_modules/@mikro-orm/nestjs
npm ERR!       dev @mikro-orm/nestjs@"5.2.3" from the root project
npm ERR!     11 more (@nestjs/axios, @nestjs/core, @nestjs/mapped-types, ...)
npm ERR!   7 more (@nestjs/core, @nestjs/mapped-types, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     dev @nestjs/sequelize@"10.0.0" from the root project
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-18T16_03_30_671Z-debug-0.log

@renovate renovate bot force-pushed the renovate/husky-9.x branch 7 times, most recently from 833eea4 to d010414 Compare February 14, 2024 00:50
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.0.10 chore(deps): update dependency husky to v9.0.11 Feb 14, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch 2 times, most recently from c340483 to 9c38dc3 Compare February 18, 2024 16:03
Copy link
Contributor Author

renovate bot commented Jul 16, 2024

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   dev reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/common
npm ERR!     dev @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from @mikro-orm/[email protected]
npm ERR!     node_modules/@mikro-orm/nestjs
npm ERR!       dev @mikro-orm/nestjs@"5.2.3" from the root project
npm ERR!     11 more (@nestjs/axios, @nestjs/core, @nestjs/mapped-types, ...)
npm ERR!   7 more (@nestjs/core, @nestjs/mapped-types, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/sequelize
npm ERR!   dev @nestjs/sequelize@"10.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/sequelize
npm ERR!     dev @nestjs/sequelize@"10.0.0" from the root project
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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-11-18T16_14_36_146Z-debug-0.log

@renovate renovate bot force-pushed the renovate/husky-9.x branch 3 times, most recently from 0ee6d87 to de5644c Compare July 17, 2024 18:01
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.0.11 chore(deps): update dependency husky to v9.1.0 Jul 17, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from de5644c to 4d6e550 Compare July 18, 2024 15:02
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.0 chore(deps): update dependency husky to v9.1.1 Jul 18, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from 4d6e550 to 650bc4a Compare July 25, 2024 14:19
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.1 chore(deps): update dependency husky to v9.1.2 Jul 25, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from 650bc4a to 51d57a0 Compare July 26, 2024 23:07
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.2 chore(deps): update dependency husky to v9.1.3 Jul 26, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from 51d57a0 to 58c908a Compare July 29, 2024 15:24
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.3 chore(deps): update dependency husky to v9.1.4 Jul 29, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from 58c908a to f98e3e4 Compare August 20, 2024 14:46
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.4 chore(deps): update dependency husky to v9.1.5 Aug 20, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from f98e3e4 to bec2fa2 Compare September 12, 2024 01:35
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.5 chore(deps): update dependency husky to v9.1.6 Sep 12, 2024
@renovate renovate bot force-pushed the renovate/husky-9.x branch from bec2fa2 to f7138ad Compare November 18, 2024 16:14
@renovate renovate bot changed the title chore(deps): update dependency husky to v9.1.6 chore(deps): update dependency husky to v9.1.7 Nov 18, 2024
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