Nicolas Grekas

That's on purpose. I get this is a drawback in your situation but this is also a nice safeguard in many more. You should duplicate the binding in envs that...

That's because you're missing an implementation for __isset. While property access was tolerant to this, this breaks the behavior of objects with the php engine.

Maybe a note in the UPGRADE-6.4.md file? Up for a PR?

(note that #57372 has been reverted recently)

> this is how stateless firewalls are checked everywhere else in Symfony not anymore, this was all reverted recently

Could we augment the LogoutEvent with an isStatelessFirewall method? That'd require telling LogoutListener that the firewall it monitors is lazy, which is doable in SecurityExtension? Can you please dig this...

I agree with the above comment: the entity manager is not ready to use readonly properties, because by doing so it breaks legit use cases that need to reset it...

@derrabus actually I doubt that this would work. The virtual proxy strategy is essentially the best possible implementation of what you're saying, but still, there is one major issue (if...

(you need to bump the version of the string component in the composer.json file to fix the deps=low tests)

The next version is 5.4.39