Updates and upgrades

Versioning

The second number in the version (e.g. 1.9.0) defines the major version, while the third number defines the minor version. For example:

  • 1.9.0 → 1.9.1: Minor version change.

  • 1.9.0 → 1.10.0: Major version change.

Major vs. Minor Releases

Minor releases include bug fixes and new features. Backups and exported artifacts remain compatible within the same minor version.

Major releases introduce significant technical changes, such as technology upgrades or configuration changes. After updating to a new major version, a rollback is not possible. Unless stated otherwise, updates to new major versions are performed automatically and require no manual interaction.

New features are typically introduced in minor releases, so users usually see no direct visible changes between major releases.

Steps

Unless specified otherwise in the changelog, updates and upgrades are performed by:

  1. Creating a backup of all artifacts and database entries.

  2. Stopping the SmartUnifierManager (if installed as a service, stop the service).

  3. Renaming the old SmartUnifierManager folder (recommended).

  4. Extracting the new SmartUnifierManager.

  5. Starting the SmartUnifierManager.

  6. Activating the license.

  7. Restoring the backup. Required migrations of configurations will be performed during the restore.

No manual interaction is required beyond these steps.