On behalf of the Spring for GraphQL team, I am pleased to announce the availability of 1.4.0, the generally available release.

In case you missed those, the 1.4.0-M1 and 1.4.0-RC1 release blog posts described the new features for this generation. The Spring for GraphQL 1.4.0 wiki page should help you to upgrade your application. We will keep updating this page with the feedback we get from the community on our issue tracker and on StackOverflow.

GraphQL Java 24+ baseline

The GraphQL Java team recently released new major releases for the Java DataLoader and GraphQL Java projects. They immediately supersede the 23.x generation so Spring for GraphQL 1.4 will require GraphQL Java 24+ as a baseline. This last-minute change shouldn't affect much your…

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 fifth milestone continues delivering new features and refinements on top of 7.0.0-M1, 7.0.0-M2, 7.0.0-M3 and 7.0.0-M4.

Jackson 3.0 support

As of #33798, we default to supporting Jackson 3.x in our entire stack, falling back to Jackson 2.x. Support for the Jackson 2.x generation has been deprecated in Spring Framework, and our current plan is to disable its auto-detection in 7.1, and remove its support entirely in 7.2.

Jackson 3.x uses a new tools.jackson package, which differs from the usual com.fasterxml.jackson. Classes from the "jackson-annotation" artifact (like @JsonView, @JsonTypeInfo) remain in the com.fasterxml.jackson…

On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Framework 6.1.20 and 6.2.7 are available now.

Spring Framework 6.1.20 ships with 4 fixes and documentation improvements. This version will be shipped next week with Spring Boot 3.3.12.

Spring Framework 6.2.7 ships with 25 fixes and documentation improvements. This version will be shipped next week with Spring Boot 3.4.6 and 3.5.0.

CVE-2025-22233:

The releases address CVE-2025-22233 for Spring Framework DataBinder Case Sensitive Match Exception (2nd update).

Open source support for Spring Framework 5.3.x and 6.0.x generations has ended and will expire for the 6.1.x generation next month, see our support page for more information…

On behalf of the Spring for GraphQL team, I am pleased to announce the availability of 1.4.0-RC1, our last stop before the generally available release. In case you missed it, 1.4.0-M1 already shipped lots of new features and improvements.

You can read the full changelog for 1.4.0-RC1 and the upgrade notes on our wiki.

DataLoader observations

The Spring for GraphQL instrumentation creates Micrometer Observations for GraphQL requests and DataFetcher operations. Some data fetching operations are relying on batch loading calls to avoid the "N+1 problem". In previous generations, one would not see the difference between a "full" data fetching operation and one that simply delegates to DataLoader…

I am pleased to announce that Spring for GraphQL 1.3.5 is now available on Maven Central.

1.3.5 closes 12 issues. This version will ship with Spring Boot 3.3.11 and 3.4.5, to be released next week.

How can you help?

If you have general questions, please ask on stackoverflow.com using the spring-graphql tag.

Project Page | GitHub | Issues | Documentation | Stack Overflow

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 team and everyone who has contributed, I am pleased to announce that Spring Framework 6.1.19 and 6.2.6 are available now.

Spring Framework 6.1.19 ships with 11 fixes and documentation improvements. This version will be shipped next week with Spring Boot 3.3.11.

Spring Framework 6.2.6 ships with 35 fixes and documentation improvements. This version will be shipped next week with Spring Boot 3.4.5 and 3.5.0-RC1. It's very unusual for us to ship new features in maintenance versions, but this version also brings first-class support for Bean Overrides with @ContextHierarchy. Please refer to the "Context hierarchies with bean overrides" documentation section…

On behalf of the team and everyone who has contributed, I am pleased to announce that Spring Framework 6.2.5 is available now.

Spring Framework 6.2.5 ships with 14 fixes and documentation improvements. This is an out of cycle release fixing a JAR scanning regression introduced last week. This version is right on time for the Spring Boot 3.4.4 and 3.5.0-M3 releases tomorrow.

Project Page | GitHub | Issues | Documentation

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!

By popular demand, the java Optional type is now better supported in SpEL expressions. Not only you can now call null-safe operations on Optional types, but you can also use the Elvis operator…