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
Currently download-and-submit will take the latest dependency graph from the artifacts.
In the case of monorepo matrices, where many dependency graph artifacts are generated, there is a need to download all of them and submit them together only if the entire matrix succeeds & a release is generated.
The code is already here to upload multiple dependency graphs, so it should just be a case of parameterising latest:
Thanks for the report @ChipWolf . Can you elaborate on the use case where you have multiple dependency graph files being generated with the same name in a single workflow execution?
Please describe the workflow structure and provide concrete examples of the file names involved?
Thanks!
Currently download-and-submit will take the latest dependency graph from the artifacts.
In the case of monorepo matrices, where many dependency graph artifacts are generated, there is a need to download all of them and submit them together only if the entire matrix succeeds & a release is generated.
The code is already here to upload multiple dependency graphs, so it should just be a case of parameterising
latest
:actions/sources/src/dependency-graph.ts
Lines 126 to 131 in 4ba34e9
The text was updated successfully, but these errors were encountered: