Please target 6.1 here as well.

I think, the documentation should show an actual code example of a configured request matcher instead of just mentioning that it is somehow possible to provide your own matcher.

I tried adding one copying from other similar configuration code blocks, is it ok/enough?

We usually don't write whole documentation blocks inside aversionadded block. Just document the feature as if it has always existed and add a smallversionadded block blow that new piece of documentation where you tell the reader that this feature has actually been added in 6.1. Once we work on the documentation for Symfony 7, a maintainer can simply drop thatversionadded block without touching the rest of your documentation.

@derrabus Is it ok for you to merge now? :)

LGTM, but I'm powerless on this repository. Someone from the docs team will need to review and merge your PR. upside_down_face

Ok, sorry for the ping then, who should I notify to see it merged? :)

Tristan, sorry it took us so long to merge your contribution 🙏 ... and congrats on your first Symfony Docs contribution 🎉