TYPO3 Core

May I ask you to create an issue for jms/serializer as well?

It looks as if it should be ok for us to add "^1.3.1 || ^2", but it's of course always better to look forward than back, so jms/serializer should catch up in this regard, i suppose.

Ok, rechecked:

• jms/serializer is waiting for doctrine/orm to allow ^2 https://github.com/schmittjoh/serializer/issues/1483
• doctrine/orm allows ^2 in 2.15.x branch, but that has not been released, yet
• Looking through doctrine/instantiator 1.5.0..2.0.0, https://github.com/doctrine/instantiator/compare/1.5.0...2.0.0 , with 1.5.0 being latest 1.x, the changes are type sugar, the php min-raise, and minor cleanups

-> I'll prepare a patch to allow ^1.5 || ^2.0

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/78779

Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/78779

Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/78779

Christian Kuhn wrote in #note-4:

Ok, rechecked:

• jms/serializer is waiting for doctrine/orm to allow ^2 https://github.com/schmittjoh/serializer/issues/1483
• doctrine/orm allows ^2 in 2.15.x branch, but that has not been released, yet
• Looking through doctrine/instantiator 1.5.0..2.0.0, https://github.com/doctrine/instantiator/compare/1.5.0...2.0.0 , with 1.5.0 being latest 1.x, the changes are type sugar, the php min-raise, and minor cleanups

-> I'll prepare a patch to allow ^1.5 || ^2.0

Thanks for your reply. I already opened an issue for that. ;-)
https://github.com/schmittjoh/serializer/issues/1483