Hi,
We are using several components from the Constellation UI Gallery (GitHub - pegasystems/constellation-ui-gallery).
Our current approach is to download the COMPONENTS_ONLY ZIP packages (for example, ConstellationUIGalleryLib_5_0_6_COMPONENTS_ONLY.zip) and import them into our development environment whenever we need a major release or patch update.
I have a question regarding version management of the imported assets.
The downloaded ZIP always contains the ruleset ConstellationUIGalleryLib with a ruleset version of 01-01-01. In newer releases, many existing components are delivered with updated JavaScript files that have different names. As a result, importing a new release creates additional rules instead of replacing the existing ones.
Over time, all component updates accumulate under the same ruleset version (01-01-01), causing that ruleset version to grow significantly.
Questions:
- Is it acceptable to continue importing component updates into a single ruleset version (01-01-01) as provided by the ZIP packages?
- Are there any best practices for managing versioning and rollback support when importing newer component releases?
- How do other teams handle cleanup or governance of older component versions that remain in the ruleset after multiple imports?
Any guidance, recommendations, or examples of how others manage Constellation UI Gallery component upgrades would be greatly appreciated.
Thanks!
