Version compatibility for your add-on

When publishing your add-on to the eLabNext Marketplace, you must specify the minimum required eLabNext version. This ensures that your add-on will only be available to users whose environment supports the features and APIs your add-on depends on.

How version compatibility works

The minimum required version is determined by the SDK functions and API calls used in your add-on. By default, this field is pre-filled with one of the following values:

The current eLabNext version for the public cloud, or
The minimum required version from the last released add-on version (if it is higher than the current public cloud version).

When to update the minimum version

You may need to manually update this setting if:

Your add-on uses new SDK or API features available in the Sandbox that are not yet in the public cloud.
You plan to release the add-on to a Private Cloud or On-Premises installation running a different version of eLabNext.
Your add-on has been developed or tested on a specific eLabNext version that is newer than the default value.

If you are unsure which minimum required eLabNext version to specify for your add-on, please contact support for guidance.