How to handle compatibility checks between different contract versions

[xiangshiyin]

In case of breaking changes on data contracts, what is the best way to make sure the newer version has backward compatibilities to the older version?

[jgperrin]

At the standard level or at the implementation level?At the standard level, so far, we have been really careful in incremental changes that will NOT break using semver. Some of us are working on v3, which will introduce some changes. I must admit that we might have broken this rule with some requirements on some fields, but going forward, we will also watch those. On the implementation of a data contract on YOUR data, it is the responsibility of the contract (or product) owner. I don’t think the field is mature enough to edict best practices, but I may be wrong…—Jean-Georges On Nov 8, 2023, at 16:12, Xiangshi Yin ***@***.***> wrote: In case of breaking changes on data contracts, what is the suggested mechanism to make sure the newer version has backward compatibilities to the older version? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>