webcomponents and webcomponents-react version and release releationship #7910
-
|
I understand that when working with UI5 Web Components for React, the underlying UI5 Web Components and the React wrapper library generally need to be kept in sync for optimal compatibility and functionality.
Dependency Relationship: The UI5 Web Components 2.16.0 were just releases. So, this means, I have to wait until the UI5 Web Components for React peer dependencies get updated? 2.16.0 includes a fix I need and I'm wondering, how close the two projects release new versions to stay in sync. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Yes, We usually release a compatible minor version on the next working day after the ui5/webcomponents release. Occasionally - like in this case - discrepancies arise during the update that need to be resolved before we can proceed. For this specific release, we’re aiming to have it completed by tomorrow. However, since there are upstream dependencies outside of our control, I can’t guarantee it. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification, and you guys make a great job to enhance both libraries that close together. It's great to see that these projects are actively maintained. |
Beta Was this translation helpful? Give feedback.
-
|
just wanted to let you know that v2.16.0 is now available. Please note that it's only compatible with v |
Beta Was this translation helpful? Give feedback.
-
|
You guys rock! That's a turnaround speed letting us move at a high speed as well. |
Beta Was this translation helpful? Give feedback.
Hi @Robert-M-Muench
Yes,
ui5/webcomponentsandui5/webcomponents-reactlibraries need to sync their minor versions. New component APIs and components would otherwise not be included in the wrapped web component.We usually release a compatible minor version on the next working day after the ui5/webcomponents release. Occasionally - like in this case - discrepancies arise during the update that need to be resolved before we can proceed.
For this specific release, we’re aiming to have it completed by tomorrow. However, since there are upstream dependencies outside of our control, I can’t guarantee it.