Release and Maintenance
Learn about versioning practices, release habits, and the life cycle of Socure's SDKs.
Release frequency
Socure adheres to Semantic Versioning for SDK releases using the format Major.Minor.Patch where precedence is determined by comparing each identifier from left to right: major versions have the highest precedence, followed by minor versions, then followed by patch versions. For example, 3.2.1 > 3.2.0 > 3.1.0 > 3.0.0 > 2.1.1 > 2.1.0 > 2.0.0 > 1.2.0.
The table below describes each version type and its expected release cadence:
| Version type | Example | Scope | Cadence |
|---|---|---|---|
| Major | x | Significant product updates, backward-incompatible changes | Yearly |
| Minor | x.y | Minor features or enhancements, major bug fixes | Quarterly |
| Patch | x.y.z | Minor bug fixes | As needed |
Predictive DocV SDK timetable
The end of support schedule for the Predictive Document Verification (DocV) SDKs is as follows:
| Version | Release Date | End of Support |
|---|---|---|
| Native SDK v5 | November 2024 | To be announced |
| Native SDK v4 | July 2023 | November 2025 |
| Native SDK v3 | July 2022 | July 2024 |
| Native SDK v2 | October 2020 | July 2023 |
| Web (JavaScript) v5 | July 2024 | To be announced |
| Web (JavaScript) v2 | July 2021 | July 2025 |
Digital Intelligence SDK timetable
The end of support schedule for the Digital Intelligence SDKs is as follows:
| Version | Release Date | End of Support |
|---|---|---|
| Native SDK v4 | February 2024 | To be announced |
| Native SDK v3 | August 2023 | February 2025 |
| Native SDK v2 | November 2022 | August 2024 |
| Native SDK v1 | October 2020 | November 2023 |
| Web (JavaScript) v2 | February 2024 | To be announced |
| Web (JavaScript) v1 | N/A | February 2025 |
Maintenance policy
The sections below outline the maintenance policy for DocV and Digital Intelligence SDKs.
End of Support
We will no longer develop or maintain a SDK version after it reaches End of Support (EOS). A SDK version enters EOS when any of the following conditions occur:
| Version Type | Condition for EOS | Example |
|---|---|---|
| Major | A major version enters EOS 12 months after the next major version is released. | All 2.y versions enter EOS 12 months after 3.0.0 is released. |
| Major | A major version enters EOS immediately after two higher major versions are released. | All 1.y versions enter EOS immediately after 3.0.0 release, regardless of the release time of 2.0.0. |
| Minor | Any minor version of the second highest major version enters EOS immediately after a new minor version of the same major version is released. | If 3.y is released, version 2.0.0 enters EOS after 2.1.0 is released. |
| Minor | A minor version of the latest major version enters EOS immediately after two higher minor versions are released. | Version 3.0.0 enters EOS after 3.2.0 is released. |
| Patch | Any version enters EOS immediately after a patch version of the same minor version is released | Version 3.2.0 enters EOS after 3.2.1 is released. |
End of Development
Socure continues development for the last two major versions of an SDK (for example, version 3.y and 2.y) until they reach EOS. While all Socure innovations are built into the latest major release (for instance, 3.y), we will continue to develop the second major version (for instance, 2.x) for critical updates, including security and compliance.
Updated 5 months ago