I should add that those events are triggered through an error handler, and that having the bridge installed actively breaks it.

Maybe we should disable (and later disband) that feature under PHPUnit 10+?

Well, I don't think PHPUnit 10 contains the existing deprecation-related features of the bridge (at least not all of them).

However, we should look at rebuilding them on top of the PHPUnit events instead of replacing the error handler with our own for PHPUnit 10+.

I discussed PHPUnit 10's event system with @nicolas-grekas at SymfonyCon in November. I think the way forward for Symfony is to no longer register its own error handler for the bridge, let PHPUnit's own error handle emit events for deprecations etc., and then have the bridge subscribe to the events it is interested in. If you want the bridge to produce different output for deprecations than what PHPUnit offers out of the box.

Do u plan to fix it in 6.3?

now that PHPUnit 10 is out, I'm giving this a shot. I experience the same error noted here: symfony/recipes#1173

@nicolas-grekas notes here that this should resolve the problem.

It looks like that was merged, so I'm wondering what the next step is here.

Next step would be adding the PHPUnit 10 support to the deprecation handler; this probably means a nearly total rewrite of it, to be done side-by-side to the old one, since the versioning of the bridge is tied to the framework.

Sounds pretty labor intensive.

Would you say this is a priority of the team, or consumers shouldn't expect to see 10 support for quite some time?