Version lifecycle
Itential provides two support models for Itential Platform, Extended Support (ES) and Standard Term Support (STS). This page explains the lifecycle and support phases for each model.
Version numbering and release types
Itential products follow semantic versioning principles to provide clarity about the nature and scope of changes in each release. Understanding how Itential versions its software helps you plan upgrades and assess the impact of updates.
Semantic versioning structure. Starting with Platform 6, Itential Gateway 4, and Itential Gateway 5, Itential uses a MAJOR.MINOR.PATCH versioning scheme, such as 6.1.2.
- Major releases such as 6.0.0 may include breaking changes and require careful upgrade planning.
- Minor releases such as 6.1.0 introduce new backwards-compatible features and functionality.
- Patch releases such as 6.1.1 contain bug fixes, security updates, and minor improvements without new features.
Legacy versioning. Products using date-based versioning, such as 2023.1 or 2023.2, follow similar principles but use a different format. Updates to these versions focus on bug fixes and security patches during their support lifecycle.
Backwards compatibility. Minor and patch releases within a major version maintain backwards compatibility, ensuring existing integrations and workflows continue to function without modification.
Support models
Extended Support
Extended Support (ES) provides a three-year support period for customers who need longer-term stability.
Support phases:
Standard Term Support
Standard Term Support (STS) provides a six-month release cycle for customers who want faster access to new features.
Support phases:
Regular updates
Software updates, including patch releases, minor releases, and security fixes, are targeted for availability each month, but may release more or less frequently than that, based on customer needs and the nature of the updates. The specific versioning and release cadence may vary by product. Refer to individual product documentation for details.
Regular updates are version-specific and follow the support phase schedule for each version.
Deprecations and breaking changes
Deprecations can be introduced in any release, including ES releases. Deprecated features remain available while the release is active. Backports and bug fixes will not introduce deprecations to existing releases.
Breaking changes can be introduced in any release, including ES releases. Backports and bug fixes will not introduce breaking changes to existing releases.
End of maintenance and support
After two years for STS, or three years for ES, a major Platform software version will reach its end-of-support (EOS) date. After the software reaches EOS, Itential will no longer accept support tickets related to the version, and maintenance releases for the version will cease to be published.
Version support status
Itential Platform
Itential Gateway
Gateway version lifecycles align with their corresponding Platform version. When a Platform version reaches end of support, its associated Gateway version reaches end of support on the same date.
Itential Gateway 5 doesn’t have an assigned end-of-support date yet. It remains supported through at least February 27, 2028, aligned with the Platform 6 end-of-support date. Itential reserves the right to extend this date and will update this page as the timeline is finalized.
For more information, see Gateway compatibility and Gateway versioning.
RPM package compatibility
Platform 6 only: All current RPM packages work together. Install the latest version of each component for best performance.
When an RPM isn’t updated in a maintenance release, the existing version remains current and supported. No update needed.
Security updates
Itential may release security-only maintenance updates until end of support for both Platform and Gateway versions, even if no other fixes are planned.
Software repository retention
Itential periodically removes software from the Itential repository after it reaches end of support.