Prevent issues by matching major and minor versions
PreviousDevolutions Password Manager Android life cycle policyNextVault privacy for administrators and users
Last updated
Was this helpful?
Always match major and minor versions across Devolutions products (e.g., 2026.2 with 2026.2) to avoid errors and compatibility issues.
Devolutions products follow a Major.Minor.Patch.Revision numbering scheme, a variant of semantic versioning (SemVer) adapted to include a revision or build number. For example, in version 2026.2.9.0:
2026: Major version, which usually corresponds to the release year.
2: Minor version, which introduces feature increments.
9: Patch (or build), which includes bug fixes or minor updates.
0: Revision (or build number), which is generally reserved for hotfixes or internal builds.
In addition to understanding major and minor versions, it is important to distinguish between extended maintenance and latest versions. This distinction applies only to Devolutions Server.
Extended maintenance: Refers to the latest minor version of the previous major release (e.g., 2026.2.9).
Latest: Refers to the most recent version available, which includes all the latest features, improvements, security patches, and bug fixes (e.g., 2026.2.x).
Each time a new release becomes available (e.g., 2026.3.x), the latest version (2026.2.x) becomes the new extended maintenance version. No security updates or patches are provided for previous extended maintenance versions (e.g., 2025.3.x or earlier). This lifecycle is repeated for each new release.
The Version management allows administrators to manage the workspace availability in other versions of Remote Desktop Manager for Windows, macOS, and Linux.
Last updated
Was this helpful?
Was this helpful?