In Relation To

Hibernate Reactive 2.4.3.Final is now available!

This release is compatible with Hibernate ORM 6.6.4.Final.

The full list of changes is available on GitHub.

We just published Hibernate Search 8.0.0.Alpha1, the first alpha release of the next major version of Hibernate Search.

This version brings metric aggregations, logging improvements, a new Lucene backend and more.

Hibernate Search 8.0 sets JDK 17 as a baseline and is no longer compatible with JDK 11.

It also upgrades Lucene and Hibernate ORM dependencies and includes compatibility with the latest Elasticsearch and OpenSearch versions.

Hibernate Reactive 3.0.0.Beta1 is now available!

This release is compatible with Hibernate ORM 7.0.0.Beta3.

The full list of changes is available on GitHub.

We just published Hibernate Validator 9.0.0.CR1, the first candidate release of the new 9.0 series of Hibernate Validator.

This series targets Jakarta EE 11. It is the implementation of the Jakarta Validation 3.1.

Since the previously released 9.0.0.Beta3, we spent some time on various build improvements, tidied up a few things and addressed various reports from the community and our testing.

With this release, we no longer publish relocation POMs for the old org.hibernate group id.

There also are some dependency updates and bug fixes.

Hibernate Validator 8.0.2.Final maintenance release is out.

This release contains some documentation and constraint violation message translation updates as well as a few bug fixes.

We are pleased to announce the release of Hibernate Search 7.2.2.Final.

This release brings a couple bug fixes and dependency upgrades.

As we have continued automating much of our processes, one item that has become increasing more scripted is releases. That automation creates a GitHub release for each release we do.

GitHub exposes an RSS feed for a project’s releases. For Hibernate ORM, that URL is https://github.com/hibernate/hibernate-orm/releases.atom ^[1].

There are many excellent ways to be notified of releases through this RSS feed, including many email clients. And many people already consume these release announcements using RSS from this site.

A few weeks ago, the GitHub Security Lab reported to the Hibernate team a vulnerability in GitHub Actions workflows used in some Hibernate projects, which could have (indirectly) impacted released artifacts.

Fortunately, that vulnerability wasn’t exploited and all Hibernate releases are perfectly safe.

However, considering the impact an exploit could have had, we thought it would be best to provide some transparency on what happened and how we made sure that Hibernate releases — past, present and future — are safe.

I think it’s fair to say that Jakarta Persistence has too many options for mapping collections and to-many associations. Way back when we wrote JPA 1.0, I argued against adding so many things, on the grounds that a lot of these options tend to lead users down the wrong path. But the things I wasn’t keen on were ultimately added in JPA 2.0, and I can’t really say this was a bad decision, since all these options are things users ask for.

That said, I’m going to begin by reiterating what I’ve said many times before: