Spring Data 2026.1 Release Notes

Upgrading from Spring Data 2026.0 (Spring Data 4.1.x)

General Themes

*

Participating Modules

Details

Spring Data Build - 4.2
Spring Data Commons - 4.2
Spring Data JPA - 4.2
Spring Data Relational - 4.2
Spring Data MongoDB - 5.2
Spring Data Neo4j - 8.2
Spring Data Elasticsearch - 6.2
Spring Data Couchbase - 6.2
Spring Data for Apache Cassandra - 5.2
Spring Data Redis - 4.2
Spring Data REST - 5.2
Spring Data KeyValue - 4.2
Spring Data LDAP - 4.2

New and Noteworthy

Spring Data Commons - 4.2

Spring Data JPA - 4.2

Stricter validation of named repository queries in `@Query`

When @Query(name = "…") or @Query(countName = "…") reference a named query that does not exist, Spring Data JPA now consistently throws a QueryCreationException at repository initialization. Absent named querties previously fell back to a derived query silently, which made typos easy to miss.

Applications using name or countName with a value that does not resolve to an existing named query will fail to start and surface the mismatch. For example, the following declaration now requires that a named query UserRepository.findByLastname.count exists:

@Query(value = "select u from User u where u.lastname = :lastname",
       countName = "UserRepository.findByLastname.count")
Page<User> findByLastname(String lastname, Pageable pageable);

To fix this, either register the corresponding named query or remove countName to let Spring Data JPA derive the count query automatically. The derived <name>.count convention, used when countName is not set at all, is unaffected and continues to fall back silently.