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 com.google.api.grpc:proto-google-common-protos from 2.36.0 to 2.38.0 #295

Closed

Conversation

EngHabu
Copy link
Contributor

@EngHabu EngHabu commented May 17, 2024

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


Snyk has created this PR to upgrade com.google.api.grpc:proto-google-common-protos from 2.36.0 to 2.38.0.

ℹ️ 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 3 versions ahead of your current version.

  • The recommended version was released a month ago, on 2024-04-18.


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

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

….0 to 2.38.0

Snyk has created this PR to upgrade com.google.api.grpc:proto-google-common-protos from 2.36.0 to 2.38.0.

See this package in maven:
com.google.api.grpc:proto-google-common-protos

See this project in Snyk:
https://app.snyk.io/org/flyte/project/0631be49-03a8-4bec-a1a3-6f3ceca5643d?utm_source=github&utm_medium=referral&page=upgrade-pr
@RRap0so RRap0so mentioned this pull request Jul 2, 2024
8 tasks
@RRap0so RRap0so closed this Jul 2, 2024
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.

3 participants