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 7.0.4 to 9.1.1 #425

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

Conversation

lholmquist
Copy link
Member

snyk-top-banner

Snyk has created this PR to upgrade husky from 7.0.4 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.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 17 versions 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.
  • 9.0.11 - 2024-02-13
  • 9.0.10 - 2024-02-01
  • 9.0.9 - 2024-02-01
  • 9.0.8 - 2024-02-01
  • 9.0.7 - 2024-01-29
    • fix: typo and source ~/.huskyrc correctly (compatibility with v8)
    • docs: fix example by @ typicode in #1363
  • 9.0.6 - 2024-01-25
  • 9.0.5 - 2024-01-25
  • 9.0.4 - 2024-01-25
  • 9.0.3 - 2024-01-25
  • 9.0.2 - 2024-01-25
  • 9.0.1 - 2024-01-25
  • 8.0.3 - 2023-01-03
  • 8.0.2 - 2022-11-08
  • 8.0.1 - 2022-05-09
  • 8.0.0 - 2022-05-08
  • 7.0.4 - 2021-10-21
from husky GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • 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 7.0.4 to 9.1.1.

See this package in npm:
husky

See this project in Snyk:
https://app.snyk.io/org/nodeshift-agg/project/e8d21d75-2403-4802-8afa-ada5e48d4de5?utm_source=github&utm_medium=referral&page=upgrade-pr
@coveralls
Copy link

Coverage Status

coverage: 98.802%. first build
when pulling 7837f90 on snyk-upgrade-082b90974fef1f3244cf5d7d3b6baa32
into 7e2d7d6 on main.

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.

export HUSKY=0 in a config has no effect
3 participants