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
We changed this behavior from an artifact per platform to a single one in #62. We found that matching names and merging multiple causes data corruption with actions/download-artifact: #29 (comment). Hence why we switch from merging with actions/download-artifact in verify workflow to instead merging using upload-artifact/merge in finalize job.
As this is only an issue with the verify workflow, I'm fine having an opt to have an artifact per platform but keep in my mind that data corruption might happen if you want to download all artifacts at once with actions/download-artifact like:
Activity
crazy-max commentedon Feb 2, 2026
We changed this behavior from an artifact per platform to a single one in #62. We found that matching names and merging multiple causes data corruption with
actions/download-artifact: #29 (comment). Hence why we switch from merging withactions/download-artifactinverifyworkflow to instead merging usingupload-artifact/mergeinfinalizejob.As this is only an issue with the
verifyworkflow, I'm fine having an opt to have an artifact per platform but keep in my mind that data corruption might happen if you want to download all artifacts at once withactions/download-artifactlike:- name: Download artifacts uses: actions/download-artifact@v7 with: pattern: ${{ needs.build.outputs.artifact-name }}* merge-multiple: trueMore info:
dfunkt commentedon Feb 2, 2026
Thanks for the info, I'll keep it in mind. It's a bit unfortunate that a bug like that is still around.