Fabbot doesn't seems happy, but it complains about things which are not in my changes... Should I update it too ?

Fabbot doesn't seems happy

You can ignore it

Thank you @NeilPeyssard.

Hi @fabpot @nicolas-grekas @NeilPeyssard

I think this PR could make BC-Break. In my case in my project (with SF 6.4), I have a lot base-code where a property have the same name as accessor-method.

For example:

<?php

class MyObject {
    public function __construct(
        private readonly bool|null $isVerified,
    ) {
    }

    public function isVerified(): bool|null
    {
        return $this->isVerified;
    }
}

returns before 6.4.6:
['verified' => true];

returns after6.4.6:
['isVerified' => true];

This situation means that if "keys" are sent via the API in the original version, it now has to be fixed, which is a difficult work.

At the moment, only way is to add conflict in composer.json like
"symfony/serializer": ">= 6.4.6"

In my opinion, you have a right - this was bug but this should be fixed in deprecation-way with some warnings. WDYT ?