In Relation To

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 The format for the RSS feed URL is standardized - https://github.com/{organization}/{project}/releases.atom.

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. For these reasons, we have decided to no longer write blog posts for Hibernate ORM releases.

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:

Today someone asked us to add some documentation explaining how to deal with addition of elements to very large collections. I’m not sure if this is a topic I really want to talk about in the documentation, but it’s definitely worth a blog.

We’re now seeing a lot of interest in Jakarta Data, along with very positive reactions from the people who’ve already tried it out.

I’m afraid I missed the news that Hibernate 6.6 is now available in Quarkus, and so I’ve been slow of the mark in letting everyone know that Hibernate Data Repositories, our implementation of Jakarta Data, is now fully integrated with Quarkus. 🎉🎉

To start writing repositories, all you need to add is:

Hibernate Reactive 2.4.2.Final is now available!

This release contains a couple of bug fixes:

The full list of changes is available on GitHub.

Hibernate Reactive 2.4.1.Final is now available!

This release is compatible with Hibernate ORM 6.6.1.Final and Vert.x SQL client 4.5.10.

The full list of changes is available on GitHub.

We just published Hibernate Validator 9.0.0.Beta3, the next beta 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. Compared to the previous release in this series, this version removes a few more constraints, configuration properties and APIs, which have been deprecated for several major versions. We have also identified some possible areas to improve while testing the previous version in the downstream projects. Also, there are some bug fixes.

We are pleased to announce the release of Hibernate Search 7.1.2.Final and 7.2.1.Final.

These releases bring a few bug fixes and clarifications in the migration guides.