Tags
Authors
The first candidate release!
Hibernate ORM version 5.6.5.Final is now available, improving compatibility with the latest version of H2.
We just published Hibernate Search 6.1.0.Final!
The most important change by far in Hibernate Search 6.1.0.Final
is support for asynchronous, distributed automatic indexing
through the outbox-polling coordination strategy.
But it doesn’t stop there and introduces Elasticsearch 7.16 compatibility, OpenSearch 1.0/1.2 compatibility, search DSL improvements, conditional mass indexing, and more!
We just released Hibernate ORM version 5.6.4.Final.
We just published Hibernate Search 6.1.0.CR1, the first release candidate of Hibernate Search 6.1.
Among the main changes since Beta2: better defaults and optional operators for the regexp predicate, additional Maven artifacts compatible with Hibernate ORM 6, and more.
We just published Hibernate Search 6.1.0.Beta2, another beta release of the next minor version of Hibernate Search.
Among the main changes: persistence and management of aborted events with the "outbox-polling" coordination, definition of Lucene analyzers without referring to Lucene classes, Elasticsearch 7.16 compatibility, OpenSearch 1.2 compatibility, and more.
We just published a bugfix release for Hibernate Search: 6.0.8.Final.
Hibernate ORM 6.0.0.Beta3 has been released. Just in time for the holidays!
We are especially excited for this release because it feels like the last beta on the long journey it has taken to develop 6.0. Lots of work has gone into Beta3, but like Beta2 most of that work has been behind the scenes. A few specific things of note:
Hibernate projects are not affected by the vulnerabilities behind CVE-2021-45046 and CVE-2021-44228: none of the Hibernate projects has a runtime dependency on Log4j core.
We use JBoss Logging, which provides a minimal API bridging to your logger backend of choice and does not come with fancy features relying on JNDI lookups.
We do use Log4j during development of the Hibernate libraries as it’s a dependency of our testsuites; therefore we’ve still upgraded all branches.
Today, we released maintenance releases for our Hibernate Validator 6.2 and 7.0 branches.
As of now, you are all aware of the Log4j 2 security issue called Log4Shell announced on Friday. The good news is that Hibernate Validator does NOT use Log4j 2 but uses JBoss Logging as its logging framework.
Why release these versions then? Log4j 2 is only a test dependency of Hibernate Validator (being a test dependency, Log4j 2 doesn’t come in your apps through Hibernate Validator so you don’t have to worry about this issue from the Hibernate Validator perspective), but we already got hit in the past by security scanners being not as fine grained as we would have liked so we preferred to release new versions proactively so that we are sure Hibernate Validator does not get wrongly reported as unsafe.
