Skip to content

Comments

Bump third party dependencies#2289

Merged
ihrasko merged 9 commits intoPANTHEONtech:mainfrom
Tobianas:mainBump
Jul 29, 2025
Merged

Bump third party dependencies#2289
ihrasko merged 9 commits intoPANTHEONtech:mainfrom
Tobianas:mainBump

Conversation

@Tobianas
Copy link
Contributor

No description provided.

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 @Tobianas, 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 performs a routine maintenance update by bumping various third-party dependencies and Maven plugins across the project's pom.xml files. The primary goal is to leverage the latest improvements, bug fixes, and security patches from upstream libraries and tools, ensuring the project remains current and robust.

Highlights

  • Core Dependency Updates: I've updated several key third-party dependencies, including testng from 7.10.2 to 7.11.0, spotbugs-annotations from 4.8.6 to 4.9.3, commons-io from 2.19.0 to 2.20.0, and org.json from 20240303 to 20250517.
  • Major Version Bumps for Test Libraries: Significant updates include jsonassert moving from 1.5.1 to a release candidate 2.0-rc1, and junit-bom jumping from 5.13.1 to a milestone release 6.0.0-M2. These major version changes might introduce breaking changes or new features that warrant careful testing.
  • Spring Boot and Maven Plugin Updates: The Spring Boot dependencies and parent versions have been bumped from 3.5.3 to 3.5.4. Additionally, several Maven plugins, such as maven-gpg-plugin (to 3.2.8), maven-enforcer-plugin (to 3.6.1), and license-maven-plugin (a major bump to 5.0.0), have been updated across various pom.xml files.
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 or fill out our survey to provide feedback.

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 updates several third-party dependencies. junit-bom and jsonassert are being updated to pre-release versions (milestone and release candidate, respectively), which can introduce instability. The new version for org.json:json appears to be non-existent and will likely break the build.

Tobianas added 7 commits July 29, 2025 10:19
JIRA: LIGHTY-354
Signed-off-by: tobias.pobocik <[email protected]>
@ihrasko ihrasko merged commit a74fc23 into PANTHEONtech:main Jul 29, 2025
6 checks passed
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