SDK versioning policy

Introduction

We strongly advise keeping your SDK integration up-to-date.

When unable to regularly deploy the latest Entrust Identity Verification SDK as part of your build process, we recommend upgrading to the latest version at least once per quarter. This cadence will provide a reasonable balance of new value from Entrust against the engineering spend required to deploy it.

Versioning and support lifetime

Entrust uses semantic versioning to designate SDK releases.

We have updated our support lifetime policy as of March 2026 to provide more clarity and predictability. Along with improved definitions, we have updated the lifetime policy for major versions to include a minimum guaranteed support period of 12 months. This change provides more predictability for customers to plan their SDK updates.

Major

• Purpose: To introduce backwards incompatible changes, which may arise from new products, features, customizations, or other important improvements.
• Code changes: Will require one or more incompatible changes to the integration interface, depending on whether you use the affected product, feature or configuration. You'll find these changes clearly described in our migration guides.
• Lifetime:
  • Every major version is supported for a minimum guaranteed period of 12 months from its general availability release date.
  • When a new major version is released, the previous major remains supported for an additional 9 months.

Minor

• Purpose: May contain new products, features and customizations, in addition to bug fixes, security patches and other changes and improvements.
• Code changes: No incompatible changes to the integration interface - any changes required to enable new functionality are optional.
• Lifetime:
  • Minor versions are supported for 2 months after the first release of the next minor version.
  • Capped by the lifetime of its major version.

Patch

• Purpose: Contains bug fixes, security patches and other small changes and improvements.
• Code changes: No incompatible changes to the integration interface.
• Lifetime: Patch versions are supported until the next major, minor or patch version is released.

Definitions and exceptions

The following are the definitions for supported and unsupported versions, as well as some exceptions to the above versioning and support lifetime policy.

Supported Version

A supported version is one that:

• Continues to receive maintenance updates, including bug fixes, security patches, and other necessary improvements.
• May receive some new features, but is not guaranteed to receive all new features or product launches introduced in later major versions.
• Is guaranteed to function and eligible for support (e.g., SDK assistance and troubleshooting) for the duration of its support window.

Unsupported Version

An unsupported version is one that:

• Will no longer receive any updates, including feature additions, bug fixes, security patches, or platform compatibility updates.
• Will continue to function until further notice, after which the version may stop working entirely.
• Is not eligible for regular support.

Policy Exceptions

• In certain cases, changes to underlying platforms or third‑party services we rely on such as iOS, Android, or critical external libraries, may require us to shorten support timelines or mandate upgrades outside of our standard policy. This includes situations where a serious security vulnerability, deprecation, or breaking platform change necessitates immediate action, and older versions may cease to function as a result.

How often should an SDK integration be upgraded?

We recommend updating your SDK minor and patch version as part of your build process, and updating your SDK major version as often as possible.

Customers on newer versions of the Entrust Identity Verification SDK consistently see better performance across user onboarding and fraud mitigation, so we strongly advise keeping your SDK integration up-to-date.

The mobile ecosystem is constantly changing, with an ever-growing landscape of devices, operating systems, web browsers and hardware-based technologies that your identity verification flow must be ready for. Fraudster behavior, techniques and tooling also continue to evolve.

To address these issues, we continually improve our SDK. Find our update migration guides and release notes in our Technical Reference for each platform.

When it is not possible to update more regularly, we recommend upgrading to the latest version at least once per quarter. This cadence will provide a reasonable balance of new value from Entrust against the engineering spend required to deploy on a predictable schedule.

We share a SDK release roll-up by email once per quarter, detailing all new functionality since the previous quarterly email. You can find all previous SDK release letters here. To subscribe to the email, please ask your Customer Success Manager.