Alex Van Boxel

Single field moved to new oneof Is safe and binary compatible. Default submit and validate behaviour is warning. As in some storage backend this field changes from required to nullable...

Field type change enum with int32, uint32, int64, and uint64 enum is compatible with int32, uint32, int64, and uint64 in terms of wire format (note that values will be truncated...

Field type change fixed32 is compatible with sfixed32 Compatible

Compat: Message <> Bytes evolution

1

Field type change bytes and message Compatible with bytes if the bytes contain an encoded version of the message.

Field type change string and bytes Compatible as long as bytes are UTF-8.

Field type change sint32 and sint64 Compatible, but data loss can occur when consumer has lower precision.

Field type change int32, uint32, int64, uint64, and bool Compatible, but data loss can occur when consumer has lower precision.

Field names should in general not be renamed. Warning: Developer workflow, will brake when regenerating code Error: Data pipelines that rely on metadata