In Relation To

We are considering a change of license for Hibernate projects to Apache License 2.0. In fact, more recent Hibernate projects have started out using that license.

6.4 adds some cool new features, in addition to many improvements and fixes.

We just published a new candidate release for Hibernate Search: 7.0.0.CR1.

This release brings in particular compatibility with Hibernate ORM’s discriminator-based multi-tenancy, compatibility with Elasticsearch 8.10 and OpenSearch 2.10/2.11, an upgrade to Hibernate ORM 6.3.1.Final, an upgrade to Lucene 9.8, some Maven artifact renamings, and other bugfixes and improvements.

We just published a maintenance release for Hibernate Search: 6.2.2.Final.

This release mainly adds compatibility with Elasticsearch 8.10 and OpenSearch 2.10, upgrades to Hibernate ORM 6.2.9.Final for -orm6 artifacts, upgrades to Elasticsearch client 8.10.2, Jackson 2.15.2 and Avro 1.11.3, deprecates the ~ operator in regexp predicates, and fixes several bugs.

Today, we published a new maintenance release of Hibernate ORM 6.3: 6.3.1.Final and ORM 6.2: 6.2.9.Final.

We just published Hibernate Search 7.0.0.Beta1, a first beta release of the next major version of Hibernate Search.

The main theme of this new major version is upgrades: JDK 11 as a baseline, switch to Jakarta EE and to the latest Hibernate ORM, upgrade of the Lucene backend to the next major version (Lucene 9).

Beyond that, 7.0.0.Beta1 also includes experimental compatibility with Amazon OpenSearch Serverless, publishes a Hibernate Search BOM containing all of its public artifacts, and more.

Hibernate Reactive 2.0.4.Final is now available!

This release is compatible with Hibernate ORM 6.2.8.Final and Vert.x SQL driver 4.4.5.

The full list of changes is available on GitHub.

Hibernate ORM 6.3.0 has just been released. Simultaneously, 6.2.8 has also been released.

We just published a maintenance release for Hibernate Search: 6.2.1.Final.

This release mainly upgrades to Hibernate ORM 6.2.7.Final for -orm6 artifacts, upgrades to Elasticsearch client 8.9.0, adds compatibility with Elasticsearch 8.9 and OpenSearch 2.9, and fixes several bugs.

I recently enabled a number of Jira Automations which focus on closing issues which are considered stale. An issue is considered stale when

As with any attempt at automation, there will be cases which do not fit nicely into the automation rules - both false positives and false negatives. If you feel one of these issues was incorrectly closed, re-open it. Which assumes that there is a test or response of course :)