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 snyk from 1.339.3 to 1.341.1 #57

Merged
merged 1 commit into from
Jun 17, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade snyk from 1.339.3 to 1.341.1.

merge advice

ℹ️ 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 4 versions ahead of your current version.
  • The recommended version was released 2 days ago, on 2020-06-15.
Release notes
Package name: snyk from snyk GitHub release notes
Commit messages
Package name: snyk
  • 71f4578 Merge pull request #1185 from snyk/fix/remove-dubplicate-printdeps
  • 9c23809 fix: remove duplicated call to maybePrintDeps
  • bb70d31 Merge pull request #1146 from snyk/feat/bump-debug
  • 3b0c1de Merge pull request #1181 from snyk/feat/increase-max-path-count-allowed
  • 487df64 Merge pull request #1182 from snyk/fix/correct-error-on-missing-target-folder
  • 5034560 fix: correct error on missing target folder for reachable vulns
  • 8e0e56c feat: increase max path, to allow large projs pass after prune
  • 82698ab feat: upgrade debug

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

@Skerwe Skerwe merged commit 58ee648 into master Jun 17, 2020
@Skerwe Skerwe deleted the snyk-upgrade-c39a520d1a304e6325719871b7223fff branch June 17, 2020 20:20
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