Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Snyk] Upgrade semver from 7.6.1 to 7.6.2 #214

Closed

Conversation

jakob-lj
Copy link
Contributor

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


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade semver from 7.6.1 to 7.6.2.

ℹ️ 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 on 22 days ago.

Release notes
Package name: semver from semver GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade semver from 7.6.1 to 7.6.2.

See this package in npm:
semver

See this project in Snyk:
https://app.snyk.io/org/it/project/dfda9428-6f07-46e2-89b1-78190667d7ea?utm_source=github&utm_medium=referral&page=upgrade-pr
@jakob-lj jakob-lj requested a review from a team as a code owner May 31, 2024 14:09
@joakimen joakimen closed this Jul 23, 2024
@joakimen joakimen deleted the snyk-upgrade-d46c95a4319946eb11c42eaead8aebc8 branch July 23, 2024 12:47
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants