Versioning and maintenance strategy for OpenUI5.
OpenUI5 uses a three-number version identifier, for example, 1.71.22. The numbers have the following meaning:
To view the documentation for a specific version, check at https://sdk.openui5.org/versionoverview.html which versions are available. You can view the version-specific Demo Kit by adding the version number to the URL, for example, https://sdk.openui5.org/1.71.22/ .
To get an overview of the new features of each version, see What’s New in OpenUI5. To see the fixes contained in each patch, check the Change Log.
Every month, OpenUI5 releases a new version for productive usage. Support periods vary by release type:
| Release Type | Support Period | Typical Release Cycle |
|---|---|---|
| Standard | 6 weeks | Monthly |
| Mid-Term Support \(MTS\) | 9 months | Anually \(6 months after LTS release\) |
| Long-Term Support \(LTS\) | 15 months | Anually |
The release strategy follows the principle of “one innovation code line”: Subsequent versions ensure continuous innovation with an evolving code line. All OpenUI5 versions receive critical security fixes until the version’s end of life (EOL) date.
Mid-term and long-term maintenance releases also receive bug fixes until their end of maintenance (EOM) date (for standard releases, bug fixes are included in the next OpenUI5 version). After the EOM date, only critical security patches are offered for a year, after which these versions reach their EOL date.
OpenUI5 versions reach End of Cloud Provisioning (EOCP) and are removed from the Akamai content delivery network approximately one year after becoming outdated. A patch becomes outdated either when superseded by a newer patch, or when its corresponding OpenUI5 version reaches End of Maintenance (EOM). Removal occurs during the first week of the quarter following this one-year period.
In the version overview at https://sdk.openui5.org/versionoverview.html, you can find information on the maintenance status of all available OpenUI5 versions and the EOCP dates for each patch version.
OpenUI5 resources are available on the Akamai content delivery network. There, you can also find multiple OpenUI5 versions, and you can use them in your code as described in Variant for Bootstrapping from Content Delivery Network.
Check the available versions with respective maintenance status at https://sdk.openui5.org/versionoverview.html.
Caution:
Keep in mind that OpenUI5 versions are removed from the Akamai content delivery network at the latest one year after their release. Therefore, make sure to keep your OpenUI5 version up to date! We recommend using the UI5 Renovate Preset Config tool, which allows you to become aware of version changes and upgrade OpenUI5 in a controlled manner.
You can find which framework versions you use in your app in the Technical Information Dialog ([Ctrl] + [Shift] + [Left Alt / Left Option] + [P] .
To access the OpenUI5 version at runtime, you can use the following code:
sap.ui.require([
"sap/ui/VersionInfo",
"sap/base/util/Version"
], (VersionInfo, VersionUtil) => {
VersionInfo.load().then(oCurrentVersionInfo => {
const oOpenUI5Version = new VersionUtil(oCurrentVersionInfo.version);
// ...
});
});
Note:
Standalone apps, e.g. apps using the
self-containedbuild of UI5 Tooling, will report the version of the app itself. Only if the framework resources are provided by a content delivery network (CDN) or a similar shared installation will the main version of the framework be retrieved as shown above.
Related Information