The Zoom Video SDKs follow the semantic versioning scheme.
Versions with new features and bug fixes
The Zoom Video SDKs are versioned, and are compatible (backwards compatible) with other Zoom Video SDK versions. That being said, new features and new bug fixes are included in each new version. For example, Video SDK (Web) version 1.2.7 and version 1.3.0 can join a session together, but a feature like virtual background introduced in version 1.3.0, would only be available in 1.3.0 and not in prior versions.
Versions with new requirements
A new version could have a new requirement (also referred to as a breaking change), but prior versions would remain as they are. For example, in versions 1.3.0+, the role_type is required in the Video SDK JWT Auth token, but this is not a requirement in prior versions.
Minimum Support Versions
The Zoom Software Quarterly Lifecycle Policy also applies to the Video SDKs.
Why Version the SDKs?
SDK Versioning is good because it locks you into a set of functionality that won’t be affected by changes in new versions. Then, when you are ready to do a version upgrade, you can review the respective details and implement any new requirements before you do a deployment. It is uncommon for new versions to have new requirements or breaking changes. If they do, we mention it on the changelog, devforum, docs, and usually let you know via email (sent to the Zoom account owner and admins email).