You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure we ever logged this but we have composite packages in use, and the migrate package task does not seem to work with composites. Will this be supported? With out it we cannot automate promotion of composites between XLD instances towards production deployment
The text was updated successfully, but these errors were encountered:
Hello @jdewinne . Thanks for the reply. We are well aware of application dependencies but we cannot adopt them with the current required naming convention (semVer 2.0) We are working with XebiaLabs on potential solutions for increases flexibility in naming of dependency versions to support other naming conventions.
If this will not be supported then we will need to look at alternative options
We have not been provided a committed timeline for deprecation as of yet as it relates to comp packages either. They are still in heavy use due to the above mentioned restriction requiring semVer use
Not sure we ever logged this but we have composite packages in use, and the migrate package task does not seem to work with composites. Will this be supported? With out it we cannot automate promotion of composites between XLD instances towards production deployment
The text was updated successfully, but these errors were encountered: