Asmir Mustafic

shouldn't this be considered a PHP issue more than serializer?

I think you should increase the minimum version of jms/serializer in your project as most probably it affects your application. For other projects, a version lower than 1.13 could work.

>I encountered a bug regarding metadata serialization when travis-ci was installing dependencies through composer update --prefer-lowest that i was able to solve with requesting a minimum version of ^1.13 for...

I think you misunderstood semantic versioning. Version bumps do not happen on upstream project when there is a new release of down-stream projects... to make an example, following this logic...

https://github.com/semver/semver/issues/148 tries to understand which one is the right thing to do (is a bit not php-focused but it gives the idea...)

Anyway, will consider it for the next release

JMS 2.X has not yet been released... how are you using it?

is ` $settings` and array or a doctrine array collection? have you tried calling `toArray` on it?

can you please send a failing test case?

Are you sure that you don't have in the packages dev folder another jms_serializer.yml with the settings to true?