On behalf of the team and everyone who has contributed, I am pleased to announce a new milestone for the next Spring Framework generation.
The fourth milestone continues delivering new features and refinements on top of 7.0.0-M1, 7.0.0-M2 and 7.0.0-M3.
Class-File API usage for Java 24+ apps
Spring Framework reads class bytecode to collect metadata about the application code.
Historically we have used a slim ASM fork for this purpose, through the MetadataReaderFactory and MetadataReader types in the org.springframework.core.type.classreading package.
Although Spring applications typically have no direct exposure to this API, this is especially useful when parsing @Configuration…
On behalf of the Spring for GraphQL team, I am pleased to announce the availability of our first 1.4 milestone.
Aligning with the GraphQL over HTTP specification
The GraphQL over HTTP draft specification is making good progress,
so we have decided to fully align with it for our 1.4 release.
Previous versions of Spring for GraphQL already supported the official "application/graphql-response+json",
and it has been our default response media type for a while now.
Usually, GraphQL HTTP clients should expect 4xx/5xx HTTP responses if the server is unavailable,
security credentials are missing or if the request body is not valid JSON.
The remaining gap with this new specification was about the HTTP response status behavior in case of complete GraphQL engine failures.
With recent changes, "application/graphql-response+json" responses will also use 4xx statuses if the GraphQL document sent by the client cannot be parsed
or is considered invalid by the GraphQL engine. We are keeping the former behavior when clients request the "application/json"…
On behalf of the team and everyone who has contributed, I am pleased to announce the third milestone of the next Spring Framework generation.
The third milestone continues delivering new features and refinements on top of 7.0.0-M1 and 7.0.0-M2.
In this milestone, we are shipping the first step of our new "API versioning" feature for web applications.
Keep an eye for further improvements and documentation there, we're definitely interested in feedback from the community!
On behalf of the team and everyone who has contributed, I am pleased to announce the first milestone of the next Spring Framework generation.
As announced previously, we shipped "7.0.0-M1" to the usual repo.spring.io artifact repository, but also to Maven Central.
We hope to collect more feedback from the community this year along the way; we are targeting November 2025 for the official release date.
This first milestone partially delivers the baseline changes that we shared last October.
Spring Framework still expects a JDK 17-27 compatibility range and raises its minimum requirements to…