There have been similar reports on other deps recently. I feel like we will not be able to catch up with all combinations of versions and we should instead tell people how to update. Many did update only framework-bundle, which is wrong. Doingcomposer update "symfony/*" fixes the issue for everyone.

I'd be 👎 here to not create a precedent.

I tend to disagree. We have conflict rules "everywhere" to prevent such issues. The only reason we didn't have one here is that we don't have tests that perform some assertions on the container for this part (might be a good opportunity to add some which would also prevent further regressions).

Tend to agree with@xabbuh. Recommending to updatesymfony/* is a thing, having invalid version constraints between components is another. You taught me it@nicolas-grekas: symfony components/bundles are used in the wild, we can't assume that everyone hear and apply our recommendations, here perhaps because of their own technical constraints leading them to try updating a component and not another.
I think we should keep up improving our cross-package test coverage and maintain proper conflict rules when possible.

But framework-bundle doesn't know about twig-bridge.
All the other conflicts are legit because they target lower level package that framework-bundle is built on.
twig-bridge is just foreign to it.

butit does

that's not obvious reading the composer.json file ;)
you were suggesting adding a test case, possible?

Thank you@xabbuh.