Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
• Features and deprecations must be submitted against the 6.3 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

Hey!

Thanks for your PR. You are targeting branch "6.2" but it seems your PR description refers to branch "6.2 for bug fixes".
Could you update the PR description or change target branch? This helps core maintainers a lot.

Cheers!

Carsonbot

There is no reason to forbid 1.8+. As they follow semver, a 1.8 version is fine to be used as well once available (whether 1.7.x stable releases or 1.8.x-dev is used depends on the minimum-stability you configure).

So -1 from me.

Going to re do this from scratch, removing the upper restriction all together.

6.2 branch Has it correct, but 6.2.7 (down to 6.2.5?) have the limitation --- not sure how I can fix that, since it would look like no change happened against 6.2. So is serializer 6.2.0 newer than 6.2.7?

No. It is just that the 6.2 branch contains the change done in #49727, which will be part of the 6.2.8 release.