Skip to content

Update husky in / from 0.14.3 to 1.0.0#36

Open
ghost wants to merge 1 commit intomasterfrom
husky-1.0.0-272.0.0
Open

Update husky in / from 0.14.3 to 1.0.0#36
ghost wants to merge 1 commit intomasterfrom
husky-1.0.0-272.0.0

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Sep 26, 2018

Dependencies.io has updated husky (a npm dependency in /) from "0.14.3" to "1.0.0".

1.0.0

After a year of pre-releases and a complete rewrite, this marks the first stable release of husky 🐶🎉.

Notable changes

Below you'll find consolidated changes since 0.14.3. There's no change in code between 1.0.0-rc.15 and 1.0.0.

  • Hooks

    • Add sendemail-validate hook
  • Config

    • Move hooks config from scripts field to husky field
    • Prefer raw names for hooks (e.g. pre-commit rather than precommit)
    • Support .huskyrc config
  • Package managers

    • Support environments where yarn is the only package manager installed
    • Support pnpm package manager
  • Environment variables

    • Add HUSKY_SKIP_INSTALL environment variable for skipping git hooks installation
    • Add HUSKY_GIT_STDIN environment variable for pre-push, pre-receive, post-receive and post-rewrite to access arguments passed by Git via stdin
    • Rename GIT_PARAMS to HUSKY_GIT_PARAMS
  • Messages

    • Add many more messages in case of errors
    • Add please-upgrade-node message if using with unsupported Node version
    • Make --no-verify message more accurate and only show it for hooks that can be skipped
  • Upgrade

    • Add husky-upgrade command to automatically migrate hooks in package.json
    • Add deprecation warning for hooks that are still defined in scripts
  • Other

    • Drop Node 4 support
    • Drop integrated nvm support (see Node version management in docs)

Credits

Huge thanks to all the Contributors and Patreon Supporters! 🙏

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.

1 participant