Although we prevented the upgrade to this release (#42769) Spring Framework 6.2.0 has changed something that fixes the problem that was reported.

Comment From: philwebb

Sorry @snicoll, I didn't notice you were assigned.