Skip to content

[Snyk] Upgrade husky from 3.0.5 to 3.1.0 - #7

Merged
d2s merged 2 commits into
masterfrom
snyk-upgrade-ca3472799e93c0513444637b5066e4b0
Jan 10, 2020
Merged

[Snyk] Upgrade husky from 3.0.5 to 3.1.0#7
d2s merged 2 commits into
masterfrom
snyk-upgrade-ca3472799e93c0513444637b5066e4b0

Conversation

@snyk-bot

Copy link
Copy Markdown
Contributor

Snyk has created this PR to upgrade husky from 3.0.5 to 3.1.0.

ℹ️ 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 5 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2019-11-18.
Release notes
Package name: husky
  • 3.1.0 - 2019-11-18
    • Add pre-merge-commit hook (#605)
  • 3.0.9 - 2019-10-12
    • Reduce dependencies: replace is-ci with ci-info #579
  • 3.0.8 - 2019-10-02
    • Fix: git worktree support #580
    • Debug: check GIT_DIR environment variable when hooks are run
  • 3.0.7 - 2019-09-28

    Debug: display husky version and created at

  • 3.0.6 - 2019-09-28

    Debug: improve messages

  • 3.0.5 - 2019-09-01

    Fix: prevent postinstall from failing on windows #573

from husky GitHub release notes
Commit messages
Package name: husky

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

@snyk-bot
snyk-bot requested a review from d2s as a code owner January 10, 2020 02:32
@d2s
d2s merged commit 058677c into master Jan 10, 2020
@d2s
d2s deleted the snyk-upgrade-ca3472799e93c0513444637b5066e4b0 branch January 19, 2020 22:57
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