⚠️ This PR will break DoctrineBundle which has already been made compatible with Symfony 7.

Ah, I forgot about this one. As I wrote on another PR, ORMv3 makes LazyServiceEntityRepository useless, we should deprecate and drop it.

ORMv3 makes LazyServiceEntityRepository useless

Yes, but we still need a solution for ORM 2 which will stay around for a while.

we should deprecate and drop it.

LazyServiceEntityRepository is marked as internal, so we can drop that class without deprecation. If we find a way to keep the laziness of ServiceEntityRepository for ORM 2, I'm fine with the late removal of this feature. I won't have time to work on that though. 😕

So how to overcome this? My SF7 project I now need to keep symfony/var-exporter at 7.0.0-BETA1.
Or is there some release coming which would fix this?

There is an in-progress PR for DoctrineBundle.

Actually, the PR is even merged. So if you use the dev version of DoctrineBundle, it should be OK.

2.11-dev or 2.12-dev ?

Here is the PR: doctrine/DoctrineBundle#1727

2.11-dev for now. The change has not yet reached 2.12-dev as the merge-up between branches has not yet been done after the merge of that PR.

Ok, I required 2.11-dev for Doctrine Bundle and it worked. Now all my Symfony packages are RC1. Thanks for quick responses.

I've released DoctrineBundle 2.11.1 that includes the fix.