Adding an enum value may be wire-compatible while an older consumer rejects, crashes, or chooses a dangerous default. Preserve the raw value and make unsupported behaviour explicit.
SemVer communicates change to a declared software API. Data compatibility needs separate proofs for old and new readers, writers, stored history, wire formats, and business meaning.
An old Protobuf reader can preserve fields it does not understand when it parses and reserializes binary messages. JSON conversion and field-by-field copying can quietly destroy that protection.
Adding an optional field can break strict parsers, signatures, hashes, exhaustive logic, size limits, identity rules, and old round trips even when the wire format accepts it.