Skip to content

Comments

Bump grpc-netty to 1.74.0#2332

Merged
ihrasko merged 1 commit intoPANTHEONtech:20.xfrom
ihrasko:20.x-grpc-netty-1740
Aug 28, 2025
Merged

Bump grpc-netty to 1.74.0#2332
ihrasko merged 1 commit intoPANTHEONtech:20.xfrom
ihrasko:20.x-grpc-netty-1740

Conversation

@ihrasko
Copy link
Collaborator

@ihrasko ihrasko commented Aug 28, 2025

Snyk has created this PR to upgrade io.grpc:grpc-netty from 1.73.0 to 1.74.0.

https://github.com/grpc/grpc-java/releases/tag/v1.74.0

(cherry picked from commit 05d41f5)

Snyk has created this PR to upgrade io.grpc:grpc-netty
from 1.73.0 to 1.74.0.

https://github.com/grpc/grpc-java/releases/tag/v1.74.0

Signed-off-by: Ivan Hrasko <[email protected]>
(cherry picked from commit 05d41f5)
@ihrasko ihrasko merged commit 2d489b3 into PANTHEONtech:20.x Aug 28, 2025
5 of 6 checks passed
@ihrasko ihrasko deleted the 20.x-grpc-netty-1740 branch August 28, 2025 12:18
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @ihrasko, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the grpc-netty dependency from version 1.73.0 to 1.74.0. This is an automated update initiated by Snyk, aiming to ensure the project utilizes the latest stable version of gRPC, thereby incorporating any new features, bug fixes, or security enhancements available in the upstream grpc-java project.

Highlights

  • Dependency Update: The grpc.version property in lighty-modules/lighty-gnmi/lighty-gnmi-proto/pom.xml has been updated from 1.73.0 to 1.74.0.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly bumps the grpc.version property to 1.74.0. My review includes a suggestion to improve dependency management by centralizing version properties in a parent POM for better maintainability.

<properties>
<protobuf.version>3.25.8</protobuf.version>
<grpc.version>1.73.0</grpc.version>
<grpc.version>1.74.0</grpc.version>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

While this version bump is correct, I've noticed that the grpc.version property is defined locally in this module's pom.xml. For better long-term maintainability and to ensure version consistency across all modules, it's a best practice to manage dependency versions in a central location. Consider moving this property (and other similar ones like protobuf.version) to the <properties> section of a parent POM, for example lighty-core/lighty-parent/pom.xml. This would prevent potential version conflicts in the future.

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