This is pretty critical as it totally prevents using envers with the above pattern (updates of entities which have a composite ID, with one of the IDs being another entity), so I’ve updated the priority.

The only workaround (if such thing can be considered a workaround) is totally disabling envers…