There is a new release of the upload-artifact and download-artifact actions provided by Github that come with a breaking change for us. We were previously relying on being able to have multiple jobs upload the same artifact name, and have Github automatically coalesce them.
This no longer works, but with the trade-off that artifacts are now available from the REST API immediately after the step that creates them completes.
The following implements the logic to fetch all of the artifacts from a given workflow run, and unzip them in place. This is actually how I had intended to do this before, but was hit by API limitations.
There is a demo workflow run here and the corresponding call for testing that was created here.
This doesn't change the API, or expectations upon the repositories using the workflows in any way, and is just maintenance to keep the repo up to date and using the latest Github APIs :)
There is a new release of the
upload-artifact
anddownload-artifact
actions provided by Github that come with a breaking change for us. We were previously relying on being able to have multiple jobs upload the same artifact name, and have Github automatically coalesce them.This no longer works, but with the trade-off that artifacts are now available from the REST API immediately after the step that creates them completes.
The following implements the logic to fetch all of the artifacts from a given workflow run, and unzip them in place. This is actually how I had intended to do this before, but was hit by API limitations.
There is a demo workflow run here and the corresponding call for testing that was created here.
This doesn't change the API, or expectations upon the repositories using the workflows in any way, and is just maintenance to keep the repo up to date and using the latest Github APIs :)