FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

tests: Upgrade logback to 1.5.25 in tests by blakeli0 · Pull Request #4103 · googleapis/sdk-platform-java · GitHub

This repository was archived by the owner on May 14, 2026. It is now read-only.

tests: Upgrade logback to 1.5.25 in tests - #4103

Merged
blakeli0 merged 3 commits into
mainfrom
blakeli0-patch-8
Feb 5, 2026
Merged

tests: Upgrade logback to 1.5.25 in tests#4103
blakeli0 merged 3 commits into
mainfrom
blakeli0-patch-8

Conversation

blakeli0 commented Feb 4, 2026

Copy link
Copy Markdown
Contributor

We received vulnerability report for logback v1.5.21. Even though it is only used in tests and does not affect customers, it is still good to upgrade logback to 1.5.25 in tests.

product-auto-label Bot added the size: xs Pull request size is extra small. label Feb 4, 2026

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @blakeli0, 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 focuses on a minor but important dependency update within the test suite. It upgrades the logback library to version 1.5.25, primarily to resolve a reported vulnerability. While this change specifically targets test-scoped dependencies and does not affect production code or customer-facing features, it contributes to maintaining a secure and up-to-date development environment.

Highlights

  • Dependency Upgrade: The slf4j2-logback.version dependency has been upgraded from 1.5.21 to 1.5.25.
  • Vulnerability Mitigation: This upgrade addresses a reported vulnerability in the older logback version, enhancing security even though it's only used in test environments.
Changelog
  • java-showcase/gapic-showcase/pom.xml
    • Updated the slf4j2-logback.version property from 1.5.21 to 1.5.25.
Activity
  • No human activity has been recorded on this pull request yet.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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.

gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Code Review

This pull request upgrades the logback version for slf4j2 from 1.5.21 to 1.5.25 in the test dependencies. This change addresses a reported vulnerability, and it's a good practice to keep dependencies up-to-date, even for test scopes. The change is correctly isolated to the version property in java-showcase/gapic-showcase/pom.xml. The change is approved as it is correct and necessary.

blakeli0 marked this pull request as ready for review February 4, 2026 22:38
blakeli0 requested a review from jinseopkim0 February 4, 2026 22:38

sonarqubecloud Bot commented Feb 4, 2026

Copy link
Copy Markdown

sonarqubecloud Bot commented Feb 4, 2026

Copy link
Copy Markdown

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

sonarqubecloud Bot commented Feb 4, 2026

Copy link
Copy Markdown

Quality Gate passed for 'java_showcase_integration_tests'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

blakeli0 merged commit ff33367 into main Feb 5, 2026
60 of 61 checks passed
blakeli0 deleted the blakeli0-patch-8 branch February 5, 2026 16:21
lqiu96 pushed a commit that referenced this pull request Feb 12, 2026
We received vulnerability report for logback v1.5.21. Even though it is
only used in tests and does not affect customers, it is still good to
upgrade logback to 1.5.25 in tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants


Back | FazBrowse Home | New Git URL