Update _posts/2025-06-18-hibernate7-on-quarkus.adoc

Co-authored-by: Yoann Rodière <[email protected]>

Author: lucamolteni

_posts/2025-06-18-hibernate7-on-quarkus.adoc

@@ -73,7 +73,7 @@ In the meantime, you can always refer to the https://quarkus.io/version/main/gui
 
 === Hibernate Reactive together with Hibernate ORM ===
 
-A long-awaited feature is the ability to https://github.com/quarkusio/quarkus/issues/13425[mix Hibernate ORM and Hibernate Reactive extensions] in the same Quarkus application. Without this feature, making the two extensions coexist required workarounds that are now unnecessary as, since Quarkus 3.2.4, it is now possible to mix the two.
+A long-awaited feature is the ability to https://github.com/quarkusio/quarkus/issues/13425[mix Hibernate ORM and Hibernate Reactive extensions] in the same Quarkus application. Without this feature, making the two extensions coexist required workarounds that are now unnecessary as, since Quarkus 3.24, it is now possible to mix the two.
 Hibernate Reactive is a powerful reactive data access abstraction, but its advantages vary per project. Instead of dictating usage, we enable users to experiment easily with both Hibernate ORM and Reactive. Projects using Hibernate ORM can add the Reactive extension, create reactive resources reusing mapped entities, running tests and benchmarks, and determine if it suits their specific needs and scalability goals. While using both, it’s easier to choose the most suitable approach for different use cases. Another benefit is that it makes it easier to migrate in small steps from one to the other as necessary.
 Panache users will have this possibility in the API as well starting from https://github.com/quarkusio/quarkus/issues/46096[Panache 2.0]