Cascade unexpected behavior

Hi Hibernate developers,
I’ve got a question regarding the Hibernate 6 behavior. In version 5 we had an entity with relation like below and there was no problem. Now it’s impossible to do this without first persisting B1 and B2 and then adding the reference from B1 to B2.

Example:
A is managed entity. B1 and B2 are new objects of the same type.
A has a collection of B1, B2 (collection has cascade SAVE_UPDATE/PERSIST), in the same trascation we also create add a reference of B2 into B1 (this relation has no cascade). So we end up with A → collection B1, B2 and B1 referencing B2.

During flush B1 is persisted, but complains about B2 not being persisted. I wonder why this does not work anymore in version 6? Is this because version 6 is now more strict?

Caused by: org.hibernate.TransientPropertyValueException: object references an unsaved transient instance - save the transient instance before flushing

Did you try with the latest ORM 6.4 version already? If so and the problem persists, please try to create a reproducer with our test case template and if you are able to reproduce the issue, create a bug ticket in our issue tracker and attach that reproducer.