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

[Snyk] Upgrade husky from 9.1.0 to 9.1.1 #143

Closed

Conversation

JaredReisinger
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade husky from 9.1.0 to 9.1.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released on 22 days ago.

Release notes
Package name: husky
  • 9.1.1 - 2024-07-18

    Super saiyan god dog! It's over 9.0.0!

    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

    • #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" are deprecated. husky command will automatically remove them, no action required.
    • If you're having code in ~/.huskyrc please move it to .config/husky/init.sh

    Support for these will be removed in v10.

    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 😉

  • 9.1.0 - 2024-07-17
    No content.
from husky GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade husky from 9.1.0 to 9.1.1.

See this package in npm:
husky

See this project in Snyk:
https://app.snyk.io/org/jaredreisinger/project/02e6161d-4882-479d-b56c-8dab1a8d6716?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

codecov bot commented Aug 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.44%. Comparing base (d44e203) to head (ee935fb).
Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #143   +/-   ##
=======================================
  Coverage   92.44%   92.44%           
=======================================
  Files          20       20           
  Lines        3084     3084           
  Branches      300      300           
=======================================
  Hits         2851     2851           
  Misses        232      232           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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.

2 participants