SDK and cross-platform plugin versioning

The Nevis Mobile Authentication SDK and cross-platform plugins are generally adhering to the semantic versioning principle:

Given the version number format MAJOR.MINOR.PATCH:

• MAJOR version changes with new features or incompatible API changes.
• MINOR version changes when adding functionality in a backward compatible manner.
• PATCH version changes with backward compatible bug fixes.

There are some specifics to these rules applied to the Nevis mobile SDKs and plugins:

1. The MAJOR version in the SDKs and plugins will always be the same across the platforms. We will roll out new features simultaneously to Android, iOS, React Native and Flutter.
2. The MINORversion may contain breaking client API changes to ensure API and behavioral alignment between the platforms. These breaking changes will require small code changes in the client code. We try to keep such scenarios to a minimum and will clearly indicate it in the release notes if this case occurs.
3. The cross-platform plugins for React Native and Flutter will always use the latest version of the Android and iOS SDKs of the same MAJOR version. For example, the React Native plugin version 4.0.0 might use iOS SDK 4.1.2 and Android SDK 4.0.1
4. Updates in the SDK hardening framework will lead to a PATCH version increase for non-breaking updates and MINOR version increase for breaking changes, unless a new hardening framework is rolled out as part of a MAJOR version change.

Consult our SDK support matrix for detailed information regarding:

• Flutter plugin and native SDK information
• React Native plugin and native SDK information
• Mobile OS versions
• IDE and environment
• Nevis Backend compatibility