Migrate the use of GithubAction actions/upload-artifact@v3 from v3 to v4. This process will entail addressing significant semantic changes.
Details
It's important to note that there are considerable semantic differences between these versions. The same file/artifact name, for example, cannot be uploaded multiple times without triggering an error in v4. This e.g. is an issue with the current matrix build setup. Even if the overwrite option is set to true, behaviors still seem to vary. It looks like each uploaded file gets individual download URLs that can get mixed up, causing errors when trying to download the artifact.
In order to perform the migration, two alternatives are recommended. Firstly, we could run a job solely for collecting metrics, which also handles the single-time upload. Secondly, we could integrate a check before uploading the artifact(s) in the runs.
Summary
Migrate the use of GithubAction
actions/upload-artifact@v3fromv3tov4. This process will entail addressing significant semantic changes.Details
It's important to note that there are considerable semantic differences between these versions. The same file/artifact name, for example, cannot be uploaded multiple times without triggering an error in
v4. This e.g. is an issue with the current matrix build setup. Even if theoverwriteoption is set totrue, behaviors still seem to vary. It looks like each uploaded file gets individual download URLs that can get mixed up, causing errors when trying to download the artifact.In order to perform the migration, two alternatives are recommended. Firstly, we could run a job solely for collecting metrics, which also handles the single-time upload. Secondly, we could integrate a check before uploading the artifact(s) in the runs.
References