Breaking changes are part of the natural evolution of the platform. They happen when an update alters or removes behavior in a way that is not fully compatible with previous versions. To keep this process predictable, we follow strict rules and communicate early, allowing your teams to prepare with confidence.
  • Breaking changes are introduced only in a major version.
  • They are announced in advance, always with clear migration guides and practical examples.
  • Deprecated features emit warnings before removal, giving teams time to adjust without sudden impact.
  • We aim to minimize disruption by grouping breaking changes together and providing alternative solutions whenever possible.

​
Examples

  • Field replacement: In v2, the chartOfAccounts field was removed and replaced by transactionRoute, routeFrom, and routeTo for better clarity and control.
  • Validation rules: The environment variable ACCOUNT_TYPE_VALIDATION was introduced in v3, requiring explicit account type validation that was previously optional.
  • Deprecation cycle: The scale field emitted deprecation warnings in v2 before being fully removed in v3.