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.0.1 #387

Closed

Conversation

lholmquist
Copy link
Member

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade husky from 7.0.4 to 9.0.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 is a major version upgrade, and may be a breaking change.

  • The recommended version is 5 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2024-01-25.
Release notes
Package name: husky
  • 9.0.1 - 2024-01-25

    Kicking off the year with an exciting update!

    TLDR;

    Improved user experience and a (even) smaller package size while packing in more features!

    Note: install using husky@latest to get the bug fixes that were released after.

    👋 By the Way

    I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

    Introducing husky init

    v8

    npm pkg set scripts.prepare="husky install"
    npm run prepare
    npx husky add .husky/pre-commit "npm test"

    v9

    Adding husky to a project is now easier than ever. It's just a single line that does the same as above. No need to read the docs to get started anymore.

    npx husky init

    Adding a New Hook

    v8

    npx husky add  .husky/pre-commit "npm test"
    git add --chmod=+x .husky/pre-commit # On Windows

    v9

    Adding a hook is as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command. For example, on Linux/macOS:

    echo "npm test" > .husky/pre-commit

    Further Size Reduction

    v8 was already the most compact Git hooks manager at approximately 6kB.

    v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

    To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

    More to Come

    Additional features are in the pipeline for v9. Stay tuned 🙌

    Other Changes

    • Enhanced security with CI and npm --provenance for safer publishing.
    • Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
    • Fixed permission issue for Windows-created hooks; they no longer need to be executable.
    • Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
    • Modified behavior when .git is missing; it now triggers a warning instead of failure.
    • Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
    • Updated the Husky API for module usage.
    • Transitioned to ESM for module usage.
    • Dropped support for Node 14 and 16.
    • Revamped docs.

    How to Migrate

    v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

    Here are the steps to migrate:

    package.json

    {
      "scripts": {
    -   "prepare": "husky install"
    +   "prepare": "husky"
      }
    }

    .husky/pre-commit

    - #!/usr/bin/env sh
    - . "$(dirname -- "$0")/_/husky.sh"
    npm test 

    Note: sh will be used to run hooks, even if a shebang is set.

    If you were using husky as a module:

    - const husky = require('husky')
    - // ...
    + import husky from 'husky'
    + console.log(husky())
  • 8.0.3 - 2023-01-03
    • fix: add git not installed message #1208
  • 8.0.2 - 2022-11-08
    • docs: remove deprecated npm set-script
  • 8.0.1 - 2022-05-09
    • fix: use POSIX equality operator
  • 8.0.0 - 2022-05-08

    What's Changed

    Feats

    • feat: add husky - prefix to logged global error messages by @ joshbalfour in #1092
    • feat: show PATH when command not found to improve debuggability
    • feat: drop Node 12 support
    • feat: skip install if $HUSKY=0

    Fixes

    • fix: hook script use /usr/bin/env sh instead of direct path of sh by @ skhaz in #1051
    • fix: actually set 'husky_skip_init' as readonly in ./husky.sh by @ hyperupcall in #1104
    • fix: force basename/dirname to treat $0 as an argument by @ mataha in #1132
    • fix: remove git.io links by @ renbaoshuo in #1136

    Docs

    Chore

  • 7.0.4 - 2021-10-21

    No changes. Husky v7.0.3 was reverted, this version is the same as v7.0.2.

from husky GitHub release notes
Commit messages
Package name: husky
  • 513c2c9 9.0.1
  • e48ee6c update npm_publish.yml
  • c68cc26 9.0.0
  • 4bf0f79 chore: fix deploy
  • c67a57a v9
  • ec13855 v9 (#1333)
  • a5c36f5 Add simplified Chinese documentation (#1290)
  • 3dd4ea2 fix: posts urls
  • 9d3eb31 Update troubleshooting.md (#1320)
  • 6a5290c docs: update hook references in migration guide (#1282)
  • 06df89a docs: use NODE_ENV to conditionally install husky (#1310)
  • 46325f8 docs: prefer delete script prepare compare to ignore scripts (#1307)
  • 94d0393 docs: add bun to getting-started.md (#1299)
  • 8c5a08c fix: do not search for rc file at `/husky/init.sh` (#1304)
  • 4f7f37f perf: use POSIX-defined parameter expansion (#1305)
  • 358f833 docs: clarify client-side hooks are supported (#1300)
  • 97b149d fix: docs link (#1274)
  • fd32c22 feat: add new hook file to staging with executable bit (#1243)
  • 7543615 docs: reorg
  • 0eba7dd style: format
  • 5ac4829 feat: support XDG_CONFIG_HOME (#1265)
  • ac2b52f docs: typo
  • c5c1af2 docs: clean
  • cdd8376 docs: clean

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@coveralls
Copy link

Coverage Status

coverage: 98.802%. remained the same
when pulling 86cff13 on snyk-upgrade-e167e1afc17a7c88de7f188dd1bfd685
into f01633a on main.

@lholmquist lholmquist closed this Apr 22, 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.

None yet

3 participants