Bump spring to 3.4.10

[Tobianas]

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

[gemini-code-assist]

Summary of Changes

Hello @Tobianas, I'm Gemini Code Assist¹! 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 dependency upgrade, specifically updating the Spring Boot framework to version 3.4.10. This ensures the project benefits from the latest stability improvements, security patches, and features provided by the Spring Boot ecosystem, maintaining compatibility and leveraging recent advancements.

Highlights

• Spring Boot Version Update: The pull request updates the Spring Boot framework version from 3.3.13 to 3.4.10 across multiple 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 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]

Code Review

This pull request bumps the Spring Boot version from 3.3.13 to 3.4.10. This is a minor version update which can introduce new features, deprecations, and potential breaking changes. The changes in the pom.xml files are correct. However, I have a couple of suggestions for improving maintainability. First, it would be beneficial to use a Maven property for the Spring Boot version to ensure consistency across modules and simplify future updates. I've left specific comments on how this can be done. Second, for a dependency upgrade of this nature, it's good practice to include a summary of the changes from the release notes in the pull request description, especially highlighting any breaking changes and confirming that the application has been tested against them. This helps reviewers understand the impact of the change and the verification that was done.

[gemini-code-assist]

To improve maintainability, consider using a Maven property to manage the Spring Boot version. This would involve adding a <properties> section to this POM and defining the version there. For example:

<properties>
    <spring-boot.version>3.4.10</spring-boot.version>
</properties>

Then you can use it like this:

<version>${spring-boot.version}</version>

Ideally, this property would be defined in a parent POM (like lighty-parent) to ensure consistency across all modules that inherit from it.

[gemini-code-assist]

For better maintainability, it's a good practice to manage dependency versions using properties. You could define a property for the Spring Boot version in the existing <properties> section of this POM and use it here. This would centralize the version and make future updates easier. For example:

In <properties>:

<spring-boot.version>3.4.10</spring-boot.version>

And here:

<version>${spring-boot.version}</version>

This is especially helpful as the same version is being updated in other modules, and centralizing version management is a key principle of Maven.

[ihrasko]

Not suitable for stability branch.