Skip to content

Conversation

fugerit79
Copy link
Member

snyk-top-banner

Snyk has created this PR to upgrade io.quarkiverse.groovy:quarkus-groovy-junit5 from 3.15.0 to 3.16.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 2 versions ahead of your current version.

  • The recommended version was released on a month ago.


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:

…to 3.16.1

Snyk has created this PR to upgrade io.quarkiverse.groovy:quarkus-groovy-junit5 from 3.15.0 to 3.16.1.

See this package in maven:
io.quarkiverse.groovy:quarkus-groovy-junit5

See this project in Snyk:
https://app.snyk.io/org/fugerit79/project/eaffe730-360c-485c-8d77-8326c0aec20a?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sonarqubecloud bot commented Dec 5, 2024

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@fugerit79 fugerit79 merged commit bb142bb into main Dec 5, 2024
4 checks passed
@fugerit79 fugerit79 deleted the snyk-upgrade-77d736029346501414bb8d39099c4b0a branch December 5, 2024 09:37
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