What qualifies as non-breaking changes in a schema?

The addition of new fields is considered a non-breaking change in a schema because it improves the structure without disrupting the existing data or functionality. When new fields are introduced, they typically do not interfere with the existing data or how current processes operate. This allows for backward compatibility, meaning existing integrations and applications can continue to function normally without any modifications.

New fields can provide additional information and enhance the value of the schema while keeping the old fields intact. Other modifications, like changes to standard fields or field deletions, can lead to compatibility issues for existing applications relying on the previous schema, whereas the addition of fields simply extends the data model. Thus, this change type poses no risk to existing data flows or applications and can be seamlessly integrated without requiring significant adjustments on the part of users or systems.