API Versioning & Compatibility

We aim for additive, backward‑compatible API evolution. If a change would break compatibility, we provide a versioned interface and maintain the prior version for a defined period.

What this means for you - Tolerate unknown properties (forward‑compatibility). - Don’t rely on undocumented behaviors. - Subscribe to changelogs and test against pre‑release environments when possible.

*Derived from PTC’s API policy guidance.