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 4.2.0 to 4.2.1 #242

Closed

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade husky from 4.2.0 to 4.2.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 22 days ago, on 2020-01-23.
Release notes
Package name: husky
  • 4.2.1 - 2020-01-23
    • Fix: support spaces in path to husky.local.sh #658
  • 4.2.0 - 2020-01-21
    • Check Git version during install and log an error if it's <2.13.0
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

@sonarcloud
Copy link

sonarcloud bot commented Feb 15, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@sogame sogame closed this Feb 25, 2020
@sogame sogame deleted the snyk-upgrade-b9b587e33c9feaeb723dcee558d1951d branch February 25, 2020 22:12
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

2 participants