Hi, Spring fans! In this installment, we talk to the legendary lead of Spring Cloud and friend to the community, Spencer Gibb! This was recorded live from Las Vegas, NV, at the fantastic SpringOne 2025 event!
On behalf of the team and everyone who has contributed, I'm happy to announce that Spring Boot 3.4.10 has been released and is now available from Maven Central.
On behalf of the team and everyone who has contributed, I'm happy to announce that Spring Boot 3.5.6 has been released and is now available from Maven Central.
On behalf of the team and everyone who has contributed, I'm happy to announce that Spring Boot 4.0.0-M3 has been released and is now available from Maven Central.
On behalf of the Spring AI engineering team and everyone who has contributed, I'm happy to announce that Spring AI 1.0.2 has been released and is now available from Maven Central.
On behalf of the team and all contributors, I am pleased to announce that Spring Batch 6.0.0-M3 and 5.2.3 are now available in Maven Central!
Version 5.2.3 is a maintenance release that includes several bug fixes and dependency upgrades. You can find the complete list of changes in the release notes.
This blog post is more about the 6.0.0-M3 milestone release, which comes with following features and improvements:
New concurrency model
Ability to stop all kinds of steps
Observability with the Java Flight Recorder
For the complete list of changes, please check its release notes here.
On behalf of the team and everyone who contributed, I am pleased to announce the Third Milestone of Spring Integration 7.0.0 generation.
For convenience, the 7.0.0-M3 artifacts are also available in Maven Central.
In addition, the 6.5.2 and 6.4.7 versions with bug fixes and dependency upgrades have been released.
Some notable changes in 7.0.0-M3 are:
JUnit 6 upgrade;
The Nullability via JSpecify and Nullaway is applied to every single package in the project;
The AbstractPersistentAcceptOnceFileListFilter implementations now deal with full remote file to avoid conflict with the same file name in different directories;
The AbstractInboundFileSynchronizer now caches the Session.list() result (after filtering) between polls when maxFetchSize is limited;
The Spring Retry dependnecy has been removed and its API has been replaced with similar one in the Spring Framework Core;
All the available major/minor dependency upgrades.
On behalf of the team and everyone who contributed, we are pleased to announce that Spring for Apache Kafka 4.0.0-M5 has been released.
We also released a patch GA version 3.3.10.
We extend our gratitude to all contributors who made these releases possible.
This is the final milestone release for the 4.0 series.
We plan to release the first release candidate (RC1) next month.
What's New in 4.0.0-M5
Jackson 3 Support: Added comprehensive Jackson 3 support across all serialization and messaging components.
The framework automatically detects and prefers Jackson 3 when available, while Jackson…
Hi, Spring fans! Welcome to another extra special installment of This Week in Spring, wherein we celebrate a very auspicious day indeed: the release of Java 25 and GraalVM 25! That's right: an incredible new iteration of the JVM has just dropped and with it come a ton of features! Let's go through some of my favorites.
One nicety is the new Module import declarations - import all the packages in a given module with a new import variant. (Does not require importer be in a module). So now you could do: import module java.base; to get most of the core JDK types in your program in a single line…
I am pleased to announce that the third Spring for GraphQL 2.0 Milestone release is now available.
Nullability support in schema mapping inspection
Our Schema Mapping Inspection feature
got a recent upgrade thanks to our work on Null-safety in Spring projects.
If your application is written in Kotlin, or is using Null-safety annotations,
further inspections will be performed. The GraphQL schema can declare nullable types (Book) and non-nullable types (Book!).
We can ensure that both the schema and the application are in sync when it comes to nullability information.
For schema fields, we can check that the relevant Class properties and DataFetcher return types with the same nullability.
For field arguments, we can ensure that DataFetcher parameters have the same nullability