Release and compatibility policy

Check compatibility for the exact versions you plan to deploy. Use the release record for tested combinations and the approved customer agreement for support periods and upgrade terms.

Release evidence

A qualified release should identify:

service and portal artifact versions;
database scripts and required infrastructure;
SDK package versions and supported runtimes;
API and callback contract versions;
configuration changes;
known limitations and security findings;
validation evidence; and
rollback or recovery conditions.

SDK versions

Check the package version, runtime, framework version, and adapter together. The SDK feature matrix lists capabilities; each package page states its runtime requirements.

A successful installation or build does not establish runtime support. Confirm the tested combination in the approved release record.

API contracts

Versioned routes identify the contract family. They do not promise that every endpoint or response remains unchanged for a fixed period.

Use the generated endpoint catalog to find the route. Then review its request, response, and callback contracts alongside the release notes and consumer tests.

Contract changes

Release notes identify changed contracts and affected customer actions. Complete the stated qualification checks before applying the release to a customer environment.