Branch: refs/heads/main Home: https://github.com/hibernate/hibernate-orm Commit: f520bee62605794f51be7872fba75491a312dc58 https://github.com/hibernate/hibernate-orm/commit/f520bee62605794f51be787... Author: Stéphane Épardaud <stef(a)epardaud.fr&gt; Date: 2026-02-20 (Fri, 20 Feb 2026) Changed paths: M tooling/metamodel-generator/src/main/java/org/hibernate/processor/HibernateProcessor.java M tooling/metamodel-generator/src/main/java/org/hibernate/processor/annotation/AnnotationMetaEntity.java Log Message: ----------- HHH-20151 Metamodel geneartor: allow implicit repositories for Panache Next Fixes https://github.com/quarkusio/quarkus/issues/50178 Commit: 6ce283881618b58f665d94a4d7a87c2d9a4b9606 https://github.com/hibernate/hibernate-orm/commit/6ce283881618b58f665d94a... Author: Stéphane Épardaud <stef(a)epardaud.fr&gt; Date: 2026-02-20 (Fri, 20 Feb 2026) Changed paths: M tooling/metamodel-generator/src/main/java/org/hibernate/processor/HibernateProcessor.java Log Message: ----------- HHH-20163 Metamodel generator: do not visit nested types twice I added the indexQueryInterfaces method before the elements were recursively visited to find nested entities. I did not realise we were visiting nested types twice: once with the primaryEntity set (by indexQueryInterfaces) and the second time without it, causing issues with nested repositories losing their primaryEntity in Quarkus Panache. I'm now removing indexQueryInterfaces in favour of the upstream recursion, adapted for keeping track of implicit primaryEntity. Commit: 0f19aad8c6b99f3fbe10d0e1fbc2cf8583af376f https://github.com/hibernate/hibernate-orm/commit/0f19aad8c6b99f3fbe10d0e... Author: Stéphane Épardaud <stef(a)epardaud.fr&gt; Date: 2026-02-20 (Fri, 20 Feb 2026) Changed paths: M tooling/metamodel-generator/src/main/java/org/hibernate/processor/annotation/AnnotationMetaEntity.java Log Message: ----------- HHH-20164 Metamodel processor: Fixed bug with missing catch clause for @Delete queries This only happens in Quarkus Panache when we have an implicit JD repository with a @Delete query method, because jakartaDataRepository is not set, but it should not matter, because this method is only defined by JD for repositories, so I don't think it makes any sense for it to be false. The result was code like this: @Override public long deleteByTitle(String title) { var _builder = session.getCriteriaBuilder(); var _query = _builder.createCriteriaDelete(Panache2Book.class); var _entity = _query.from(Panache2Book.class); _query.where( title==null ? _entity.get(Panache2Book_.title).isNull() : _builder.equal(_entity.get(Panache2Book_.title), title) ); try { return session.createMutationQuery(_query).executeUpdate(); } Note the missing catch. This is because the catch is conditional on jakartaDataRepository while the try is not conditional. Commit: 5be1632d663d918af6d1bbeb023057224fa9e9c3 https://github.com/hibernate/hibernate-orm/commit/5be1632d663d918af6d1bbe... Author: Stéphane Épardaud <stef(a)epardaud.fr&gt; Date: 2026-02-20 (Fri, 20 Feb 2026) Changed paths: M tooling/metamodel-generator/src/main/java/org/hibernate/processor/annotation/AnnotationMetaEntity.java M tooling/metamodel-generator/src/main/java/org/hibernate/processor/annotation/CDIAccessorMetaAttribute.java Log Message: ----------- HHH-20165 Processor: avoid generating conflicting names for repositories Compare: https://github.com/hibernate/hibernate-orm/compare/0b206fb24052...5be1632... To unsubscribe from these emails, change your notification settings at https://github.com/hibernate/hibernate-orm/settings/notifications