You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/computer-vision/sdk/understand-the-liveness-sdk-versions.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,21 +11,21 @@ ms.date: 01/15/2025
11
11
12
12
# Understand the Liveness Client-side SDK versions
13
13
14
-
Microsoft will regularly upgrade the liveness detection client SDK and service to improve security, reliability, and user convenience. Staying current with these updates is crucial because the liveness detection field faces active and sophisticated attacks.
14
+
Microsoft regularly upgrades the liveness detection client SDK and service to improve security, reliability, and user convenience. Staying current with these updates is crucial because the liveness detection field faces active and sophisticated attacks.
15
15
16
16
## Client-side SDK Versions
17
17
18
18
Liveness detection client-side SDK uses major.minor.patch format to indicate software version.
19
-
- A patch version update is optional reliability fix on client SDK, it won’t impact the compatibility with service.
20
-
- A minor version update is important security and reliability improvement. We will try to extend support for a minor update as long as possible, Azure service might announce retirement of minor update after 6 months
21
-
- A major version update is critical security or breaking API updates. Customers should make client update as soon as possible. Azure service will block the previous major version after 6 months.
19
+
- A patch version update is an optional reliability fix on the client SDK that doesn't impact compatibility with the service.
20
+
- A minor version update is important security and reliability improvement. We'll try to extend support for a minor update as long as possible, Azure service might announce retirement of minor update after six months
21
+
- A major version update is critical security or breaking API updates. Customers should make client update as soon as possible. Azure service will block the previous major version after six months.
22
22
23
23
## Azure Face API Service Version
24
24
25
-
Face liveness detection feature is generally available from version 1.2. Face API will follow the Azure developing cycle, newer API version will add new features in preview release, then general available. A newer service version may require a newer minimal client SDK version. The requirement will be announced when new service version is available.
25
+
Face liveness detection feature is generally available from version 1.2. Face API follows the Azure developing cycle, newer API version adds new features in preview release, then general available. A newer service version may require a newer minimal client SDK version. The requirement is announced when new service version is available.
26
26
27
27
## Service Model Version
28
28
29
29
In the Create Liveness Session operation, customers can specify a liveness model version to classify the session. Azure service is also progressively updating new models. We strongly recommend customers always use the latest model version, which means simply leaving the model version parameter empty.
30
-
- The latest model version (default version) will be compatible with all supported client versions.
31
-
- When a service model is to be retired, Azure service will announce this 6 months ahead, providing customers with buffer time to update their backend service.
30
+
- The latest model version (default version) is compatible with all supported client versions.
31
+
- When a service model is to be retired, Azure service will announce the decision six months ahead, providing customers with buffer time to update their backend service.
0 commit comments