Needs to account for #61027 (comment)? /cc @rvanlaak

Needs to account for #61027 (comment)? /cc @rvanlaak

Will verify this within the hour, and potentially provide a commit with a test case to cherry-pick.

@soyuka @nicolas-grekas added PR soyuka#2 with a test case and fix for #61027 (comment)

Thank you @soyuka.

And thank you @rvanlaak

As can be read on soyuka#2 the 7.3.2 release actually introduced a regression for ObjectMapper, as our CI pipeline was failing on the Renovatebot update PR to that release. As patch releases usually appear once per month, could this edge case regression on the experimental component be considered to be severe enough for an extra patch release in the upcoming days? 🙌

Are there any other changes in 7.3.2 that make it impossible to downgrade to 7.3.1/7.3.0 for the time until 7.3.3 is fixed at the regular schedule?

No. And the BC itself is on an edge case, so scope of the impact is limited.

We solely can not update to 7.3.2 and will stay on 7.3.1 until this PR gets released and our CI will turn green. It's mostly my over-eagerness that's asking that wants to start dropping all the boilerplate code for ObjectMapper implementations.

I guess that's not an important enough reason for an extra release. 😉