Skip to content

Bump spring-boot to 3.5.11 - #2582

Merged
ihrasko merged 1 commit into
PANTHEONtech:23.xfrom
Tobianas:23.x_bump_spring
Feb 26, 2026
Merged

Bump spring-boot to 3.5.11#2582
ihrasko merged 1 commit into
PANTHEONtech:23.xfrom
Tobianas:23.x_bump_spring

Conversation

@Tobianas

Copy link
Copy Markdown
Contributor

https://github.com/spring-projects/spring-boot/releases/tag/v3.5.11

Signed-off-by: tobias.pobocik <tobias.pobocik@pantheon.tech>
(cherry picked from commit 2b3f26f)
@gemini-code-assist

Copy link
Copy Markdown

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 updates the Spring Boot framework version across the project to 3.5.11. This ensures that the application leverages the latest improvements, bug fixes, and security patches provided by the new Spring Boot release, contributing to overall stability and maintainability.

Highlights

  • Spring Boot Version Update: The core Spring Boot dependency version has been bumped from 3.5.10 to 3.5.11.
  • Parent POM Update: The spring-boot-starter-parent version in an example module has also been updated to 3.5.11 to align with the new dependency version.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • lighty-core/lighty-controller-spring-di/pom.xml
    • Updated the spring-boot-dependencies version from 3.5.10 to 3.5.11.
  • lighty-examples/lighty-controller-springboot-netconf/pom.xml
    • Updated the spring-boot-starter-parent version from 3.5.10 to 3.5.11.
Activity
  • No specific activity (comments, reviews, or progress updates) has been recorded for 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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown

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 the Spring Boot version to 3.5.11 in two modules. The changes are correct, but to improve long-term maintainability, I've suggested using a Maven property to centralize the version number. This will make future dependency updates simpler and more consistent across the project.

<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>3.5.10</version>
<version>3.5.11</version>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

For better maintainability and to ensure version consistency across modules, it's recommended to use a property for the Spring Boot version. This property should be defined in a common parent pom.xml. This avoids hardcoding the version number in multiple places, making future updates easier and less error-prone.

Suggested change
<version>3.5.11</version>
<version>${spring-boot.version}</version>

<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>3.5.10</version>
<version>3.5.11</version>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

For better maintainability and to ensure version consistency across modules, it's recommended to use a property for the Spring Boot version. This property should be defined in a common parent pom.xml if this module is part of a multi-module build. This avoids hardcoding the version number in multiple places, making future updates easier and less error-prone.

Suggested change
<version>3.5.11</version>
<version>${spring-boot.version}</version>

@ihrasko
ihrasko merged commit a4d619f into PANTHEONtech:23.x Feb 26, 2026
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