ApiRTC versioning and releases.
We recognize that you need stability from the ApiRTC library. Stability ensures that reusable components and libraries, tutorials, tools, and learned practices don't become obsolete unexpectedly. Stability is essential for the ecosystem around ApiRTC to thrive.
We also share with you the need for ApiRTC to keep evolving. We strive to ensure that the foundation on top of which you are building is continuously improving and enabling you to stay up-to-date with the rest of the web ecosystem and your user needs.
This document contains the practices that we follow to provide you with a leading-edge application development platform, balanced with stability. We strive to ensure that future changes are always introduced in a predictable way. We want everyone who depends on ApiRTC to know when and how new features are added, and to be well-prepared when obsolete ones are removed.
ApiRTC version numbers indicate the level of changes that are introduced by the release. This use of semantic versioning helps you understand the potential impact of updating to a new version.
ApiRTC version numbers have three parts: major.minor.patch. For example, version 4.5.3 indicates major version 4, minor version 5, and patch level 3.
The version number is incremented based on the level of change included in the release.
Latest and adviced ApiRTC version is available on our servers from address: https://cloud.apizee.com/apiRTC/apiRTC-latest.min.js
You can also choose to select the latest ApiRTC version based on a minor release, for example the latest patched 4.6: https://cloud.apirtc.com/apiRTC/v4.6/apiRTC-latest.min.js
ApiRTC JS library Change Log