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 minimatch from 5.0.1 to 5.1.0 #649

Merged
merged 1 commit into from
Feb 1, 2023

Conversation

pacostas
Copy link
Member

@pacostas pacostas commented Jun 7, 2022

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


Snyk has created this PR to upgrade minimatch from 5.0.1 to 5.1.0.

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 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2022-05-16.
Release notes
Package name: minimatch from minimatch GitHub release notes
Commit messages
Package name: minimatch
  • 6410ef3 5.1.0
  • 43cfa81 use windowsPathNoEscape/allowWindowsEscape opts
  • e2a142c docs: remote extra bracket

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 remained the same at 98.208% when pulling 5d19cfd on snyk-upgrade-2ff0cd39038cb41dcd528bc991250794 into eb7c5fc on main.

@lholmquist lholmquist merged commit b25fad5 into main Feb 1, 2023
@lholmquist lholmquist deleted the snyk-upgrade-2ff0cd39038cb41dcd528bc991250794 branch February 1, 2023 16:18
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

4 participants