With this release OpenUI5 is upgraded from version 1.149 to 1.150.
Note:
Content marked as Preview is provided as a courtesy, without a warranty, and may be subject to change. For more information, see the preview disclaimer.
| Version | Type | Category | Title | Description | Action | Available as of |
|---|---|---|---|---|---|---|
| Upcoming | Deleted | Announcement | **End of Cloud Provisioning for OpenUI5 Versions \(Q3/2026\)** | **End of Cloud Provisioning for OpenUI5 Versions \(Q3/2026\)** The following OpenUI5 versions will be removed from the OpenUI5 Content Delivery Network \(CDN\) after the end of Q3/2026. **Minor Versions Reaching Their End of Cloud Provisioning** The following versions including all patches will be removed entirely: - 1.84 - 1.133 - 1.138 - 1.140 **Action**: Upgrade to a version that is still in maintenance. **Patch Versions Reaching Their End of Cloud Provisioning** The following patches will be removed: - 1.71.71 to 1.71.72 - 1.84.51 - 1.96.39 to 1.96.41 - 1.108.42 to 1.108.43 - 1.120.32 to 1.120.36 - 1.133.3 - 1.136.2 to 1.136.6 - 1.138.0 - 1.140.0 **Action**: Upgrade to the latest available patch for the respective OpenUI5 version. For more information, see [Version Overview](https://sdk.openui5.org/versionoverview.html). **[Preview](https://help.sap.com/docs/whats-new-disclaimer)**•Deleted•Announcement•Info Only•Upcoming | Info Only | 9999-01-01 |
| 1.150 | Deprecated | Feature | **Deprecations** | **Deprecations** There are currently some deprecations in the `TypeScript` and OData V2 areas \(see the respective entries\). For a complete list of all deprecations, see [Deprecated APIs](https://ui5.sap.com/#/api/deprecated). Deprecated•Feature•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Feature | **`TypeScript`** | **`TypeScript`** We have recently made several changes in the `TypeScript` area: - `TypeScript`-specific API documentation is now published at [https://ui5.github.io/typescript/api/](https://ui5.github.io/typescript/api/) for the latest version and the long-term maintenance versions. It includes `TypeScript`-specific APIs, such as the event-specific parameter types \(like `Input$LiveChangeEventParameters`, see [Interface: Input$LiveChangeEventParameters](https://ui5.github.io/typescript/api/openui5/1.120/sap.m/sap/m/Input/interfaces/Input$LiveChangeEventParameters.html)\), which are not included in the API documentation in the Demo Kit. - The long deprecated type definition packages`@sapui5/ts-types-esm` and `@openui5/ts-types-esm` are no longer released. Use the identical packages `@sapui5/types` and `@openui5/types` instead. - The type definition package `@types/openui5` is now deprecated \(since it offers no benefit when used with the current `TypeScript` versions 6.x and higher\). Use `@openui5/types` instead. `@types/openui5` continues to be released throughout 2026 at minimum. - `TypeScript` 6 and 7 are coming with incompatible changes. From an OpenUI5 perspective, most things continue to work, but the `@ui5/ts-interface-generator` tool cannot yet be used with `TypeScript` 7. For more information, see this [blog post](https://community.sap.com/t5/technology-blog-posts-by-sap/typescript-6-and-7-what-ui5-typescript-developers-need-to-know-in-2026/ba-p/14393526). Changed•Feature•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.StandardListItem`** | **`sap.m.StandardListItem`** The `StandardListItem` now supports an optional icon alongside the info text through the new `infoIcon` property. The info text rendering has been migrated to use the internal `ObjectStatus` control. This ensures consistency with `ObjectStatus` behavior and brings the following: - Improved accessibility, including support for inverted state wrapping and high-contrast theming - Text-spacing compliance - Full support for wrapping in inverted state mode - Native truncation handling - Better screen reader support These changes ensure adherence to accessibility standards. For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.m.StandardListItem), the [Sample](https://ui5.sap.com/#/entity/sap.m.StandardListItem/sample/sap.m.sample.StandardListItemInfo), and the [Sample for Wrapping](https://ui5.sap.com/#/entity/sap.m.StandardListItem/sample/sap.m.sample.StandardListItemWrapping). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.ui.mdc.ValueHelp`** | **`sap.ui.mdc.ValueHelp` ** We have improved the filtering behavior in `DefineConditionPanel`. Only the relevant list entries are now shown in the results, and the text that matches what has been entered is now highlighted if the new `highlightFilterResults` is set to `true`. This enhancement improves accessibility for screen reader users and simplifies keyboard and mouse navigation when selecting condition operators. For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.ui.mdc.valuehelp.content.FixedList%23methods/getHighlightFilterResults) and the [Sample](https://ui5.sap.com/#/entity/sap.ui.mdc.FilterBar/sample/sap.ui.mdc.demokit.sample.FilterbarTypes). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.RatingIndicator`** | **`sap.m.RatingIndicator`** In read-only and display-only modes, `sap.m.RatingIndicator` now renders the unselected half of a half-value icon as an outline instead of a filled grey shape. This makes half-value ratings distinguishable without relying on color alone, improving accessibility for users with color vision deficiency. Interactive \(editable\) mode is unchanged. For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.m.RatingIndicator%23overview). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.Panel`** | **`sap.m.Panel`** `sap.m.Panel` now supports a new `Contrast` value for its `backgroundDesign` property. It applies a subtly different background color, making the panel visually distinguishable when placed inside containers with the same background, such as a dialog. In non-Horizon themes, it falls back to the solid background for compatibility. For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.m.Panel) and the [Sample](https://ui5.sap.com/#/entity/sap.m.Panel/sample/sap.m.sample.PanelBackgroundDesign). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.ComboBox`, `sap.m.MultiComboBox`** | **`sap.m.ComboBox`, `sap.m.MultiComboBox`** `sap.m.ComboBox` and `sap.m.MultiComboBox` now support a `maxPickerHeight` property, allowing developers to limit the height of the picker dropdown. When items exceed the set height, vertical scrolling is enabled automatically. Keyboard navigation continues to work seamlessly with scrolling. For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.m.ComboBox) and the [Sample](https://ui5.sap.com/#/entity/sap.m.ComboBox/sample/sap.m.sample.ComboBoxMaxPickerHeight). Note: Has no effect on phones, where suggestions display in a full-screen dialog. Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.Dialog`** | **`sap.m.Dialog`** `sap.m.Dialog` now supports a full-screen toggle via the new `showFullScreenButton` property. When enabled, users can expand the dialog to fill the entire screen by clicking the header button, pressing [Shift\] + [Ctrl\] + [F\] , or double-clicking the dialog header. For more information, see the [Sample](https://ui5.sap.com/#/entity/sap.m.Dialog/sample/sap.m.sample.DialogFullScreen). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **UI Integration Cards** | **UI Integration Cards** - The Object Card groups configuration now supports a new `itemsLayout` property, allowing label/value pairs to be arranged either vertically \(default\) or horizontally. For more information, see the [Sample](https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html#/explore/object/horizontalItemsLayout) and the [API Reference](https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html#/learn/typesDeclarative/object) in the Card Explorer. - UI Integration Cards functionality is now available as Claude Code Skills, enabling AI-assisted development for Cards directly in your IDE. The skills are delivered as part of the UI5 plugins for Claude Code, giving developers intelligent, context-aware support when working with Card manifests and configurations. The Card Explorer documentation has also been updated to reflect AI-driven Card creation workflows. For more information, see the [AI Generation](https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html#/overview/aiGeneration), [Developing Cards](https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html#/overview/developingCards) and [Getting Started](https://ui5.sap.com/test-resources/sap/ui/integration/demokit/cardExplorer/webapp/index.html#/learn/gettingStarted) in the Card Explorer. Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **Date Controls** | **Date Controls** Date controls now show a more accurate placeholder when no value is set. Previously, the placeholder always displayed the last date of the current year. Now, if a min/max range is configured and the year-end date falls outside it, the placeholder shows the max value instead. For more information, see the [Sample](https://ui5.sap.com/#/entity/sap.m.DatePicker/sample/sap.m.sample.DatePicker). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.PlanningCalendar`** | **`sap.m.PlanningCalendar`** The recurring concept, introduced in version 1.128 for non-working time periods, is now extended to appointments. You can define recurring appointments for any period type — daily, weekly, monthly, or custom occurrences. For example, a weekly 1:1 every Monday at 11 AM or a daily standup every workday at 10 AM. For more information, see the [Sample](https://ui5.sap.com/#/entity/sap.m.PlanningCalendar/sample/sap.m.sample.PlanningCalendarRecurringItem). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Control | **`sap.m.DynamicDateRange`** | **`sap.m.DynamicDateRange`** Custom options in `sap.m.DynamicDateRange` can now display both date and time in the value help dialog footer. Previously, the footer only showed the date, which was misleading for time-sensitive options such as a custom Business Day \(9 AM – 5 PM\). Developers can now override `getValueHelpUIFooterFormatTypes` to return `datetime`, enabling the full date and time to appear in the selected date bar at the bottom of the dialog. For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.m.DynamicDateOption%23methods/getValueHelpUIFooterFormatTypes) and the [Sample](https://ui5.sap.com/#/entity/sap.m.DynamicDateRange/sample/sap.m.sample.DynamicDateRangeWithCustomOptions/code). Changed•Control•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Feature | **OpenUI5 OData V4 Model** | **OpenUI5 OData V4 Model** The new version of the OpenUI5 OData V4 model introduces the following features: - The `groupPaths` feature introduced with OpenUI5 1.148 and 1.149 is now documented in [Sorting](/docs/04_Essentials/sorting-d2ce3f5.html) and [Sorting, Grouping, and Filtering for List Binding and Tree Binding](/docs/04_Essentials/sorting-grouping-and-filtering-for-list-binding-and-tree-binding-ec79a5d.html). - The combination of data aggregation or recursive hierarchies with `sap.ui.model.odata.v4.ODataModel#getKeepAliveContext` is now supported.For more information, see the [API Reference](https://ui5.sap.com/#/api/sap.ui.model.odata.v4.ODataModel%23methods/getKeepAliveContext). - When you use data aggregation without group levels, the following features are supported experimentally: - When you create a new record, the header context is marked as outdated only if its properties are used in a `Sorter` or `Filter` object, or if a `$search` or custom query option is set. The grand total's context is marked as outdated if the new properties are used in a `Filter` object, or if a `$search` or custom query option is set. - Properties specified with the `additionally` option in `$$aggregation` or `v4.ODataListBinding#setAggregation` can now be read using `v4.Context#requestSideEffects`. For more information, see the API Reference for [`v4.ODataListBinding#setAggregation`](https://ui5.sap.com/#/api/sap.ui.model.odata.v4.ODataListBinding%23methods/setAggregation) and [`v4.Context#requestSideEffects`](https://ui5.sap.com/#/api/sap.ui.model.odata.v4.Context%23methods/requestSideEffects). Changed•Feature•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Changed | Feature | **`sap.ui.model.type` Types** | **`sap.ui.model.type` Types** The `#getPlaceholderText` method for the following types now accepts two new optional parameters, `oMinimum` and `oMaximum`. Use these parameters to compute a placeholder that fits within a specific date range. - `sap.ui.model.type.Date` - `sap.ui.model.type.Time` - `sap.ui.model.type.DateTime` - `sap.ui.model.type.DateInterval` - `sap.ui.model.type.TimeInterval` - `sap.ui.model.type.DateTimeInterval` Changed•Feature•Info Only•1.150 | Info Only | 2026-07-09 |
| 1.150 | Deprecated | Feature | **OpenUI5 OData V2 Model** | **OpenUI5 OData V2 Model** The OData V2 hierarchy solution is now fully deprecated. This now also applies to the following: - `sap.ui.model.odata.v2.ODataTreeBinding` class - `sap.ui.model.odata.ODataTreeBindingFlat` class - `sap.ui.model.odata.v2.ODataModel#bindTree` method **Action:** Switch to the OData V4 hierarchy solution. For more information, see [Transition from OData V2 to OData V4](/docs/04_Essentials/upgrading-your-odata-model-cda632b.html#loiocda632b01c1e4a988ccecab759d19380__section_OD2OD4) and [Recursive Hierarchy](/docs/04_Essentials/data-aggregation-and-recursive-hierarchy-7d91431.html#loio7d914317c0b64c23824bf932cc8a4ae1__section_RCH). Deprecated•Feature•Recommended•1.150 | Recommended | 2026-07-09 |