EDI Versioning
DataShift public EDI contracts are versioned so partners can pin integrations, validate reliably, and adopt changes deliberately.
Immutable contract releases
Every public contract release is treated as immutable. A released schema or OpenAPI document should not change in place; corrections require a new release.
Major schema versions
Public schema URLs include the major version. Breaking schema changes require a new major version path so existing integrations can continue to validate against their selected contract.
Backwards compatibility
Additive changes should preserve existing required fields, enum meanings, identifier semantics, and correlation behavior within the same major version.
Stable channel behavior
The stable channel points developers to the recommended public contract set. Consumers that need deterministic validation should pin to an immutable release.
CDN cache expectations
Immutable release artifacts are suitable for long-lived caching. Stable channel metadata should be treated as short lived and refreshed before pinning a new release.