Announcements and Hints

Hints #

Software in End-Of-Life (EOL) #

For security reasons, Relution does not support software which has already reached its end of life (EOL), since no security patches will be provided any more.

Announcements and Deprecations #

• Update to 26.1: Before upgrading to version 26.1 or higher, a 26.0.x version (for example the latest version 26.0.3) must be installed and started at least once. If you are already running any 26.0.x version, you do not need to update to 26.0.3 specifically. Background: Relution 26.1 only supports database upgrades from version 26.0, so a 26.0.x version is required as an intermediate step. Additionally, updating to 26.1 may cause the Docker container to fail to start due to a permission issue on the temp directory. See Problem with update to 26.1 → for the solution.
• Device groups: As has been announced previously, Relution 26.0 will automatically migrate organisations to device groups. Support for the legacy functionality will be removed. This version will also finally drop all rule sets, which have been replaced by device group actions.
• Java: Starting with version 5.35, Relution will require Java 21. With 26.0, starting Relution on older Java versions is no longer possible.
• Language settings: With the update to 5.31, the organisation’s default language (Settings > Language) will be applied to all user accounts. Before updating, make sure that the language is configured according to your preferences. This is only necessary if the user has never manually saved their profile.
• MariaDB: Relution 5.30 requires MariaDB 10.11 or higher. Please note that support for MariaDB in general will only be available until the end of 2027.
• PostgreSQL: Relution 5.29 requires PostgreSQL 14 or higher.
• License Handshake: After successfully updating to Relution 5.35, downgrading is no longer possible.