This is needed for use-case where you have aggregated workflows. An intended example is a Databroker release workflow where we want to trigger both databroker and databroker-cli workflows from the same workflow. With current setup that will fail as dash data will be overwritten. With this change (and making sure that different file names are used) there is no problem.
This change may theoretically cause backward incompatibilities if any action rely on the name of the dash artifact uploaded, but I assume no Kuksa component does that so suggest that this can be tagged as 2.6 and 2
This is needed for use-case where you have aggregated workflows. An intended example is a Databroker release workflow where we want to trigger both databroker and databroker-cli workflows from the same workflow. With current setup that will fail as dash data will be overwritten. With this change (and making sure that different file names are used) there is no problem.
This change may theoretically cause backward incompatibilities if any action rely on the name of the dash artifact uploaded, but I assume no Kuksa component does that so suggest that this can be tagged as 2.6 and 2